Key takeaways
- Offer a callback whenever you can't honestly name the wait; a known, finite wait feels shorter than an open-ended one[2].
- Large phone operations already work this way: the IRS may offer a return call once waits pass 15 minutes[1].
- Put callbacks into fixed windows each day and staff them like appointments, not as "when someone's free".
- Confirm the number, say which number you'll call from, and leave the answer on voicemail if you miss them[3].
- Emergencies never get a callback slot; they go straight to the on-call path.
Hold is a wait with no end time
Putting someone on hold asks them to hand over the next few minutes of their day without saying how many. Some will wait. Plenty will hang up and try the next business on the list, and a few will hang up and call back angrier than before. A scheduled callback swaps that open-ended wait for a time the caller picks, which is why large phone operations offer one when their queues get long.
The IRS is a good example of the practice at scale. Its telephone help page says callers may be offered a return call instead of waiting on hold during high call volume, that the offer may come when waits exceed 15 minutes, and that average waits run about 8 minutes in filing season and about 15 minutes for the rest of the year[1]. A small office doesn't have the IRS's queue, but it has the same problem in miniature at 8:05 on a Monday, when two people are calling in sick, three want to rebook and the person at the desk is also checking someone in.
Source: Internal Revenue Service, 2026[1]
Show the data
| Item | Value |
|---|---|
| Filing season (January to April) | 8 min |
| Rest of the year (May to December) | 15 min |
The psychology behind this is decades old. David Maister's 1985 paper on waiting lines set out propositions that still describe a phone queue: uncertain waits feel longer than known, finite ones; unexplained waits feel longer than explained ones; and the music played while agents are busy is, to many people, an added annoyance rather than a benefit[2]. A callback fixes all three at once. The wait has an end, the caller knows why there is one, and they spend it doing something else.
When to offer a callback, and when hold is fine
Hold is not always wrong. A ninety-second check with a colleague across the room is quicker than any callback, and the caller leaves with the answer. The test is whether you can name the wait honestly. If you can, and it's short, hold. If you can't, offer the callback.
| Situation | Better choice | Why |
|---|---|---|
| You can name the wait and it's two minutes or less | Hold | Shorter than any callback, and the caller hears the answer now |
| You can't say how long it will take | Callback | An open-ended wait is the one callers resent most |
| The answer needs research, a quote or someone who is out | Callback | Nobody should hold while you look something up |
| Someone is standing at your counter | Callback | Making an in-person customer wait for the phone breeds resentment |
| The caller is driving or between jobs | Callback at their time | They choose a window when they can actually talk |
| Emergency: a leak, no heat, pain, a safety risk | Neither: transfer now | Urgent calls follow the on-call path, never a slot |
The counter row deserves a word. Maister described the resentment of waiting in person while a receptionist answers the phone, a distant caller apparently getting priority over someone who made the trip[2]. A callback lets the person at the desk keep their place, and lets the caller keep theirs. Screening junk out of the queue helps too, since every pitch answered is a minute someone real spends waiting; call screening for businesses covers the rules.
How to offer a callback: the words
The offer has to sound like the better option, not a brush-off. Say the wait honestly, offer a specific window and let the caller choose. Five short moves cover it.
- The offer: "Everyone's on calls right now and I can't promise how long it'll be. I can have someone call you back between 2 and 2:30 today, or you can hold. Which suits you better?"
- Confirm the number: "Is this the best number, the one ending in 4417?" Read it back digit by digit if it's new.
- Say who will call and from where: "It'll be Sam, calling from our main office line, the same number you just dialed."
- Get the question: "So Sam has it ready, what's it about?" Write it in the caller's words, not your shorthand.
- Close with the promise: "Between 2 and 2:30, Sam, from the office number. If anything changes, we'll call to tell you."
The number matters more than it looks. In Pew's survey, 67% of US adults said their usual practice with an unknown number is to let it go to voicemail and check the message, and only 19% said they generally answer[3]. A callback the caller is expecting, from a number they've been told about, is far more likely to be picked up. Ask permission to leave the answer itself on voicemail if they miss you, so even a missed callback does its job. The callback script covers what to say once they pick up.
Some callers will choose hold anyway, and that is their call to make. Respect it by checking back rather than leaving them in silence: every minute or so, a short update with a reason ("Still with the customer before you, should be another two minutes") and the offer again. An explained wait is easier to sit through than a silent one, and the repeated offer means nobody is stuck on hold because they said yes once.
Plan callback windows like appointments
"We'll call you back as soon as we can" is not a scheduled callback; it's a hold with extra steps. Callbacks need slots, and slots need someone assigned to them. Returning calls isn't extra work invented for the purpose, either: contacting customers to respond to their inquiries is rated a core task of customer service work[4]. Plan it like one.
Pick two or three windows a day
Half-hour blocks at predictable lulls, such as late morning, mid-afternoon and just before close. Keep them away from the opening rush.
Size them from last month
Count how many calls were put on hold for long or abandoned at peak times. That is roughly your callback demand.
Assign an owner to each window
One named person makes the calls in each window, with the callback list open and nothing else booked against it.
Keep one list, not sticky notes
Name, number, question, window, owner, attempts and outcome, in one shared sheet or system that everyone can see.
Leave slack
Fill each window to no more than about two-thirds, so one long call doesn't push the rest late.
Example: a four-person office puts an average of six callers a day into callbacks, and each callback takes about five minutes including notes. Two half-hour windows cover that with room to spare. The arithmetic is easy; the discipline is the hard part, because callback windows are the first thing to get eaten when the day goes sideways. Protect them the way you would protect a booked appointment.
- Caller
- Your team
- System
01Caller
Can't be helped right now
Every line is busy, or the answer needs research.
02Your team
Offers a window, not hold
Names the window, confirms the number and the question.
03System
Added to the callback list
Window, owner and the question in the caller's own words.
04Your team
Calls inside the window
Two attempts; a voicemail with the answer if they miss both.
05Your team
Outcome recorded
Reached, voicemail left or not reached, plus the next step.
Example flow for a small office. The list can live in a spreadsheet, a CRM or your phone system's notes, as long as there is only one.
Keeping the promise
Maister made a point about appointments that applies to every callback: once you give someone a time, you have set an expectation that must be met, and waiting past it grows more annoying by the minute[2]. A missed callback is worse than a long hold, because the caller trusted you with their time and you didn't turn up.
In the window
First attempt inside the agreed half hour
2 attempts
A second try ten minutes later if the first goes unanswered
1 voicemail
With the answer itself, not just a request to call back
Same day
Any window you can't make gets a call to rebook it before it passes
Example standard; set yours to match your staffing and write it where everyone can see it.
Track callbacks the way you track appointments. Each week, count how many windows ran late and how many callers were never reached. If unreached callers pile up, the cause is usually the number (unknown to the caller) or the window (in the middle of their working day). In 2025, 81% of employed people worked on an average weekday[5], so a 2 pm callback to someone at work is a gamble; offer an early-evening window if you can staff one. When a window starts to slip, call the next person at the start of their slot to say you're running ten minutes behind; a short heads-up keeps the promise intact even when the timing doesn't. New staff should practice the offer in role-play before they use it live; it's one of the scenarios in the two-week phone training plan.
Automated callbacks and the consent question
Some phone systems offer to call people back automatically, and it is tempting to hand the callback to software as well. Know the rule first. In February 2024 the FCC ruled that calls using AI-generated voices count as artificial under the Telephone Consumer Protection Act, so callers need the called party's prior express consent before making them, absent an emergency purpose or an exemption[6]. Whether a caller's request for a callback counts as that consent is a question for your lawyer, not your phone vendor. A person making the callback, from a number the caller has been told to expect, is the simplest route.
Where an SI Employee fits
The other way to shrink hold is to answer more calls at once. With overflow forwarded to it, an SI Employee picks up when every line is busy, so nobody sits in a queue. It answers what it can from your approved information and takes a callback request for the rest: the caller's name, number, question and preferred window, read back before the call ends. The request reaches your team as an email summary with the recording and transcript in the account, and a person makes the callback in the agreed window. Where a tested calendar is connected, the callback can be booked as an appointment instead of left as a request. Example: a caller at 12:10 asks whether a quote can be revised; the summary that lands in the inbox reads "Wants the bathroom quote reworked without the vanity. Prefers a call between 4 and 4:30, mobile ending 2290", which is everything the person calling back needs and nothing they have to listen back for.
The HVAC peak-season example shows that pattern on heat-wave days, when tune-up reschedules and no-cooling calls arrive in the same queue. Law firms have their own version of the problem, and this guide to callback windows you can keep covers it for intake. For the wider picture of covering a line without a queue, read what a virtual receptionist does and the comparison of an SI Employee and an answering service.
Frequently asked questions
How long is too long to keep a caller on hold?
If you can't honestly name the wait, it's already too long. As a working rule for a small office, offer a callback once a hold would run past two minutes. Large operations set higher thresholds; the IRS may offer a return call once waits pass 15 minutes[1].
Should a callback be an exact time or a window?
A window, usually 30 minutes. It is specific enough for the caller to plan around and loose enough that one long call doesn't make you late for the next.
What if the caller doesn't answer the callback?
Try twice inside the window, then leave a voicemail with the answer itself and how to reach the person who called. Record the outcome so nobody calls a third time by accident.
Can software make the callback automatically?
Some systems can, but a call made with an AI-generated or prerecorded voice falls under the TCPA's consent rules[6]. Check with a lawyer before automating it; a person calling back is the simplest option.
Do callbacks work for urgent calls?
No. Anything urgent, such as a leak, no heat, pain or a safety risk, goes straight to the on-call path. Callbacks are for questions that can wait half an hour, never for emergencies.
References
Internal Revenue Service (2026). Telephone assistance (opens in a new tab) ↑
David Maister (1985). The Psychology of Waiting Lines (opens in a new tab) ↑
Pew Research Center (2020). Most Americans don't answer cellphone calls from unknown numbers (opens in a new tab) ↑
O*NET OnLine (U.S. Department of Labor, Employment and Training Administration) (2025). 43-4051.00 - Customer Service Representatives (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (2025). American Time Use Survey - 2025 Results (opens in a new tab) ↑
Federal Communications Commission (2024). Declaratory Ruling FCC 24-17: Implications of Artificial Intelligence Technologies on Protecting Consumers from Unwanted Robocalls and Robotexts (opens in a new tab) ↑