TryGTM is live.See it

Find out what happens when the transfer rings out

7 min read

By Lumina Software

  • Voice agents
  • Reliability
  • Service business
  • Call handling

Most phone agents for service businesses have a moment where they hand the call to a person. The caller has a gas smell, or wants to talk about a bill, or just keeps saying "can I talk to someone." The agent says "let me transfer you," and the call rings through to the office, a manager's cell, or an on call tech.

Then what? On a lot of setups, nobody has ever checked. The transfer rings six times and drops into a personal voicemail box that nobody listens to. Or it bounces back to the main line, where the agent picks up again and starts over from "thanks for calling." Or it simply ends. The caller who asked for a human because their problem was urgent now has the worst version of the experience, and they had it at the exact moment it mattered most.

This post covers how to find out what your transfer actually does when no one answers, and how to make that path safe.

Why the unanswered transfer is the one to test

Transfers are tested when the system is set up. Someone calls in, asks for a person, and their own phone rings. It works, so it gets checked off.

That test happens during business hours, with the person who set it up holding the phone and expecting the call. Real transfers happen at 7:40 in the morning when the office manager is driving, at lunch when the front desk is empty, and on a Saturday when the on call tech is under a house. The test proved the call can reach a person. It did not prove anything about what happens when the person is not there.

The calls that get transferred are also not a random sample. They are the ones the agent could not or should not handle: emergencies, angry customers, billing disputes, anything outside its rules. A dropped call on a routine booking is annoying. A dropped call on a water leak is a lost customer and sometimes a damaged house.

Call it yourself and let it ring

The fastest way to learn what happens is to try it.

Pick a time when the person on the receiving end of the transfer agrees not to answer. Call the main line from a phone that is not in the system, ask the agent for a person, and let the transfer ring out. Do not hang up early. Stay on until the call ends on its own.

Write down exactly what you heard:

  • How many rings before anything changed.
  • Whose voicemail greeting played, if any. A personal greeting like "you've reached Mike's cell" tells the caller they reached the wrong place.
  • Whether you could leave a message, and where that message went.
  • Whether the call came back to the agent, and what the agent said when it did.
  • Whether anyone got a text, email, or alert that a transfer had been missed.

Then do it again for every transfer target. Most businesses have more than one: the office line, an after hours number, an emergency on call number, maybe a billing contact. Each one can fail differently, and each one has its own voicemail settings.

Decide what should happen instead

Once you know what the failure looks like, decide what it should look like. There is no single right answer, but there are a few reasonable patterns.

Fall back to a second person. If the first transfer target does not pick up within a set number of rings, try the next one. This works well for emergencies, where a backup on call person exists anyway. It needs a clear order and a limit, so the caller is not passed around for five minutes.

Return the caller to the agent with context. If nobody answers, the call comes back to the phone agent, which tells the caller plainly that no one is available right now, collects the details, and promises a callback within a stated time. The key is that the agent knows the transfer failed. An agent that greets the caller again as if the call just started makes things worse.

Take a message to a shared place. If the call does go to voicemail, it should be a box the business controls and checks, not someone's personal cell greeting. The message should land somewhere more than one person can see it.

Alert someone either way. Whatever the fallback is, a missed transfer should produce a notice to a person: a text to the manager, a message in the team channel, a flag on the job board. A missed transfer that nobody hears about is the real failure. The caller may have left a message, but if no one knows to look, it sits there.

For true emergencies, decide in advance whether the agent should ever give up on reaching a person. Some businesses want the agent to keep trying the on call list until someone answers. Others want it to give the caller a clear instruction, such as calling the gas company or 911, and then alert the team. Write that decision down so the agent follows it the same way every time.

Set the timing on purpose

Two numbers control most of this, and they are usually left at whatever the phone system defaulted to.

The first is how long the transfer rings before it is treated as unanswered. Cell phones send unanswered calls to the carrier's voicemail after a delay that depends on the carrier and the phone's settings, and that voicemail can pick up before your fallback ever runs. If your fallback is set to trigger after 30 seconds and the cell's voicemail grabs the call sooner, the fallback never happens. The caller hears a voicemail greeting instead. Set the transfer timeout shorter than the shortest voicemail pickup among your targets, or turn off carrier voicemail on numbers that are only used for transfers.

The second is the total time a caller can spend being transferred before the system stops trying. If you fall back through three people at 20 seconds each, that is a minute of ringing, plus the time to explain each handoff. That might be fine for an emergency line. It is too long for a billing question. Set a ceiling per type of call.

Make the callback promise real

When the agent tells a caller "someone will call you back," that sentence is a commitment the business made. It needs an owner.

The record of the missed transfer should include who called, the number to call back, what they needed, and when they called. It should go to a list someone works through, with a time by which each item is handled. If the agent promises a callback within an hour, someone has to actually be watching for those during the hours the promise applies. If no one can do that after hours, the agent should promise something it can keep, like a call the next business morning.

Check this list weekly. Look at how many transfers were missed, how many got a callback, and how long the callbacks took. A rising count of missed transfers usually points to a staffing gap or a transfer target that changed numbers without anyone updating the system.

Retest when anything changes

Transfer paths break quietly. Someone gets a new cell number. The on call rotation changes. The office switches phone providers. A manager sets up a new voicemail greeting. None of these show up as an error in the phone agent. The agent keeps transferring to a number that no longer behaves the way it did.

Put a short unanswered transfer test on the checklist for any of these changes, and run it once a month even if nothing changed. It takes a few minutes per target.

The short version

Your phone agent probably transfers callers to a person for the most important calls it gets, and most setups have only tested the case where that person answers. Call in yourself and let each transfer ring out so you know what callers hear. Choose a fallback for each target: a second person, a return to the agent with context, or a shared voicemail box, and make sure every missed transfer alerts someone. Set the ring timeout shorter than the carrier voicemail pickup. Give every callback promise an owner and a deadline. Retest whenever a number, schedule, or phone provider changes.

Written by Lumina Software. Have a question? Book a call

Keep reading