Our own product
Writford
A workspace for UK legal firms connecting cited research, matter records, time recording and billing. The research workflow keeps source checking and professional review with the solicitor.
Explore WritfordManchester software house. We build websites, web and mobile apps, MVPs and AI for UK businesses.
An AI voice agent answers your phone 24/7, books appointments straight into the diary you already run, answers routine questions and passes anything else to a person. BigBerri builds them for UK businesses that run on the phone: call answering is live in one to two weeks, booking and multi-site agents take longer, and every build is a fixed price quoted after a free discovery call.
Or call 07305 694001 and hear one answer.
Incoming call — 02:47 AM
Outside business hours
Agent response
“Hello, you’re through to the practice’s automated assistant. I can book you in right now — what day works best for you?”
Every
Call answered
0s
Hold time
Every call answered on the first ring: nights, weekends, bank holidays and the hour when the whole team is in a meeting.
Checks the diary you already run, books, confirms and reschedules, and sends the caller a confirmation by text.
Reminders, confirmations and follow-ups to people who expect to hear from you, on a schedule you set.
Transfers to the right person, takes a message when nobody is free, and flags anything urgent to a human straight away.
An agent that can only take a message is an answerphone with better manners. The useful ones end the call with something done: an appointment in the real diary, a record in the real CRM, a text in the caller’s hand. The phone line is rarely the hard part. What decides the scope is what your diary or practice system permits — some expose everything, some allow reading but not booking, and some sector products need the vendor to approve the connection first. We check yours before quoting.
Every project is scoped and quoted after a free discovery call, so you get a fixed price for your situation rather than a number that assumes someone else’s. These are the shapes most engagements take.
Businesses missing calls while the team is busy, on site, or closed.
Typical timeline: 1–2 weeks
Practices and agencies where the call needs to end in an appointment.
Typical timeline: 2–4 weeks
Several branches or departments, or teams that also need outbound calling.
Typical timeline: 4–8 weeks
Timelines are typical and depend on how many systems are involved and how ready your data is. Tell us what you need and we will give you a fixed price and a date.
This is a typical booking build. Plain call answering compresses into the first two weeks; a multi-site or outbound agent runs longer. The column on the right is the part most proposals leave out: a voice project stalls on diary access and on nobody having written down what the front desk actually says, far more often than on engineering.
| When | What we do | What we need from you |
|---|---|---|
| Week 1Call audit and boundary | We listen to how calls actually arrive: what people ask, when the phone goes unanswered, and what a good outcome is for each call type. We agree the calls the agent will own, write the list of what it must never attempt, and check what your diary or practice system will let it do before promising anything. | A week of call logs or the front desk’s honest account of them, a named decision-maker, and read access to the diary or system in scope. |
| Week 2Conversation design and connections | We write the conversations for each call type, including the opening line that says what the caller is talking to, the questions it asks before booking, and the exact moment it hands over. We build the diary, CRM or practice-system connections agreed in week one and the SMS and email that follow a call. | Your services, opening hours, directions, what you would tell a caller who asks what things cost, and the policies the agent must follow. Whoever owns the systems, for a short access conversation. |
| Week 3Test calls from real people | You get a number to ring. We run your real call types through it, including the awkward ones: the caller who interrupts, the one with a strong accent or a bad line, the one who wants a person straight away. Weak answers get rewritten, and we confirm the handover lands with a human every time. | Two or three people to try to break it, and an hour to review the calls it handled badly. |
| Week 4Go live and listen | Forwarding goes on, usually out of hours or overflow first so nothing changes during the day. We read the transcript of every call in the opening fortnight and fix the answers that fall short while you watch, rather than at a quarterly review. | A decision on where transfers and messages land, and someone to receive them. |
On the phone the cost of pressing on is higher than anywhere else, because the caller cannot scroll back and check. So we design the handover to a person before we write a single conversation. An agent that knows when to stop is worth more than one that always has an answer, and the failures we are most often asked to fix are an agent that carried on when it should have handed over.
The list is yours, not ours. We write a first draft from your sector and your policies, you correct it, and it becomes the specification the agent is built against and the test calls are scored on.
Not legal advice, and your own advisers should confirm how each applies to you. But these are the questions that separate a supplier who has thought about running a phone line in the UK from one selling a demo.
Most voice agents record, and the recording is personal data. ICO guidance is that you must tell people you are recording and why, and it treats a recorded message at the start of the call as good practice for doing so. Your privacy notice has to cover the calls, a lawful basis has to be recorded, and there should be a retention rule rather than an indefinite archive. You stay the data controller; we build the announcement and the retention into the agent rather than leaving it to you to remember.
Reminders and follow-ups to your own customers are ordinary service calls. Marketing is not: under the Privacy and Electronic Communications Regulations an automated calling system that plays anything other than live speech needs consent that specifically covers automated calls, and Ofcom’s persistent misuse policy governs silent and abandoned calls and answer machine detection. The Data (Use and Access) Act 2025 raised the maximum penalty for breaking those rules to the same level as UK GDPR. We ask what the agent will be calling about before we build any outbound at all.
The duty to make reasonable adjustments under the Equality Act 2010 is anticipatory: gov.uk and the Equality and Human Rights Commission are explicit that you plan for disabled customers rather than wait for one to have difficulty. In practice that means the agent handles Relay UK calls, slows down or repeats on request, and never traps someone in a menu, and that a human route stays open for anyone who cannot use it.
Ofcom’s General Condition B3 gives a UK customer the right to take their number to another provider. That right only helps you if the number is on an account you control. An agent whose number sits on the supplier’s account is a number you cannot take with you, whatever the contract says. Ours are set up in your company name from the first day.
A voice agent is a phone line, and a phone line has to keep working whether or not you are still talking to us. So the arrangement is built to survive the end of the engagement rather than depend on it.
The telephony provider, the voice platform and any number we set up are registered to your company from the start, with us as an invited user. Ending the relationship means removing a user, not migrating a phone line.
The conversation design as a document you can read, the list of what the agent must never do as tested, every call transcript and recording you have chosen to keep, and a dashboard showing what was booked, transferred and missed.
We read every call. Not a sample — every one — because the calls an agent gets wrong in its first two weeks are the ones that decide whether the front desk trusts it. Fixes ship the same day where we can.
Optional monthly tuning: new services, a changed opening time, a call type you had not anticipated. Agreed before launch rather than negotiated during an incident: what is covered, how quickly we respond, and what counts as new work. Every build has a named person to escalate to.
Each sector page sets out the systems the agent books into there, the rules it has to work under, and what it must hand to a person.
Not listed? Restaurants, gyms, salons and any business that loses work to an unanswered phone. Tell us about yours.
If you mainly need missed calls covered with a generic script, a self-serve app is a fair option and we will say so on the call. What we build is different: an agent that answers from your actual services, opening hours and policies, that books into the diary or CRM you already run rather than a copy of it, with a written list of what it must never attempt and a person on the end of every handover. The build is a fixed price, and the tuning in the first weeks, when real callers reveal the edge cases, is part of it rather than an extra.
They will know, because the agent says so at the start of the call rather than pretending otherwise, and we would not build one that hides it. Whether they stay depends on whether it is useful in the first ten seconds: a caller who wanted to book and is booked, or who asked a question and got the answer, rarely minds what answered. Anyone who asks for a person gets one, immediately and without argument, and we read the transcripts of the calls where people did hang up so the next version handles them.
It is built not to guess. The agent answers from your own information and, where it does not have an answer, says so and hands the caller to a person rather than improvising. The things it must never attempt — clinical or legal judgement, a price commitment, anything outside your written policy — are agreed with you before the conversation flows are built. Every call is logged, so when something does go wrong you can see exactly what was said and we fix the answer, not the transcript.
Yes, for the calls your customers expect: appointment reminders, confirmations, a follow-up after an enquiry, a callback someone asked for. Marketing is different. An agent that dials a list and speaks with a synthesised voice falls under the rules for automated calling systems in the Privacy and Electronic Communications Regulations, which require consent that specifically covers automated calls — the ICO is clear that general marketing consent, or consent to live calls, is not enough. We will build outbound reminders and follow-ups; we will not build a cold-calling robot, and we will tell you why on the call.
Almost always. The simplest route is to forward your existing number to the agent, either all the time or only when you are busy or closed, which works with any provider and changes nothing about your number. Where you want the agent to own a line, we set up a new number or port yours, on an account in your company name. Nothing about your current handsets, mobiles or phone system needs to change for the agent to answer.
You do. The telephony and platform accounts are set up in your company name rather than ours, so your number, your call history and your recordings stay yours, and the agent keeps answering. Handover is part of the engagement rather than a favour at the end of it. Worth asking any supplier this before signing, because an agent running on the supplier’s account is a number you cannot take with you.
A fair question to ask a small company, and the honest answer is that you should not have to depend on it. Because everything runs on your own accounts and the code is yours on completion, another developer can pick it up. We build on the mainstream platforms rather than anything proprietary of ours, for the same reason. Big Berri Limited is registered in England and Wales, company number 16562429, and ICO registered under ZC119995, both of which you can check.
Most guides on this question are written by people selling the answer. Here is the honest version, including the four situations where we tell UK businesses not to buy one.
A subscription needs nothing up front; a custom build is engineered around your systems. Where each one wins, what actually sits underneath both, and how to decide without guessing.
A straight guide to choosing an AI answering service in the UK — what the templated subscription apps actually give you, what a custom-built voice agent adds, and the questions to ask before you sign.
A straight guide to AI voice agent and AI phone answering costs for UK businesses in 2026 — what actually drives the price up or down, hidden extras to ask about, and how it compares to a part-time receptionist.
Review our own live products, check our company registrations and read the commitments that shape a project. These give you concrete work and clear terms to discuss before booking a call.
Our own product
A workspace for UK legal firms connecting cited research, matter records, time recording and billing. The research workflow keeps source checking and professional review with the solicitor.
Explore WritfordOur own product
Tools for connecting shopping assistants with storefront product, cart and checkout actions. Its WordPress and storefront integrations show the kind of connected web workflows we build.
Explore Let AI BrowseRead the LetAIBrowse case studyThirty minutes, free, no obligation and no salesperson. You describe what is costing you time or customers, we ask about the systems involved, and you leave with an honest view of whether this is worth doing. We regularly end that call by saying the tool you already pay for covers it.
The code, the repository and the accounts are set up in your company name rather than ours, and they are yours on completion and full payment. Nothing runs on infrastructure we control, so ending the relationship does not end the thing we built.
Every project is quoted as a fixed price with a written scope after the call, so an over-run is our problem rather than yours. If the scope changes, we say so and re-quote before doing the work, not after.
In the UK or EU, under a data processing agreement, kept only as long as you specify. Any model provider we rely on is named as a sub-processor rather than left implicit, and we will tell you plainly where something you have asked for would put a commitment of yours at risk.
Agreed before launch rather than negotiated during an incident: what is covered, how quickly we respond, and what counts as new work. Every build has a defined escalation to a person, because the failure that costs you is the one nobody noticed.
Big Berri Limited is registered in England and Wales, company number 16562429, and registered with the Information Commissioner's Office under reference ZC119995. Both are public registers. Look us up rather than taking our word for it.
Book a free discovery call and we will tell you which tier fits, what your diary will permit, and whether a cheaper option would do the job. If it would, we will say so.
Book a Free Discovery Call