A caller has told your AI receptionist what is wrong. The AI says, "Let me connect you with someone." The line rings, nobody picks up, and the caller lands in a generic voicemail box. They hang up and call your competitor.
Handing a live caller to a human is four decisions: whether to try a transfer at all, what the human hears first, what the AI says when the transfer fails, and what promise you make instead.
Try a transfer only when someone can actually answer
A live transfer is worth it when speed changes the outcome and a person is ready to take it. Write that down as rules, not as a feeling.
For a roofing company, that means an active leak or a homeowner whose estimator is already on the way. For a freight brokerage, it means a carrier calling about a covered load or a shipper with freight moving today.
Everything else is a callback. A quote request or a pricing question does not need a person in the next ninety seconds. It needs a person who calls back with the right information.
Then add the condition most teams skip. Do not offer a transfer outside staffed hours or when nobody is marked available. "Let me connect you" is a promise. If your phone system can report who is logged in, check that before the AI says the word "transfer." If it cannot, set a schedule and stick to it.
Decide what the human hears before picking up
The worst warm transfer is one where the human answers cold and the caller has to start over.
Platforms handle this differently, so read your vendor's docs. [Vapi's warm transfer documentation](https://docs.vapi.ai/tools/transfer-call/warm-transfer), for example, lists modes where the destination hears a fixed message or a generated summary, including modes that wait for the person to speak first. Those matter because a briefing played into a voicemail greeting helps nobody.
Keep the briefing short enough to say in about ten seconds. Fields worth including:
- Caller name and the number they called from - The reason for the call in the caller's own words - Address for a roofing call, or lane and equipment for a freight call - What the AI already told them and anything it promised - What it could not collect
Use a fixed template. A hypothetical example: "Dana Reyes, calling from 555-0142. Water coming through a bedroom ceiling since this morning. Address collected. Insurance not discussed. She was told you would pick up."
Write what the AI says when nobody answers
Transfers fail. The person is on another call, in a truck, or on a ladder.
[Twilio's documentation for its Dial verb](https://www.twilio.com/docs/voice/twiml/dial), for instance, reports an outcome of completed, busy, no-answer, failed, or canceled, and says the default ring time is 30 seconds. After a failed dial, the caller is still on the line and your flow decides what happens next. Write that part.
A workable script says plainly that you could not reach the person, confirms the callback number, gives a time, and says what to do if the call does not come. For example: "I couldn't reach Mike just now. I have your number as 555-0142 and I've passed along what you told me. Mike will call you before 3:30 this afternoon. If you haven't heard from us by then, call this number back and say your name."
Thirty seconds of ringing is a long silence, so test your ring time yourself. Do not say "someone will be with you shortly," and do not drop the caller into the main voicemail box. The AI already has the information voicemail would collect.
Set a callback window you can keep
"Shortly" and "as soon as possible" tell the caller nothing. A time of day tells them when to start being annoyed.
Set the window from your actual staffing, not your best day. Time your callbacks in the busiest hour and quote that figure. A window you hit nine times out of ten beats a faster one you hit half the time.
During staffed hours, give a clock time such as "before 3:30." After hours, give a morning time on the next business day, not "tomorrow." On a storm surge day, give a longer window and say why.
Every promised callback needs an owner, either a named person or a queue someone watches. If the window passes with no call, the record should alert a manager, not sit in a list.
If an automated voice might ever place your callbacks, talk to counsel first. In February 2024 the FCC ruled that calls made with AI-generated voices are "artificial" under the Telephone Consumer Protection Act, which brings consent rules into play ([FCC news release](https://docs.fcc.gov/public/attachments/DOC-400393A1.txt)). Confirm your setup with your own attorney.
Stop callers from bouncing between the AI and voicemail
The transfer fails and the caller leaves a voicemail. Nobody calls back fast enough, so they call again. The AI greets them like a stranger and asks the same questions.
Fix it with one record per phone number holding the transfer result, the callback deadline and owner, and whether the callback happened.
When the same number calls again, the AI reads that record first. A good reply: "I see Mike was going to call you back by 3:30. I'll try him again now." Make one more transfer attempt if someone is available. If not, flag the record as overdue, tell the caller who is chasing it, and skip the intake questions they already answered.
Treat voicemail as the last resort, and attach whatever lands there to the same record.
Test it by failing on purpose
Before launch, call your own number and let the transfer ring out. Call again from the same phone ten minutes later, then once after hours. Check what the caller heard, what the record says, and who got alerted.
After launch, watch weekly how many transfers get answered, how many callbacks land inside the window, and how many callers ring back within a day. If the last number is high, the handoff is broken.
If you want help setting the transfer and callback rules for an AI receptionist, [book a call with Chosen AI Solutions](https://chosenai.co/book).
Sources
- Federal Communications Commission. "FCC Makes AI-Generated Voices in Robocalls Illegal." News release, February 8, 2024. [docs.fcc.gov](https://docs.fcc.gov/public/attachments/DOC-400393A1.txt) - Twilio. TwiML Voice: Dial (timeout, action, and DialCallStatus). [twilio.com](https://www.twilio.com/docs/voice/twiml/dial) - Vapi. Configure warm transfer modes. [docs.vapi.ai](https://docs.vapi.ai/tools/transfer-call/warm-transfer)