Field notes

What an AI receptionist actually does on a call

4 min read

Not a robot reading a script, and not a person. What happens on the call, what it hands you after, and where it should get out of the way.

The phrase "AI receptionist" does a lot of work, and most of it is unhelpful. Half the people who hear it picture a chatbot reading a menu tree. The other half picture something indistinguishable from a person, which is both untrue and, in most places, illegal to imply.

So here is the unglamorous version: what actually happens when a customer rings a number with an AI front desk on it.

The first four seconds

It answers. That is not a small thing.

The single most expensive number in a service business is the percentage of inbound calls that go unanswered — at lunch, on a ladder, after five, on a Sunday. Every one of those is a customer who is, right now, dialling the next result. They are not leaving a voicemail. Almost nobody leaves a voicemail anymore.

An AI front desk picks up on the first or second ring, every time, including at 2am. Before anything clever happens, that alone changes the arithmetic.

It says what it is

This part is not optional and you should be suspicious of anyone who treats it as a feature toggle.

The call opens by disclosing that the caller is speaking to an AI assistant. Not buried, not mumbled — stated. If the call is going to be recorded, that is disclosed too, and in jurisdictions that require consent, consent is taken before recording starts, not after.

There are two reasons to care. The obvious one is legal: disclosure and consent rules for automated callers and call recording vary by country and by state, and getting them wrong is a fine, not a telling-off. The less obvious one is commercial. Callers who work out mid-conversation that they were misled about talking to a machine do not become customers. Being upfront costs you almost nothing — people are markedly more forgiving of an AI that says it's an AI.

It has one job: find out what's needed

A good voice agent is not trying to be charming. It is trying to leave the call with a small number of specific facts:

  • Who is calling, and how to reach them again
  • What the job actually is, in their words
  • Where it is
  • How urgent it is
  • When they're available

That is roughly what a competent human receptionist gets, and it is enough to decide whether this is a job worth driving to.

It should also be willing to say I don't know. An agent that invents a price, guesses an availability window, or commits you to a Tuesday it knows nothing about is worse than no agent, because now you are the one breaking a promise you never made. Constraining what it is allowed to claim is most of the work of setting one up properly.

It gets out of the way when it should

Two cases matter, and both need to be built in from the start.

On request. If a caller asks for a human, the correct behaviour is to transfer or take a callback commitment immediately — not to attempt one more qualifying question first. People who ask for a person have usually already decided, and the fastest way to lose them is to make them ask twice.

On emergency. Gas, water, electrical faults, anything with a safety dimension, anyone distressed. The agent's job there is to stop qualifying and escalate — and for genuine emergencies, to direct people to emergency services rather than to your Tuesday slot. This needs to be explicit, tested, and written into the service terms. It is the single thing most worth being paranoid about.

There are also whole categories where a voice agent has no business handling the first conversation at all. Health advice, financial advice, legal advice, anything about someone's immigration status or a safeguarding matter. Those route to a person. If a vendor won't tell you which sectors they exclude, that is the answer to your next question.

What lands on your phone afterwards

The call is the visible part. The useful part is what arrives after it.

A transcript, a summary, and the extracted details — name, number, job, address, urgency — as structured data rather than a wall of text. That last bit matters more than it sounds: structured fields are what let the enquiry be scored, sorted, and dropped into a CRM automatically. A summary you have to re-read and re-type is a slightly nicer voicemail.

Done properly, the call ends and a qualified lead appears in the place you already work, tagged with enough context that you can decide in ten seconds whether to ring back now or at six.

What it does not do

It does not close the job. It does not replace judgment about which work to take. It does not know your van is off the road on Thursday unless something tells it. It will not build a relationship with a customer who has used you for fifteen years — and it should recognise that person and hand them straight to you.

It answers the phone, finds out what's needed, tells you clearly, and never sleeps. For most local service businesses, that is not a modest offer. That is the difference between the jobs you win and the ones that went to whoever picked up.


We run this as part of the bundle — the site, the phone, and the follow-up, one vendor. The service terms spell out disclosure, recording, escalation and excluded sectors in full. Or just get in touch.

Want this handled for you?

NPC Protocol builds your website, answers your phone when you can’t, gets you more Google reviews, and gets you found on ChatGPT.