AI phone agent for UK businesses
Nobody has ever enjoyed pressing 5 for something else.
Civilly answers your line, asks what the caller needs in plain words, and either handles it or puts them through to the right person — with the details already taken, so nobody repeats themselves. When a call needs to know exactly who it's talking to, it checks that properly first. And a missed call may not ring twice: a caller who reaches voicemail can just as easily ring the next company on the list.
The name is the standard. Every call handled civilly: it never argues, never pressures, never pretends to be a person — and there is always a way to reach one.
A real line, answered by the real system. Try to catch it out. Not sure what to say? Borrow a caller's identity →
What it actually does on a call
Three jobs. We suggest starting with the first two, which need nothing connected at all.
Works out why they're ringing
No menu, no keypresses. The caller says what they need in their own words and Civilly works out where it belongs — including the ones who don't know which department owns their problem. Just want the menu gone? That's Front Door.
Takes the details properly
Dates parsed, postcodes checked, phone numbers validated. It won't call a form finished while something's missing, and it hands over a complete record rather than "customer rang, will call back".
Checks identity when it matters
For calls that touch an account, it verifies the caller against your own records before disclosing anything — even their name. Caller ID is never treated as proof; it's trivially spoofable. This is the part a booking bot can't legally do.
Books callbacks & transfers
Respects your real opening hours. Out of hours it offers a callback rather than pretending someone's available to take the call.
Knows when to stop
Anything outside what it's authorised to handle goes to a person, with the context attached. Vulnerability signals are flagged before verification even completes — it doesn't wait for identity checks to notice someone is struggling.
Sounds like a person
Natural, low-latency speech with real turn-taking — it doesn't talk over callers, and it copes with someone on speakerphone in a noisy room.
Why it's called Civilly
Manners are cheap to promise and expensive to engineer. These four are built in, and none of them is left to the model's good nature.
It never argues
A caller who says a charge is wrong gets a structured dispute logged and collection paused for a person to review. The agent doesn't make the business's case on the call, and it doesn't decide whether the caller has a point — that's a judgement for a human, so it goes to one.
It never pressures
No script can be configured to discourage a dispute, a complaint or a request for a person — that's in our acceptable-use policy, not just the prompt. When someone says they're struggling, every trace of sales talk stops for the rest of the call, and on a collections line it signposts free, independent debt advice.
It never pretends
It says it's an automated assistant. It says when the office is shut instead of promising a transfer to nobody. And if the line itself is failing, it says so — "if you said something, it didn't reach me" — rather than leaving silence or asking the same question a third time.
There is always a way to a person
A transfer during opening hours, a callback outside them, and an on-call line for the things that genuinely can't wait. A line with no human escape route is a configuration we refuse to build.
The business case, before anything is connected
No borrowed statistics. Just the arithmetic of a phone line.
Hours a week it answers — against 37 from a full-time hire
Of those hours that fall outside a standard working week
Hours a month back for your team, if Civilly takes the first minute of 1,000 calls
Every minute Civilly spends finding out who's calling and why is a minute nobody on your team has to. Take the first minute of each call on a line handling a thousand a month, and that's 1,000 minutes, or about seventeen hours of someone's time every month. It needs no integration to start.
And remember when your customers are free to ring: lunchtime and the evening. One is your busiest hour, the other is after you've closed — why the lunchtime rush loses calls, and why the evening ones never come back.
Built the way a careful business would build it
Every account-affecting action is gated in code, not left to the model's judgement.
The safety is in the code, not the prompt
"We told the AI not to do that" isn't a control. Account access is gated in code, the balance-editing tool doesn't exist to be misused, and payment arrangements come from your rules rather than the model's judgement. If the AI went completely off-script tomorrow, it still couldn't harm an account.
Verification before disclosure
Account lookups return only the next question to ask — no name, no confirmation an account even exists — until enough knowledge-based checks pass. The matching logic sits in code the model never sees.
Everything logged, and redacted
Transcripts and audit detail are stored with personal data redacted by default, on a retention window that purges automatically rather than depending on someone remembering.
It goes further than taking a message
A booking bot can capture a name. It can't validate a date, refuse an incomplete record, escalate a gas leak, or establish who it's speaking to before disclosing anything. Those are the differences between a message and a record your team can act on.
Hear it before you believe any of this.
Ring the demo line and try to trip it up. It takes four minutes and tells you more than this page can — and if you'd like a script, there's a caller identity to borrow.