Skip to content
Chleb AI

What should an AI receptionist do when the person it transfers to does not answer?

A handoff has two jobs: connect the caller to a person, and have a plan for when that person is busy, away or never picks up. A configured fallback is what covers the second job. According to vendor documentation, a busy or unanswered transfer can end the call outright unless you configure a fallback. Decide the fallback before you launch, then test every outcome with real phones: answered, busy, no answer, wrong number and voicemail.

How it works. By Chleb AI Editorial (AI-assisted). Published 2026-11-11. 7 min read.

Know which kind of transfer you are buying

Platforms use different names, but the split is between an immediate transfer and a transfer that has an acceptance or briefing step. Retell AI describes its cold transfer as sending the call straight to the destination while the agent drops off. Vapi's default blind transfer connects the caller without speaking to the destination first; the downstream result must be checked in the provider record.

Warm modes vary. Retell AI documents a warm transfer that can wait for a live person, brief the destination privately so the caller cannot hear, or introduce the caller in a three-way message; its internal-queue behavior requires the platform's queue and hold setting. Vapi's ordinary warm message, summary and TwiML modes brief the destination, while its assistant-based warm mode can keep the caller on hold and connect or cancel after the destination leg.

The practical difference depends on the selected mode: an immediate transfer may leave no assistant path when the attempt fails, while a mode that explicitly waits for or screens a person can apply a configured fallback. Warm or screening modes cost more setup and, on Retell AI, the agent bills at its normal rate while it stays on the line during hold and briefing, so ask what that does to your usage.

Find out what the system counts as answered

Your fallback only works if the system can tell the attempt failed. Twilio's Dial verb reports a status for each attempt: no-answer, busy, failed (for example a number that does not exist), completed, answered (conference only) and canceled. When you give Dial an action URL, Twilio requests that URL with the status of the attempt and continues the original call, so the instructions returned there can send the caller to voicemail or a message-taking step. Without an action URL, the next verb in the document runs.

Timing matters. Twilio's Dial timeout defaults to 30 seconds, with a minimum of 5 and a maximum of 600, and Twilio adds a five-second buffer. So a 10-second setting behaves closer to 15 seconds. Retell AI has a similar transfer ring duration that decides how long the destination rings before the attempt counts as unanswered.

Some results cannot confirm success. Vapi documents `assistant-forwarded-call` as an ended reason that does not confirm the destination answered or that the parties spoke. If the selected mode cannot tell you whether anyone picked up, it cannot trigger a sensible fallback, so plan for that uncertainty.

One risk the documentation does not settle: a voicemail greeting on the destination phone may count as an answer. The Twilio Dial page does not say how voicemail on the called phone is treated or how to detect it, and this article does not claim to know. Do not assume it is handled. Test it with a real phone that has voicemail turned on, and note what the caller hears.

Write the fallback before you configure the transfer

Vapi's documentation says that on Twilio, Telnyx and Vonage numbers, a busy or unanswered blind transfer ends the call. On Vapi numbers and bring-your-own SIP trunks, a failed blind transfer returns to the assistant only when a fallbackPlan is configured. The default fallback message is 'Could not transfer the call.' With endCallEnabled set to false, the assistant can keep helping; when it is true or omitted, the call ends. Other providers and modes have their own behavior, so verify the setting on the production path. If you use Vapi, read the fallbackPlan section of its transfer call page for the exact fields before you build.

A good fallback is a short script that does three things. It tells the caller plainly that nobody is available right now. It offers a next step that does not need the person, such as taking a message with a name, number and reason for calling. It states what happens next, such as who will call back and roughly when, but only if your business can keep that promise.

Choose the fallback by call type. A routine question can become a callback request. A call that sounds urgent may deserve a different path, such as trying a second number before taking a message. Whatever you choose, write it down as the rule you are testing against. Do not promise an urgent-call guarantee unless your phone setup has been tested to deliver it.

Decide what the person receives when they do answer

A transfer that connects but leaves the person cold wastes the caller's time. Vapi states the destination does not receive the prior conversation context, variables or assistant context. Unless you configure a briefing, the person who picks up may have to start from scratch.

If your platform supports a briefing, keep it short and fixed in shape: caller name, reason for calling, and anything the caller asked for. Retell AI's whisper debrief is private to the destination, and its three-way message introduces the caller to the person. Pick one and test how it sounds on a real phone.

Also check caller ID. Vapi says caller ID depends on the phone provider, and that Telnyx and Vonage ignore a configured callerId. Retell AI says showing the caller's number needs provider support, and if it is not supported the transfer fails. If your team needs to see the caller's number to call back, confirm that behavior on your own carrier before launch, not from a feature list.

Finally, check the limits. Retell AI documents transfers for phone calls only, not web calls, and says custom SIP headers may be stripped when the destination is a regular phone number. If your plan includes a website chatbot or a web voice widget, the phone transfer path does not apply there, so decide separately how a web visitor reaches a person.

Run this test plan with real phones

Do this on your actual phone numbers and carrier, not in a simulator. Use at least two devices you control, one to call in and one to receive the transfer. Write down what the caller hears and what each log shows for every case.

  1. Answered: pick up on the first ring, confirm the caller is connected, the audio is clear and you hear any briefing you configured.
  2. Answered late: let it ring until just before your timeout, then pick up. Confirm the call still connects and nothing is cut off.
  3. No answer: let it ring past the timeout. Confirm the caller hears your fallback script, not silence and not the default failure message.
  4. Busy: have the receiving phone on another call. Confirm the same fallback plays.
  5. Voicemail: leave the receiving phone's voicemail on and let it answer. Note whether the system counts this as answered and what the caller hears.
  6. Wrong or disconnected number: use an isolated test configuration and a provider-documented invalid or test destination. Confirm you get a failed status and a sensible caller experience without changing the production route.
  7. Slow lookup: if the destination is chosen by a lookup, delay it on purpose. Vapi notes that a slow destination lookup plays nothing to the caller, so confirm the caller hears something or is told to hold.
  8. Caller ID: check which number shows on the receiving phone and whether your team can call it back.
  9. Logs: for each case, find the result in the call logs. On Vapi numbers and bring-your-own SIP trunks, check endedReason values such as call.forwarding.no-answer, call.forwarding.operator-busy and call.in-progress.error-transfer-failed, or the transfer result in call logs (connected, busy, no-answer, unconfirmed). On Twilio, check the Dial status. Vapi notes that no server message reports a failed phone or SIP transfer, so you may need to read logs rather than wait for an alert.

Worked example: a small plumbing office

Take a hypothetical plumbing office with one dispatcher and one owner. The goal is that a caller who asks for a person reaches the dispatcher, and if the dispatcher is unavailable the caller leaves a message that someone sees quickly.

Step one: choose a transfer mode that your platform documents as waiting for or screening a live dispatcher, with a short briefing that gives the dispatcher the caller's name and reason. Step two: set the ring time to 20 seconds. On Twilio, remember the five-second buffer, so the real wait is closer to 25 seconds. That is long enough for a dispatcher to reach a phone but short enough that the caller is not left wondering.

Step three: write the fallback. For example: 'Nobody is free to take your call right now. I can take your name, number and what you need, and the office will call you back.' Then the assistant collects those details and the office gets them through whatever channel it checks most often.

Step four: run the test plan. In this example, suppose the voicemail test shows the system treating the dispatcher's voicemail as an answered call. Treat that as a configuration problem to investigate with the provider. Possible remedies include changing the destination's voicemail behavior or choosing a mode that confirms a live person, if the platform supports it; then test again until the fallback plays when it should.

Questions to ask any vendor, including us

Use the questions below to compare vendors on the failed transfer, not just the happy path. Ask for answers in writing and ask to see them demonstrated on your own phone number.

For Chleb AI specifically, the public product pages describe an AI receptionist and website chatbot for service businesses, based in Tampa, Florida. The CRM is a separate published plan unless the Front Office Bundle is selected. This article does not claim any particular handoff, fallback or urgent-call behavior for Chleb. Ask about transfer behavior on a call, and verify it against the live product before you rely on it.

  • Is the transfer cold or warm, and does the AI stay on the line if the attempt fails?
  • What exactly counts as answered, and how does the system treat a voicemail greeting?
  • What does the caller hear on busy, no answer and failure? Can you change it?
  • Is the ring time adjustable, and does the real wait include a provider buffer?
  • What does the person who answers see or hear about the caller before they speak?
  • How is caller ID handled on my carrier?
  • Where do I see the result of each transfer attempt, and what are the status names?
  • What is not supported, for example web calls or certain carriers?
  • What happens to the message if the caller leaves details after a failed transfer, and where does it go?

Related reading

Sources

How this article was made

Written with AI assistance. Every factual claim links to its source above. Illustrations are AI-generated, not photographs; cover cards are set in type; charts and diagrams are built from the public data they cite. This is general information, not legal, financial or tax advice. Found an error? Tell us at chleb@chleb.ai or through the contact page and we will correct it and note the correction on this page.

More stories

All stories

Questions readers ask

What happens if nobody answers an AI receptionist transfer?

It depends on the setup. Vapi's documentation says a busy or unanswered blind transfer ends the call on Twilio, Telnyx and Vonage numbers, and on Vapi numbers and bring-your-own SIP trunks the caller returns to the assistant only if a fallback plan is configured. Check this for your own platform and test it.

Is a warm transfer always better than a cold transfer?

Not always. Some warm or screening modes keep the caller on hold while they wait for or brief a person; other warm modes only play a message or summary before connecting. It takes more setup, and on Retell AI the agent bills at its normal rate while holding or briefing. Test the selected mode against your own call patterns.

How do I know whether a transfer failed?

Look at the call logs. Twilio reports statuses such as no-answer, busy and failed for each Dial attempt. Vapi notes that no server message reports a failed phone or SIP transfer, so check endedReason values and the transfer result in the logs. The assistant-forwarded-call ended reason does not confirm that the destination answered, so check the provider record.

Book a demo