What Is a Queue Callback?

What a callback is

Everyone knows it: you call for service, hear "All agents are busy," and stay with the phone glued to your ear for ten minutes. You can't drive, you can't talk to anyone else, and if you hang up — you start over.

A callback (also called a queue callback) solves this. A caller waiting in a queue hears an offer: "For a callback, press 1." They press, hang up, and go on with their business. Their place is saved, and when their turn comes, the system dials them by itself and connects them to an agent.

It's important to understand the difference from "Leave a message and we'll get back to you." With a voicemail message, someone has to hear it, write it down, and remember to call back. With a queue callback, nobody has to remember anything: the system itself dials, in order, the moment an agent is free.

How it works — for the caller

1. Enters the queue and hears an opening message and hold music, and from time to time their position in the queue.
2. After a set wait time — the offer is played: "For a callback, press 1."
3. If they pressed — they hear a confirmation that the request was received, and can hang up. The number they called from is the number that will be called back.
4. If they didn't press — they keep waiting as usual, and an agent answers when their turn comes.
5. When their turn comes — their phone rings, and they are connected to an agent.

Note a subtle point: the wait time after which the callback is offered is measured from the moment the caller enters the queue, and not from the start of the call. Someone who spent a minute in the voice menu shouldn't get the offer earlier just because of that.

How it works — for the agent

From the agent's point of view, a callback looks almost like any call from the queue. They become free, and the next call in the queue reaches them — except that this time it is the caller who asked for a callback, and the system dialed them.

Usually it's worth having the agent open with a sentence like "Hello, we're calling you back from the office, as you requested." The person answering sometimes forgot they asked, or an unfamiliar number confuses them. A fixed opening sentence saves the moment of confusion.

And what if the caller doesn't answer when called back? It depends on the system and the settings. In many systems it tries again after a few minutes, and if there is no answer then either — the request is closed. It's worth checking what happens in your setup and configuring accordingly.

Types of callbacks

The term "callback" is used for several different things, and it's worth telling them apart:

• Queue callback — The subject of this article. The caller is already in the queue, presses a key and hangs up, and their place is saved. The system calls them back automatically.
• Manual callback for a missed call — the caller makes no request. Someone sees in the call log or in an alert that a call went unanswered, and calls back. It works, but it depends on someone remembering.
• Callback request for a specific time — in some systems the caller chooses when they will be called back. Less common, and it requires managing a list of appointments.
• Callback from the website — the customer leaves a number in a form on the website, and the system dials. This is closer to a dialer than to a queue.

The main difference: with a queue callback, the order is preserved. Whoever waited first gets called first, exactly as if they had stayed on the line. With a manual callback, the order depends on whoever is dialing, and customers can fall through the cracks.

Why it is good for both sides

For the caller: no waiting on the line. No need to hold a phone for ten minutes, and they can keep working, driving or taking care of the kids. Most important: they do not lose their place.

For the business: fewer abandoned calls. A caller who hangs up in frustration is a customer who may not call again, or a donor who went to another organization. A callback turns that hang-up into an orderly request.

For the load: the load is spread out. At peak time, requests are collected, and the agents answer them when the pressure drops. Instead of a long, tense queue, there is a list that slowly gets shorter.

For costs: when callers are not waiting on the line, fewer call channels are tied up in waiting. In an organization with a limited number of channels (see Channels), this leaves room for new calls.

A real-life example: a busy morning in a billing office

Nine in the morning, the start of the month. Twenty parents call the yeshiva office about payments, and there are two clerks. Without a callback: some wait eight minutes, some hang up and dial again, and the queue only grows. With a callback: after two minutes in the queue, most parents press 1 and hang up. The clerks answer in order, and the system dials each parent in turn. By ten thirty everyone has been answered, and nobody held a phone for half an hour.

When it fits, and when it fits less

• Fits a service center with waiting times of a few minutes, a nonprofit on a fundraising night, a support line, an office that gets a wave of calls in the morning.
• Fits less when the wait is short anyway — an offer after ten seconds only confuses.
• Does not fit urgent calls — someone who needs help now does not want to wait for a callback.
• Note callers with a blocked number or from a public phone — there is nowhere to call them back.

Tips for setting it up well

• Don't offer too early. If most calls are answered within a minute, offer after two. The offer is meant for someone who is really waiting.
• Short, clear wording: "For a callback when an agent is free, press 1. To keep waiting, stay on the line."
• Confirm the request — the caller needs to hear that the request was received, otherwise they will not dare to hang up.
• Don't promise a time you are not sure of. "We will call you back soon" is better than "within five minutes".
• Train the agents to open with a sentence that reminds the caller that they asked for a callback.

A full example: a nonprofit campaign night

A food distribution nonprofit holds a phone fundraising night. Six volunteers answer from home through temporary extensions, and the line is advertised in announcements and flyers. Expected: a few hundred calls between eight and eleven at night, in waves.

• 20:00. The broadcast begins. Within ten minutes forty callers are in the queue, with six volunteers on calls. The message at the entrance: "Thank you for calling, all volunteers are busy, we will answer in order".
• After 90 seconds in the queue the caller hears: "So you don't have to wait on the line, press 1 and we will call you back in the next few minutes". About three out of four press the key and hang up.
• 20:20. The first wave calms down. The system dials everyone who asked, in order, and connects them to the volunteer who became free. The volunteer opens with: "Good evening, we are calling you back from the campaign, as you requested".
• 21:30. A second wave after a reminder. Same mechanism, without anyone having to change a setting.
• 23:00. The coordinator goes through the call log for requests the system could not complete, for example people who did not answer the callback, and assigns them to volunteers for the next day.

The difference compared with the previous year, without a callback: back then many hung up after three minutes and did not call again. This time almost everyone who called got an answer, even if after half an hour, and nobody held a phone. The coordinator watched the queues screen throughout the evening to see how many were waiting and how many requests were open, and added a volunteer when needed.

Metrics: how to know it works

This data is pulled from the call log and from the queue statistics. The right order to check: abandonment first, and only then the other metrics. A queue where almost nobody hangs up does not need a callback at all, and a queue where many hang up before the offer needs an earlier offer.

A rule of thumb for orders of magnitude: if more than one in five callers hangs up before being answered, it is worth checking the offer time. And if most callback requests are answered only after more than a quarter of an hour, the problem is the number of agents, not the setting.

Calibration: how to decide when to make the offer

There is no single right number. The right time depends on how the waiting is distributed in your case, and this varies between queues and between morning and evening. A simple method in four steps:

1. Measure for a week. From the call log, pull the wait time of every call in the queue, and mark who was answered and who hung up.
2. Look for the breaking point. There is almost always a time after which hang-ups jump: for example, up to one minute almost nobody hangs up, and between two and three minutes many do. The offer should be heard a little before that point.
3. Set it and test for a week. If the abandonment rate dropped and the share of people who accepted the offer is reasonable, keep it. If most callers press the key immediately, the offer is too early and the agents waste time on callbacks.
4. Repeat it each season. Before the holidays, at the start of the school year and on a campaign night the wait gets longer, and the offer may need to move.

Two more considerations: a queue with only two agents benefits from an early offer, because every waiting call takes up a large part of the capacity. And a queue whose callers mostly use a landline in an office can afford a later offer, because waiting there is less bothersome than on a mobile phone on the street.

When it doesn't work: symptom, cause, fix