Cleavr

More than twenty native integrations connect by OAuth or API key, and they act as well as read. They cover accounting, ERP and business management systems (Pennylane, NetSuite, SAP, Sage, Microsoft Dynamics NAV, Oracle, Odoo, Xero, Zoho, Sellsy, Axonaut), billing, payments and banking (Stripe, Chargebee, Qonto), CRM (HubSpot), messaging (Slack, Teams) and automation platforms (Zapier, Make, n8n). B2G invoices go to Chorus Pro through its official API the moment they are validated, and payments are matched into the ERP, which is synced again when a debtor pays. Alerts are pushed to Slack.

SourceCleavr, cleavr.fr/en/faq and cleavr.fr/enread 2026-09-06

Cleavr runs the collection cycle as progressive phases, from reminders and qualification through friendly and firm stages to pre legal and legal, with escalation following debtor behavior rather than a fixed schedule. Cleavr Intelligence qualifies every response and triggers the next action. Disputes pause the workflow, and payment stops it and cascades the ERP sync and analytics. When amicable collection fails, a complete file goes to a bailiff on the vendor's portal, so the whole recovery runs as multiple steps on Cleavr's own runtime.

SourceCleavr, cleavr.fr/en/faq and cleavr.fr/enread 2026-09-06

Decisions are grounded in three things: invoices, clients and payments synced from the ERP, which remains the source of truth; the rules and tone the customer sets; and each debtor's reply as Cleavr Intelligence qualifies it. No maintained retrieval structure over the customer's documents, contracts or policies is described.

SourceCleavr, cleavr.fr/en/faq and cleavr.fr/enread 2026-09-06

Before a formal notice is sent or a file goes to a bailiff, Cleavr creates a task with the full file context and the team approves or rejects it in one click, so nothing sensitive goes out without them. Disputes pause reminders and either resolve on their own or land as a task, depending on how much autonomy the customer has given Cleavr Intelligence. Deployment can start with a segment of debtors in observation mode and gain autonomy over time.

SourceCleavr, cleavr.fr/en/faqread 2026-09-06

ISO 27001:2022 certification covers the Cleavr platform and infrastructure, as the vendor's own security page states. Cleavr is a GDPR processor with an appointed DPO, encrypts with AES-256 at rest and TLS 1.3 in transit, and isolates each client through row level security; its sub processor list is published. What is missing is any access surface for the customer: no SSO, SAML or SCIM through the customer's identity provider and no named role or permission model, although the FAQ refers to tasks created for the team.

SourceCleavr, cleavr.fr/en/security and cleavr.fr/en/faqread 2026-09-06

Every action lands in a complete audit trail with timestamp, author and context, protected against alteration, kept six to twelve months and exportable. Cleavr Intelligence also shows the qualification and confidence behind each decision on a debtor's response, and dashboards and call summaries report the state of every receivable.

SourceCleavr, cleavr.fr/en/security and cleavr.fr/en/faqread 2026-09-06

The homepage describes a profile for each debtor that the agent maintains and reads on every decision. It tracks interactions and payment patterns, such as when the debtor pays, which channel they respond to and when they open messages, scored and trended, and tone and timing are personalized from it.

Its scope is clear, one debtor across interactions, but Cleavr gives no lifetime, retention or deletion terms for the profile apart from the receivable records, so whether it can be deleted for one customer without touching the business record is unanswered. The broader claim that the AI gets sharper the more it works describes learning absorbed into the product.

SourceCleavr, cleavr.fr/enread 2026-09-06

Data is hosted only in the European Union, on AWS in Paris, Ireland and Frankfurt through Supabase, and those regions are listed as Cleavr's own infrastructure. A customer cannot pick a region or bring its own cloud, and there is no on premises or dedicated tenant option. The regions are a fact about where Cleavr runs, not an option a buyer can use.

SourceCleavr, cleavr.fr/en/security and cleavr.fr/en/faqread 2026-09-06

Default recovery workflows ship with proven settings for durations, channels and tone that work from day one and can be customized. The site also sells sector adaptations, for SaaS, healthcare, build ups and services, but these are configurations of the same product, and the Chorus Pro module is a feature of the platform. What a customer gets is one workflow with defaults to tune, not a catalog of distinct agents or workflows to choose between.

SourceCleavr, cleavr.fr/en/faq and cleavr.fr/enread 2026-09-06

Invoice and payment events synced continuously from the ERP start the agent's work. Overdue invoices are detected and reminders start from D plus 1 and before due dates, and debtor replies are qualified with the next action triggered without intervention. B2G invoices are deposited on Chorus Pro the moment they are validated in the customer's system, rejections are detected and resubmitted, and webhooks fire on recovery events. Outreach runs over email, SMS and messaging apps, and over phone, voicemail and letter.

SourceCleavr, cleavr.fr/en/faq and docs.cleavr.frread 2026-09-06

Five sub processors appear on the security page, AWS, Vercel, Stripe, Brevo and Slack, and none of them supplies a model; the FAQ names Supabase and AWS as infrastructure. A customer or admin cannot choose a model either. An AI provider missing from a published sub processor list is the plainest sign that the model provider goes unnamed.

SourceCleavr, cleavr.fr/en/securityread 2026-09-06

The Cleavr Connect API is published at docs.cleavr.fr, and through it a partner platform submits receivables into recovery and receives status events. The reference covers authentication over OAuth and endpoints for onboarding, receivables and webhooks, with date based versioning, a JavaScript client and an LLM export of the schemas. Access is gated: the FAQ says the Enterprise API is documented there with webhooks and is granted on request to approved partners and enterprise customers. The full platform API, Cleavr One, is described but not documented publicly.

SourceCleavr, docs.cleavr.fr and cleavr.fr/en/faqread 2026-09-06

Cleavr's AI starts in observation mode on a segment of debtors and gains autonomy over time, a supervised ramp on live operations, and the homepage says it adapts its approach automatically as it works. There is no evaluation harness or scored test cases, and nothing shows a controlled experiment or a readable verdict on a change to the agent.

SourceCleavr, cleavr.fr/en/faq and cleavr.fr/enread 2026-09-06

The agent acts through ERP connections and the Chorus Pro API, and through messaging channels and AI voice calls, while data enrichment keeps client records current as a maintained feed. Nothing shows browser, desktop or computer control. Automated phone calls are a voice channel rather than control of a computer, and data enrichment is a background feed, not an agent operating screens.

SourceCleavr, cleavr.fr/en/faq and cleavr.fr/enread 2026-09-06