What the AI should do when a caller says "I want to speak to a person"

The short answer

When a caller says "I want to speak to a person", the AI agent's job is simple: hear the request, confirm it in one sentence and hand the call to a human. If nobody is available right now, say so honestly and offer a real alternative: record the request and state when someone will call back. The agent must not hold the caller with "tell me first, maybe I can help" again and again.

One short offer is fine — "Of course, I'll connect you. If you tell me the topic briefly, my colleague will be ready" — but if the caller insists a second time, the call must be handed over unconditionally. Hiding the route to a person saves agent time in the short term and loses the caller's trust in the long term.

Why callers ask for a person

• Past experience: they have been sent round in circles by automated systems
• The question is complex or personal, and they do not want to explain it
• They are already frustrated — the problem has gone unsolved for a long time
• The agent has misunderstood them twice
• They simply prefer talking to a person

None of these reasons means "the caller is wrong". Each one points either to the process or to the agent's coverage. That is why it is worth tracking "asked for a human" calls separately: their reasons show what the agent needs to improve.

How to recognise the request

Callers phrase the request in different ways: "operator", "a person", "a member of staff", "a real person", "let me talk to a manager", "I don't want to talk to you". Sometimes they do not say it directly but it is clear: "is this a robot?", "put me through to someone". The scenario needs a list of these phrases, tested in the caller's language. With indirect phrases, be careful: if in doubt, the agent can ask briefly — "Shall I connect you with a colleague?"

Response script: a person is available

1. 11. Confirm"Of course, I'm connecting you with a colleague."
2. 22. One offer (optional)"If you tell me the topic briefly, I'll pass it on so you don't have to explain again." If the caller declines, go straight to step 3.
3. 33. Hand overThe call passes to an operator, with the collected details and summary.
4. 44. About waitingIf there will be a wait: "There may be a wait of a few minutes" — no figure unless it is real.

Response script: nobody is available

At night, at weekends or when every operator is busy, the agent must not hide the situation. Saying "I'm connecting you" and handing the call to an empty line is the worst option.

1. 11. Honest explanation"Our staff aren't working right now; they start at 9 a.m."
2. 22. Alternative"Shall I note your topic and number so they contact you in the morning?"
3. 33. RecordName, number, topic and preferred time are written down.
4. 44. Offer of help"In the meantime, if you have a general question, I can answer it." — not compulsory.

The no-hiding rule

Some companies deliberately make the route to a person harder to reduce operator load: the agent "does not understand" the request or says "tell me first" three times. In the short term operator calls fall, but callers complain in other channels, post on social media and call again. On top of that, the agent's real performance is hidden — some calls that look "resolved" are really callers who hung up.

A healthy rule: once a request for a human has been made twice, handoff is unconditional. This rule should be written into the scenario and checked in every test cycle.

When one offer is acceptable

An agent saying "maybe I can help" can be useful for the caller — if the question really is simple and the wait for an operator is long. For example: "There's a wait of about 5 minutes for a colleague. If it's about opening hours or the address, I can tell you straight away." Here the choice stays with the caller and the information is honest. The offer is made once.

Illustrative example: two versions

Not real calls. The bad version: the caller says "operator", the agent asks "How can I help you?"; the caller repeats it, and the agent replies "Please tell me your question first"; the third time the caller hangs up, and half an hour later writes a complaint on Instagram.

The good version: the caller says "operator", the agent replies "Of course. If you tell me the topic briefly, I'll pass it to a colleague"; the caller says "a payment problem"; the call passes to an operator with a summary, and the operator opens with "Hello, you're calling about a payment, is that right?" The difference is ten seconds; the difference in the caller's impression is large.

How the operator should take the call

On a call that came through a request for a human, the caller is often already somewhat annoyed. The operator's first sentence should take that into account: confirm the details the agent collected, do not make the caller explain again, and apologise for any wait. Operator comments like "the bot couldn't help you?" make the caller's impression worse.

What to measure

• The share of calls with a request for a human — and its weekly trend
• Time and number of steps from the request to the handoff
• The share of callers hanging up after asking for a human
• The reasons behind the requests — which topic or agent error led to them
• The share of promised callbacks made on time

The share of requests for a human should be read as a diagnostic source, not as a failure score for the agent. Making the route harder to cut the share improves the metric but worsens the service.

Common mistakes

• Not recognising the word "operator", or recognising only one form of it
• A long list of questions after the request for a human
• Saying "I'm connecting you" out of hours and handing over to an empty line
• Not passing the collected details to the operator
• Promising a callback and assigning it to no one

Limits

Because of audio quality and accents, the request may not be recognised every time; so expand the list of indirect phrases using real calls. In some sectors a customer's right to speak to a person may be regulated by law — check with a lawyer. This article describes industry practice.

Handing over to a person in Vexvon

In Vexvon AI Call Center, when a question gets difficult or the caller insists, the call passes to a live member of staff; the agent's behaviour and the handoff cases are written in the scenario. After the call, the transcript, summary and extracted fields land on the customer card, so the operator can see what was said beforehand. For out-of-hours times, a night scenario is set up with routing rules: the agent records the caller's number and request, and the team sees it in the panel in the morning.

The technical modes of handoff are covered in AI-to-human call handoff, and which call types never go to the agent in when not to use an AI voice agent.

First step

Call your own line three times and ask for a person in a different way each time: "operator", "I want to speak to a person", "put me through to someone". Note how many steps it took to reach a human and what you heard out of hours. More articles are in the human handoff & CRM section; to review your scenario together, get in touch.