What to tell a caller waiting in the queue
It is not only the wait that wears callers out in a queue — it is the uncertainty. This guide covers what a caller should hear on entering the queue, the rule for talking honestly about time, a second-by-second message sequence, when to offer a callback, phrases to avoid, an illustrative courier example, night calls and a checklist.
The short answer
A caller waiting in a queue needs three things: to know the call has been received, to have a rough idea of how long the wait will be, and to have an alternative if they do not want to wait. That means hold messages must be short, honest and useful. Advertising, "your call is important to us" repeated every 20 seconds, and unrealistic time promises annoy callers and make them more likely to hang up.
A good queue experience is more about wording and rules than technology. This article shows the sequence of hold messages, the rule for talking about time, the moment to offer a callback, and how to check your messages.
What callers feel in a queue
Uncertainty is as tiring as the wait itself. A caller who does not know how long they will wait feels one minute as three. Silence is worse: the caller assumes the call has dropped, hangs up and calls again — adding one more call to the queue.
So the main purpose of hold messages is not to "fill" time but to explain the situation and give the caller a choice: wait, ask for a callback, or find the answer in another channel.
The first message: the call is received
As soon as the caller enters the queue, they should hear one sentence: "All our staff are on other calls right now; you are in the queue." That sentence says two things — the call is not lost, and a person will answer. Do not repeat information already given in the greeting.
Being honest about time
An estimated wait or a position in the queue helps the caller, but only if it is accurate. Saying "you will be answered in one minute" and then keeping them waiting four minutes is worse than saying nothing. If your system cannot give a reliable estimate, do not quote a figure; give general but honest information such as "waiting times are longer than usual".
The sequence of messages
- 0 secondsThe call is in the queue; staff are busy.
- 30–45 secondsUseful information: the answer to a frequent question, or a task that can be done on the website.
- 60–90 secondsA callback offer: "If you'd rather not wait, we can keep your number and call you back."
- Every further 60 secondsA short confirmation — "You are still in the queue and will be answered soon" — and the callback offer again.
There can be music between messages, but never silence. Repeating the same message too often is also a problem — the caller already knows it by heart, and every repeat reminds them how long they have been waiting.
When to offer a callback
A callback offer is the queue's most powerful tool, but offering it too late is useless — the caller has already hung up. Offering it too early can happen too: if the wait will only be 40 seconds, the callback process takes longer. A practical rule: offer it when the expected wait passes a set threshold, such as two minutes.
There must be a real process behind the offer: where the number is recorded, who calls and when, and what happens if the customer does not answer. A promised callback that never happens creates double dissatisfaction.
What not to say
- Advertising and campaign announcements — the caller has a problem, not a shopping trip
- "Your call is very important to us" — every 20 seconds
- Unrealistic time: "you will be answered in a few seconds"
- A long website URL — impossible to remember on the phone
- Sending the caller to dial another number when the call could be transferred there
How to choose useful information
The information given while waiting should come from the most frequent question on that line. If most callers ring about order status, a sentence like "you can also check the status using the link in your text message" frees some of them from the queue. A general company presentation helps no one.
Illustrative example: a courier service
Not a real customer case. On a courier service's line, the hold message was a three-minute advertising loop. The new sequence: a receipt message, at 40 seconds "your parcel's status is shown in the link in your text message", at 75 seconds a callback offer, then a short confirmation every minute. Accepted offers go to a separate list, and when the queue shortens, that list is worked first.
The results of such changes cannot be promised in advance, but they can be measured: compare the share of callers hanging up in the queue, the callers accepting the callback offer, and whether callbacks happened on time, before and after the change.
Nights and out of hours
An out-of-hours call should not enter a queue — there is nobody there to answer. Such a call is either answered by an AI agent, or the caller is told the opening hours and offered to record the request. Saying "you are in the queue" on a line where no one is working is the worst practice of all.
Checklist for your messages
- What does the caller hear in the first 5 seconds after entering the queue?
- Has the quoted time been compared with the real wait?
- At which second does the callback offer come, and who is behind it?
- Are there any moments of silence?
- Have advertising and repeated courtesy phrases been removed?
- Do out-of-hours calls enter the queue?
What to measure
- The share of callers hanging up in the queue, and at which second
- The share accepting the callback offer
- The share of promised callbacks made on time
- Repeat calls from the same number within a short time — callers frustrated by waiting
Limits
Hold messages do not fix the cause of a long queue — that lies in staffing, routing and call volume. Features such as queue position and estimated wait depend on the telephony platform and may not exist in every system. This article describes general industry practice.
Answering without a queue in Vexvon
Vexvon AI Call Center approaches the queue from another side: a call reaching the line is answered by the AI agent without hold music, and even when several calls arrive at once nobody hears a busy tone (the parallel-call ceiling depends on the plan). The agent answers simple questions itself, passes difficult calls to a live operator, and for a night-time call records the caller's number and request for the team in the morning. Business hours and the night scenario are set up with routing rules.
The overflow path at peak times is covered in call overflow, and the menu wording in IVR menu best practices.
First step
Call your own line at a peak hour and wait in the queue for three minutes. Write down every message you hear with its timing and compare it with the checklist above. More articles are in the IVR & call routing section; to shorten your queue with an AI agent, get in touch.