Using Call

Handing a Call from the AI Agent to a Person: A Guide

How to design a clean hand-over from an AI phone agent to your team: when to hand over, who rings, warm or cold transfer, out-of-hours fallbacks and follow-up.

Call editorial team · Published · 6 min read

The moment a call passes from an AI agent to a person is where customers decide whether the automation helped or got in the way. If the hand-over is smooth, the caller barely notices; the person already knows the name and the reason for calling. If it is clumsy, the caller repeats everything, waits in silence or is cut off.

A support team member picking up a transferred call at a shared desk
Illustrative image

This guide covers when to hand over, who should pick up, how to prepare the person, and what to do when nobody is there. It complements IVR versus an AI voice agent, designing the way out of a phone menu and setting up your AI agent.

When the AI should hand over

Write the triggers down. An agent with no rules either hands over too often, which defeats the point, or too late, which frustrates callers.

Reasons to hand over

  • The caller asksAny request for a person should be honoured promptly, in everyday words such as "someone" or "a person".
  • Outside the agent's scopeA decision, an exception or a topic it has no answer for.
  • Repeated misunderstandingTwo failed attempts to understand the caller is enough.
  • Distress or urgencyAn upset caller, an emergency or a sensitive matter.
  • High value or high riskCases your business wants a person to own.

Of these, the first is not negotiable. A caller who asks for a person and does not get one will remember it. You can try once to help, for example by offering to take a message, but do not argue.

Designing the hand-over

A good hand-over has four parts: the decision, the connection, the context and the fallback.

Anatomy of a good hand-over

  1. DecideThe agent recognises a trigger and tells the caller what is happening.
  2. ConnectThe call rings the right people for the line at that time.
  3. Pass contextThe person sees who is calling and why, or hears it first.
  4. FallbackIf nobody answers, the caller is offered a callback or a message.
  5. RecordThe call, summary and outcome are saved for the team.

Tell the caller what is going on: "I will put you through to a colleague now." Silence while a transfer happens feels like a dropped call, and callers may hang up. If there is a wait, say so, and say what the options are.

Warm versus cold transfers

A cold transfer connects the call straight away. A warm transfer lets the person hear who is calling and why before they are connected. Each has a place.

Warm and cold transfers

Warm transferCold transfer
What the person hears firstWho is calling and what they needNothing; they pick up the call
SpeedA few seconds slowerFastest
SuitsComplex, sensitive or high-value callsSimple requests and routine calls
RiskA longer wait for the callerThe person starts without context
Caller experienceFeels organised; less repetitionFeels quick, but may involve repeating

Deciding who picks up

The strongest script fails if the wrong phone rings. Think about hours, skills and the number of people. Keep the list small: everyone on it will be interrupted.

In Call, you can see each phone line and who would ring right now: whether your AI agent answers, whether the line is in business hours and who would be put through, marked as reachable in the browser, by phone or not reachable now. Everyone chosen rings at once; the product has no shift rotation, priority, tag or team routing. For each line, transfer targets list the people and numbers the AI puts callers through to, with their own hours, and whether the transfer is warm or cold. A line can have up to ten targets, and outside every target's hours the AI does not transfer, so make sure the fallback exists.

When nobody is available

The usual cause of bad hand-overs is not the hand-over but the empty office. Plan the fallback before you need it.

Fallback checklist

  • The agent says plainly that nobody is available right now
  • It offers a callback or to take a message
  • It captures a name, a number and the reason for calling
  • It confirms what will happen next and roughly when
  • The request lands somewhere a person will see it
  • The business-hours settings match what the agent says

In Call, a caller who asked for a person is listed as a request in the help desk, with the result (for example asked for a person or nobody answered), what the caller said and, for a callback request, a summary, the preferred time and the language. A person can take it, assign it, add a note, call back or add the caller to the callback queue, and resolve it. See call-back requests and help desk tickets.

What the AI should say

Words carry a lot of weight at the moment of transfer. Short, honest sentences work well, and they should match what really happens next.

SituationWeak wordingBetter wording
Caller asks for a person"I will try to help you with that first.""Of course. I will put you through to a colleague now."
Putting throughSilence while the call rings"One moment while I connect you; I will tell them why you are calling."
Nobody free"Please try again later.""Nobody is free right now. Shall I take a message so someone calls you back?"
Outside hoursThe call ends"We are closed. I can take your details, and we will call you when we open."

A good rule is to promise only what the system will do. If the agent says someone will call back today, make sure the callback request is seen today. Saying "soon" is safer than a specific time you cannot keep.

Sensitive and urgent calls

Some calls should skip the usual flow. If your business can receive emergencies, such as a medical practice or a utility, decide in advance what the agent says and does when it hears one. The wording should point the caller to the proper emergency service, not to a queue. A hypothetical veterinary clinic might have the agent say that for an emergency the caller should phone the emergency vet directly, and then offer to put them through if someone is on duty. Plan these cases with your team and test them regularly.

Learning from handed-over calls

Every hand-over is a small signal. Each one means the agent could not or should not continue. Review them weekly: which topics trigger the most, which callers ask for a person immediately, and which hand-overs ended without an answer.

  1. List the topics behind the last month of hand-overs.
  2. Add answers to the knowledge base for the ones the agent should have handled.
  3. Keep hand-over for topics that really need a person.
  4. Check how many requests were resolved and how long they waited.
  5. Run a practice batch to test the changes; see practice calls.

The aim is not zero hand-overs. It is that the right calls reach a person quickly, with context, and the rest are handled well without one.

Frequently asked questions

Should the AI try to keep a caller who asks for a person?

Not for long. You can offer once to help or take a message, but a clear request for a person should lead to a hand-over or a recorded request.

What is the difference between warm and cold transfers?

In a warm transfer the person hears who is calling and why before connecting. In a cold transfer the call is put straight through. Warm suits complex or sensitive calls.

What happens when nobody answers?

The caller should be offered a callback or a message. In Call, the request appears in the help desk with the caller's words, so someone can call back.

Can I set different people for different hours?

Yes. Transfer targets have their own hours. Outside every target's hours the AI does not transfer, so plan a fallback for those times.

Do all chosen people ring one after another?

No. In Call, everyone chosen rings at once. There is no shift rotation or priority order.

How can I check who would ring right now?

The help desk shows, for each line, whether the AI answers, whether the line is open and who would be put through at that moment.

Set who picks up when callers ask for a person in Call

In the demo console you can try incoming calls in a simulation.

Related guides