How it works
What actually happens on a Civilly call
No black box. Here's the real sequence, the same one that runs on every live call.
The call arrives
A real inbound phone call reaches your number and is routed to Civilly over standard business telephony. Civilly greets the caller and asks what they're calling about.
Identity, then verification
Civilly asks for a reference it can use to find a matching record — never confirming a match out loud. It then asks knowledge-based questions from your policy (for example: postcode, vehicle registration, a recent payment amount) and only proceeds once enough of them check out. Caller ID is recorded for audit but never counted as proof on its own — it's trivial to spoof.
Now it can help
Verified, Civilly pulls the real case status, balance or history from your CRM through a purpose-built adapter, and answers in plain language — grounded in what your systems actually say, not a guess.
Structured actions, not free-form edits
Where Civilly can act — proposing a payment plan, logging a dispute, updating a contact detail — it uses a fixed set of tools with your own business rules behind them. There's no tool that can waive or change a balance, and every action is a two-step propose-then-confirm.
Hands off when it should
Outside business hours or outside what it's authorised to do, Civilly offers a callback or a transfer rather than guessing — and an on-call number, if you give it one, is reserved for the calls that genuinely can't wait. Vulnerability signals and disputes get flagged for a person to review.
The call ends, cleanly
A summary is logged with personal data redacted by default, retained for a fixed window, then purged automatically. Nothing about the account is ever left half-updated — actions are recorded before the goodbye, not after. A captured enquiry is posted into your own system, and if that system happens to be down at that moment it's delivered later, not lost.
The whole thing, on one screen
Six boxes, no magic. Your number is forwarded, Civilly answers, and everything it can reach is on this map — nothing else is connected.
What it plugs into
Civilly talks to your CRM through an adapter — a small, purpose-built integration, not a generic scraper.
Where your data already lives
Salesforce, HubSpot, a bespoke case-management system, or anything with an API (or a database Civilly can query safely). We build the adapter as part of setup — this is the "make it relevant to your business" part that takes real time up front.
Least-privilege by default
The adapter only exposes what a call needs: read case/balance data, log notes, propose plans against your rules, flag disputes and vulnerability. Nothing that can silently write outside that surface.