What happens when an AI receptionist call transfer fails

It's 2:40 on a Thursday. Two vans out, both plumbers under somebody's sink, and a woman rings because there's water coming through her kitchen ceiling. The AI picks up on the first ring. It takes her postcode, works out that this one is urgent, and says exactly the right thing: "I'll put you through to someone now."

Then it dials the owner's mobile. He's kneeling in a stranger's bathroom with wet gloves on. His phone rings in his pocket. Three rings, four, five, and his carrier's voicemail answers on his behalf.

She hears "Hi, you've reached Dave, leave a message after the tone." She doesn't leave one. She rings the next plumber on the results page.

Nothing failed in the way the demo warned you about. It understood her, qualified her, and did what it was told. The handoff lost the job.

The conversation is the easy part

When you're assessing one of these systems, you listen to the conversation. That's reasonable. It's the part that was impossible three years ago and works now. We've written before about what an AI receptionist can and cannot do on a call, and the short version is that the talking is mostly a solved problem.

The transfer is not. A transfer is the moment the call leaves software you can inspect and enters three systems you don't control: your phone provider, whichever mobile network your engineer happens to be standing on, and the voicemail box sitting behind their number. Nobody demos that. You can't demo it, because it only misbehaves when someone is busy, and nobody is busy during a sales call.

Every vendor page lands on the same promise in slightly different words. If the agent can't help, it escalates to a human. Fine, but the human is up a ladder, in a loft, or on the A34, and that case decides whether the feature is worth anything.

Your carrier decides how long the phone rings, and it's shorter than you think

Here is the number that quietly breaks most setups. An iPhone hands an unanswered call to voicemail after about 20 seconds by default, and across networks the window generally sits between 20 and 30 seconds, which is roughly three to six rings (SlashGear has the handset and carrier detail). Some networks let you lengthen it. Some won't let you touch it at all.

That timer doesn't belong to you, and it doesn't belong to your AI either. It belongs to the network, and it starts the second the transfer connects.

So picture the configuration nearly everybody writes on day one. Ring Dave for 30 seconds. If Dave doesn't answer, ring Mo. If Mo doesn't answer, take a message.

Mo never gets rung. Dave's voicemail answers at twenty-something seconds, the network reports the call as answered, and as far as the phone system is concerned that transfer succeeded. Your escalation ladder has three rungs. Callers only ever reach the first one, and on a busy day the first one is a recorded greeting with Dave's name on it.

Set the window per rung at 12 to 15 seconds instead. Two or three rings. Short enough that the agent is still holding the call when it decides to give up.

You'll pay something for that. Now and then you'll cut off a person who was reaching for their phone and would have answered on ring five, and they'll be mildly irritated with you. Take the trade anyway. An agent that gave up early can try the next name on the list. A voicemail box can't do anything at all.

We could drop a statistic in here about how many callers who hit voicemail never ring back. The famous one is 85 percent, it appears in nearly every article on this subject, and it traces back to an uncited vendor blog post from 2016 (one of the few round-ups honest enough to say so). So we won't use it. You don't need it. Open your voicemail box on a Monday morning, count the messages, then count how many of them turned into work.

Cold transfer, warm transfer, and the one that can come back

There are three shapes of handoff. Only one of them survives a no-answer.

Cold transfer. The agent connects the caller to a number and drops off the call. Nothing added, no hold, and the caller repeats the whole story to whoever picks up. Once the agent is gone it has no idea what happened next. Voicemail, engaged tone, an answer: all identical to it, which is to say invisible.

Warm transfer. The agent parks the caller, dials your engineer, says two sentences about who's waiting and why, then bridges the two together. It costs the caller roughly ten seconds of hold. It buys the engineer a name, a postcode and a reason before they open their mouth.

The agent stays on the line. This is the one worth asking about. The agent remains a participant in the call rather than a step that hands over and exits. It hears the ringing. It hears the voicemail greeting start, and it can come back to the caller still holding everything she already said. "Dave's on a job and can't get to the phone. I can have him ring you back within the hour, or I can book you the first slot tomorrow at half seven." That's a recovery. The other two are a dead end with better manners.

One question sorts the vendors quickly. After a failed transfer, can the agent rejoin the call and carry on talking? A straight answer means somebody has thought about it. An offer to follow up by email means no.

Five things to write down before you turn transfers on

1. The ring window for each person. In seconds, measured against that person's actual handset and network rather than assumed from the default.
2. The order of the ladder, and the bottom of it. Who gets rung second, who gets rung third, and what happens once the last rung fails. That final step is the one people leave blank, and it's the only one that runs on your worst day.
3. What the caller hears while the agent dials. Twelve seconds of silence sounds like a dropped call. Either the agent keeps talking or something plays.
4. The failure script, word for word. Not the sentiment, the sentences. What the agent offers when nobody picks up, and whether the business can honour it. A callback promise you can't keep does more damage than no promise, for the same reason speed of response decides who gets the job.
5. Where the record lands, and how fast. A text to a phone, number tappable, inside a minute. If the only trace is a row in a dashboard nobody has open, the lead is still lost. It's just documented now.

The test takes ten minutes and you should run it at 4:50 on a Friday

Ring your own main number from a mobile the system has never seen. Ask for something the script doesn't cover so the agent has to escalate. Then put the phone face down on the desk and leave it there.

Time the rest with the clock on your laptop. How many seconds before the agent gives up. Whether it tries anybody else. Whether it comes back to you or leaves you sitting in silence. Whose voicemail greeting plays, if one plays at all, and what that greeting tells a stranger about the business.

Then check the far end. Did a text arrive, and how long after. Did the lead reach the CRM with the postcode and the reason attached, or only a call duration. Is there a transcript you could read tomorrow.

Run it again at twenty to seven in the evening, and once on a Saturday morning. Coverage on a Tuesday afternoon tells you almost nothing. Tuesday afternoon isn't when you're losing the work.

Where a transfer is the wrong thing to offer

Two cases, and we'd rather say them out loud than sell a feature you can't use.

If you're a one person business, your ladder has one rung and that rung is you, on a roof. Dressing it up in a transfer flow is theatre. The honest build is an agent that never promises a transfer at all: "he's on a job until about five, I'll get him to ring you before six." Then you make that true. It's a worse demo and it loses fewer jobs.

The second case is real emergencies. A warm transfer's consult leg costs ten seconds of hold, and ten seconds is a long time when there's a gas smell or water coming through a light fitting. For those intents we switch the warm handoff off and transfer cold, straight to a number somebody always answers. That only works if such a number exists. If your out of hours plan is a mobile that gets picked up when somebody feels like it, no routing logic repairs that, and we'd be taking money to paper over a rota problem.

What to do this afternoon

Ring your own number and don't answer the transfer. Whatever you hear next is what every caller hears on the day you're busiest. Most owners have never once heard it.

If what plays is your own voicemail greeting, the fix is usually an afternoon: shorter ring windows, a second name on the ladder, and a failure script that books something instead of apologising. That's the work, and how we scope it is on the front page. Tell us what your callers hear and we'll tell you what we'd change first.