Most AI-to-human transfer failures are not AI problems. They are phone-route problems that nobody tested. In one deployment, a Telugu booking assistant that transfers callers to one of several receptionists worked perfectly on one telephony route and silently failed on another because of a missing setting. The agent retried the transfer, the caller heard silence, the call dropped. The failed transfers weren't even logged as transfers, so the pattern was invisible until someone listened to calls. Here is what we learned.
Test transfers on your own number: Start free on Edesy — Rs 50 free credit, no demo needed.
The setup
- An AI booking assistant answering and making calls in Telugu.
- Several named transfer destinations: different receptionists for different needs.
- Two telephony routes in use for different numbers.
Transfers on route A worked. On route B, the configuration that allows a call to be transferred was missing. The AI did what it was told: tried to transfer, waited, tried again.
What callers experienced
- The agent said "I'll connect you to our receptionist."
- Silence.
- The agent tried again.
- More silence, and then the call dropped.
From the caller's side, the business hung up on them.
Why nobody noticed
- Failed transfers weren't recorded as transfers. They looked like short, completed calls.
- Testing had been done on route A only.
- No one listened to route-B calls in the first days.
The fixes
1. Test every route, every destination
Before go-live, place a test call through every number and telephony route, and transfer it to every destination, during the hours you'll run live. Check:
- The caller hears a short announcement before the transfer.
- The receptionist's phone actually rings and connects.
- The call record shows the transfer and its outcome.
2. Log failed transfers as their own outcome
A failed transfer should be a separate, visible outcome in the call log and reports. Review it daily in the first weeks.
3. Give the agent a fallback
When a transfer fails, the agent should not retry endlessly. Instead:
I'm sorry, our receptionist isn't available right now. Can I take your number and a short message? Someone will call you back within {{callback_window}}.
Then create a callback task and, if you use it, send a WhatsApp message confirming the callback.
4. Always speak before transferring
A short line before the transfer ("Connecting you to our billing team now") avoids silence and tells the caller what is happening. See how to fix dead air on AI calls.
Designing transfer rules
| Caller need | Destination | If unavailable |
|---|---|---|
| New booking, complex case | Front desk | Callback within 30 minutes |
| Billing | Billing desk | Message + callback next working hour |
| Complaint | Supervisor | Message + callback same day |
| Emergency (clinics) | On-call number | Give emergency number immediately |
On Edesy, the agent transfers to named destinations with a short announcement. Keep the list short and the descriptions clear, so the agent picks the right one.
For hospitals and clinics
Transfers matter most in healthcare, where callers may be anxious or unwell. See AI night receptionist for hospitals and 20 questions clinics ask before buying an AI receptionist.
Try it
Create a free account, set a transfer destination to your own mobile, and test it before you connect real callers. Need help checking your routes? Talk to us.