📲 Live Transfer for AI Receptionists: Warm Transfer, Cold Transfer, and What Breaks on Real Lines

Warm transfer vs cold transfer

If a vendor cannot tell you what happens when nobody answers, assume a cold transfer.

How our transfer works, step by step

1. The AI understands the need and confirms it. "Loan department, is that right?" If the caller goes quiet, it re-asks once, then continues normally rather than transferring on a guess.
2. It checks the directory. A staff-editable list of people and departments with phone numbers or extensions, per-destination office hours and an on/off toggle. Municipal clients maintain about 50 entries themselves from the dashboard.
3. It dials the target on a second leg while telling the caller "one moment, connecting you". Sequential targets are tried in order, roughly 25 to 30 seconds each.
4. It bridges only on a real answer. This is the part that needs a PBX you control: the bridge happens when the far end picks up, not when the carrier says "answered".
5. If nobody answers, the AI resumes with the caller, takes a message, and creates a ticket with the recording and transcript for the destination.
6. Everything is logged: who was dialled, for how long, whether it bridged, and the outcome, visible in the dashboard.

A transfer that goes right, and one that does not

The second AI line is what a cold transfer never gives you. The caller is still on the line, their request is recorded, and someone will call back.

What breaks on real phone lines

We have hit all of these in production. Ask your vendor about each one.

• Carriers that fake-answer. Some trunks report "answered" the moment they play a recharge or unavailable announcement. The bridge then connects your caller to a recording. Our fix: detect answer by audio and timing, not by the carrier's signal, and keep the AI's leg until a human speaks.
• Trunks that cannot dial out. Inbound-only accounts are common with Nepali providers. A transfer to a mobile number silently fails. Test an outbound call to a real phone before launch.
• Extensions that were never registered. A softphone extension in the directory that nobody logged into rings nothing. The directory shows registration status so staff can see it.
• Office hours in the wrong time zone. Set per destination, in the office's local time, with holidays.
• The caller's own silence. A confirmation question followed by silence should be re-asked once, not treated as "yes".
• Transfers that strip the context. The person who answers should see or hear why the call came; otherwise the caller repeats everything and the AI looks useless.

Before the checklist, one test that takes two minutes and exposes most products: call the vendor's demo line, ask for a human, and then do not answer the phone that rings. What the AI says next tells you whether the transfer is warm, whether a message is taken, and whether anyone will ever see it.

Checklist for choosing a live transfer service

1. Is the transfer warm (bridged on answer) or blind?
2. What exactly happens when nobody answers, after hours, or on a busy line?
3. Can my staff edit the destinations and hours without calling the vendor?
4. Does it transfer to mobile numbers, SIP extensions and existing PBX queues?
5. Does the receiving person get the transcript or an announcement?
6. Is every transfer attempt logged with its outcome?
7. Can I test it on my own number before paying?

Where it is running

Warm transfer with a staff-editable directory runs on municipal helplines in Nepal, where officials are dialled within their office hours and callers get a message taken otherwise, and in the bank front-desk persona that routes account, loan, card and remittance requests by department. The behaviour is the same on every line: confirm, dial, bridge on a human, otherwise message and ticket. Details on the government and banking solution pages.

Transfer rules we recommend, by industry

Two universal rules: an explicit "I want a human" is honoured immediately during staffed hours, and the AI never claims it transferred when it did not.

Cost

Transfer is part of the receptionist, not an add-on. The call is billed per minute of AI talk time ($0.03 to $0.06); the bridged leg to your staff is billed by your carrier at its normal rate. Agent desks for staff softphones are a small monthly add-on. See the pricing page, or call the demo line and ask for a human to see the hand-off yourself.

Frequently Asked Questions

What is the difference between warm and cold transfer?

A warm transfer keeps the caller with the AI while it dials, and connects only when a person answers; otherwise it takes a message. A cold transfer forwards the call blindly and drops off, so an unanswered transfer ends in voicemail or silence.

What happens if nobody answers the transfer?

The AI returns to the caller, explains, takes a message with the details, and creates a ticket with the recording for the destination. Outside office hours it never dials; it says when the desk reopens.

Can it transfer to mobile phones as well as extensions?

Yes, to mobile numbers, SIP extensions and existing PBX queues, in a sequence you define, provided the trunk can dial out, which we test before launch.

Can my staff change who calls go to?

Yes. Destinations, office hours and on/off toggles are a table in the dashboard that staff edit; changes apply on the next call.

Does the person receiving the call know what it is about?

Yes. The transcript and the reason for transfer are attached to the ticket, and the AI can announce the caller before bridging.

Can the AI announce the caller to my staff before connecting?

Yes. When the person answers, the AI can state who is calling and why before bridging, and the transcript is attached to the ticket, so the conversation continues instead of restarting.