Oduro

Navigate

AI

What a voice agent should capture from the call

What a voice agent should write down from the call, and which lines a person still has to own.

Key takeaways

  • Capture the caller, their request in their words, the job it belongs to and the next step. Nothing more than you need.
  • The record should land where your team already works, not in a separate call log.
  • Prices, dates, exceptions and complaints stay with a person.
  • Tell callers the call is recorded and why, and give them the rest of your privacy information.
  • Don't use a voice agent for outbound marketing calls without specific consent.
Joel Oduro, founder of Oduro

By Joel Oduro, Founder

Last updated 7 min read

Cover for the guide on what a voice agent should capture from a call.

A voice agent should capture who called, how to reach them, what they asked for in their own words, which job or enquiry it belongs to and the agreed next step, then write all of that into the system your team already works from. Anything that commits you to a price, a date or an exception should go to a person, and callers should be told up front that the call is recorded and why.

Whether you call it an AI receptionist, AI phone answering or a voice agent, the test is the same: after the call, can someone on your team pick it up without ringing the customer back to ask the same questions? Here's what I'd have it capture, what I'd keep with people, and the UK rules worth knowing before you switch one on.


The call that never reaches the record

Here's the usual pattern. The phone gets answered, which feels like progress. Then the details sit in a call recording, a transcript emailed to a shared inbox, or a voicemail someone means to listen to. The next morning, a person rings the customer back and asks them everything again.

That's not an answering problem, it's a capture problem. A voice agent that answers every call but doesn't write down anything useful just moves the backlog from the phone to the inbox.

What the call should capture

Keep the list short and specific. For most service businesses, it's:

  • Who called and how to reach them
  • What they asked for, in their words
  • Which job, account or enquiry it belongs to
  • The next step, if it's already defined (a callback window, a booking, a quote visit)

"In their words" matters. A summary like "customer enquiry re: service" is useless. "Boiler making a banging noise since Sunday, needs someone before Friday" is something a person can act on.

Capture only what you'll use. Data minimisation is a core UK GDPR principle, and it's also just good practice: every extra question the agent asks is another chance for the caller to give up. If you run a clinic, be especially careful. Health details are special category data under UK GDPR, so decide what the agent genuinely needs to take (often a name, a number and the type of appointment) and leave the rest for a clinician.

What stays with a person on the call

A voice agent can take details, answer from approved information and book into slots you've opened. It shouldn't make commitments on your behalf.

That means anything involving a price you haven't published, a date outside your normal booking rules, a refund, a complaint, or an exception to policy goes to a person, with the details already captured so the caller doesn't repeat themselves. The same goes for anything urgent or safety-related: the agent should know your escalation route and use it. I've written more about the decisions you shouldn't hand over to AI.

Say you run a 15-person plumbing and heating firm. A caller asks if you can fit a new boiler next Tuesday for the price they saw on a competitor's site. The agent's job is to take their name, address, boiler details and the date they want, tell them a person will confirm availability and price, and say when. It doesn't agree to Tuesday and it doesn't match the price.

Recording, privacy and the rules

This is the bit people skip, and it's where the ICO has been fairly clear.

On recording: the ICO's guidance says that if you record calls, you must tell callers you're recording and why, and a recorded message at the start is good practice. The rest of your privacy information (how long you keep recordings, who you share them with, people's rights) can follow by email or a link to your website. Recordings and transcripts are personal data, so callers can ask for them through a subject access request. I'd also have the agent say plainly that it's an automated assistant. Being honest up front costs nothing and saves awkwardness later.

On outbound calls: keep your voice agent on inbound calls unless you've taken advice. Under PECR, automated marketing calls need specific consent, and general marketing consent isn't enough. In its innovation advice, the ICO said that even a short AI-generated voice greeting at the start of a marketing call would count as an automated call. Live marketing calls also need screening against the Telephone Preference Service.

Two caveats. Several of these ICO pages carry a note that they're under review following the Data (Use and Access) Act 2025, so check them before you go live. And the ICO hasn't yet published guidance written specifically for conversational voice agents. A data protection impact assessment is a sensible step before you switch one on, especially if callers might share sensitive details.

Put the call on the same path

The captured details should write into the same system as your web enquiries and emails: the CRM, the job system or the booking tool you already run. One record per customer, with the call notes attached, and one named person who owns the next step.

If calls land in a separate voice-agent dashboard, you've just built a second inbox. If you're also adding chat, the same rule applies; see what website chat should handle before a person steps in. And before any of it goes near a real customer, test the agent properly. For more on where AI fits in a service business, browse our guides.

See Voice agents for voice agents that capture the call, hand exceptions to a person and write the record onto the path your team already uses.

Questions people ask

What should an AI receptionist capture from every call?

The caller's name and contact details, what they asked for in their own words, which job or account it relates to, and the next step. Keep it to what your team will actually use.

Do I have to tell callers the call is being recorded?

Yes. The ICO says you must tell people you're recording and why, and a recorded message at the start is good practice. The rest of your privacy information can follow by email or a link.

Can a voice agent make outbound sales calls?

Not without specific consent. Under PECR, automated marketing calls need specific consent, and the ICO has said even a short AI-generated greeting would make a marketing call automated.

Should a voice agent answer every call?

Not necessarily. Many firms start with overflow and out-of-hours calls, where the alternative is voicemail, and keep their team on the line during the day. Either way, the agent hands anything needing judgement to a person.

Sources