Transferring Calls From an AI Agent to a Human: When to Transfer and How to Set It Up

Transferring a call from an AI agent to a manager means handing a live conversation to a person within the same call: the caller doesn't hang up or wait for a call back, and the manager joins with the context of the conversation. A good transfer does three things: it happens at the right moment, it reliably reaches an available person, and it doesn't make the caller repeat their story. Below: when to transfer, the technical options, and how to set things up so that no calls get lost.

• Every rollout needs a transfer: on average about 20% of callers on an inbound line ask to speak to a person (Sales Workshop data).
• 83% of consumers still have to repeat themselves at least sometimes after being transferred (Five9, 2026) — so the context has to travel with the call.
• There are three technical ways to transfer: a dial-out through the platform's PBX, a cloud PBX transfer code (DTMF) and SIP REFER. The last two show the manager the caller's real number.
• A transfer needs a backup plan: a queue of several managers, a fallback dial-out and a fast call back if nobody answered.

When an AI agent should transfer a call

A transfer isn't the agent admitting defeat — it's a normal part of the conversation. Calls are usually transferred in five situations:

The Sales Workshop agent transfers the call when the caller asks for a person or is ready to discuss a deal. Other rules — which topics go straight to a specialist, what the agent never discusses — are set in its script and restrictions. Don't try to hold on to someone who asks for a person: in Gartner's survey, customers' top concern about AI in customer service is that it will become harder to reach a human, and Gartner explicitly recommends telling customers they'll be connected to an agent if the AI can't help.

Cold vs warm transfer

Contact centres distinguish two kinds of transfer. In a cold (blind) transfer, the call is simply switched to another employee, who starts from scratch. In a warm transfer, the first agent briefly fills the colleague in before connecting the caller. Cold is faster; warm spares the caller from repeating themselves.

An AI agent combines the best of both: the call is switched right away, with no verbal briefing, and the manager gets the context in writing. During the conversation the agent fills in the lead card — name, phone number, needs, budget — and after the call it holds the recording and a summary: what was discussed, what objections came up, how ready the customer is to buy and what to do next. Hot leads also trigger a Telegram notification.

Three technical ways to transfer a call

The transfer method is chosen in the telephony channel settings. It determines which number the manager sees and which PBXs the transfer works with.

If the PBX doesn't execute the code or the command, the platform automatically falls back to a regular dial-out: the call isn't lost, but the manager sees the line number. The caller's number matters for more than convenience: the manager knows who is calling, can call back directly, and the call lands correctly in the customer's history in the CRM through the PBX integration. For a step-by-step example with one cloud PBX — two extensions, a queue scheme for managers and a transfer code like #207#, where 207 is the queue extension — see our documentation.

How not to make callers repeat themselves

According to Five9's research (3,000 consumers in the US, UK and Germany), 83% still have to repeat themselves at least sometimes after being transferred. Repetition devalues the whole conversation that came before: the caller has already spent time with the agent and expects to be remembered. What helps:

• One line before the transfer. The agent briefly says: “I'm connecting you to a manager, please stay on the line” — no pauses, no repeated questions.
• The lead card is the first thing the manager opens. The agent fills in the name, request and qualification results during the conversation.
• The manager opens with a confirmation, not a question: “John, I see you're asking about delivery to another city — is that right?” instead of “Hello, how can I help?”.
• Transfer to the people who handle such questions. If you have several departments, set up the queue on the PBX side so the call reaches the right people and the caller isn't transferred twice.

What to do if no manager picks up

The worst failure is when a caller asks for a person, gets transferred, and nobody answers. It is solved at three levels:

• A queue instead of a single number. Transfer not to one manager's phone but to an extension with a queue scheme: the PBX rings managers in order with set timeouts.
• Out of hours. Outside working hours the agent shouldn't promise a live connection: it's better to offer a convenient time for a call back or book a meeting in the calendar, and pass the manager a lead card with the call summary.
• A fast call back on failed transfers. Call back within minutes, not hours: according to research published in Harvard Business Review, firms that contacted a potential customer within an hour were nearly seven times as likely to qualify the lead as those that made contact even an hour later. More on the cost of delay in our article on lead response time.

Transfer setup checklist

• Turn on the agent's “Call transfer to a person” tool and enter the operator number — ideally a queue extension rather than a manager's mobile.
• Choose the transfer method in the telephony channel settings: if the caller's number matters, use the cloud PBX transfer code (DTMF) or SIP REFER.
• Set up the queue on the PBX side: which managers take transfers, in what order, and how many seconds each one rings.
• Define the agent's behaviour: the line before the transfer, the “one clarifying question at most” rule and the out-of-hours scenario.
• Test with a real call: ask to “speak to a manager” and check that the manager sees your number and that the call reached the CRM.
• Review the stats weekly: how many requests for a person there were, how many transfers went through, and how fast failed ones were called back.

Metrics to track

Why callers ask for a person in the first place, and why the share varies so much by industry, is covered in How often callers ask for a human.

Bottom line

A transfer to a manager is as much a part of an AI agent as answering questions. It should trigger immediately when the caller asks or is ready to buy, go to a queue rather than a single phone, keep the caller's number and pass the context in writing so nobody has to repeat themselves. Then a request for a person stops being a risk of losing the customer. For the overall rollout of an agent on an inbound line, see our guide to AI agents for inbound calls.