IVR and phone menus

What to Say in a Call Queue: Hold Messages That Keep Callers

How to write queue announcements that keep callers on the line: position updates, wait estimates, callback offers, hold music and message frequency.

Call editorial team · Published · 6 min read

Few moments in a phone call feel longer than waiting in a queue. The caller has no visual cue, no sense of progress, and no idea whether the line has dropped. What they hear, or do not hear, shapes their view of your whole business. This guide explains what to say, how often, and which choices to give, with examples you can adapt.

A customer waiting on the phone while looking at a laptop
Illustrative image

What callers feel while they wait

A waiting caller has three questions: have I reached the right place, how long will this take, and what can I do instead? Good queue messages answer these in order. Poor ones answer none of them, or answer a question nobody asked, such as repeating the company slogan.

What a good queue experience answers

  • Am I in the right place?Confirm the team or service they chose.
  • How long?Honest information about waiting, even if it is only "longer than usual".
  • What are my options?Callback, voicemail, a web form or a self-service answer.
  • Is anyone there?A change in sound at intervals reassures that the call is still connected.

The first message: acknowledge and set expectations

The opening message should arrive within a few seconds of the caller entering the queue. Keep it to two short sentences: thank them, confirm where they are, and say what happens next.

If calls may be recorded, the legal notice usually goes here or earlier. The rules differ by country; read Call Recording Consent for the general picture.

Position and wait estimates: use with care

Callers like to know how long they will wait, but a wrong estimate hurts more than none. If you say "about two minutes" and they wait ten, trust is lost. Position in queue is easier to get right than time, because it only counts people.

Ways to describe the wait

Position in queueEstimated timeGeneral statement
Example"You are third in line.""The wait is about four minutes.""Waits are longer than usual today."
AccuracyEasy to keep trueCan mislead if calls vary a lotAlways safe
RiskPosition may stall if early callers take long callsCallers resent a missed estimateProvides little to plan with
Good whenQueues move steadilyHandling times are predictable and data is reliableYou lack reliable data

A sensible default is to give position when queues are short and a general statement when they are long, backed by a callback offer. Average Speed of Answer explains how to get reliable timing data before you promise any.

Giving callers choices

The most helpful thing you can say to a long-waiting caller is that they do not have to wait. A callback offer holds their place in line or promises a call back at a time that suits them. Other options include leaving a voicemail, using web chat, or visiting a help page.

A queue message sequence

  1. ImmediatelyThank them, confirm the queue and say calls are answered in order.
  2. After about thirty secondsOffer a callback, or a self-service route for common questions.
  3. Every minute or twoA short reassurance, a position update if reliable, and the callback reminder.
  4. At your long-wait limitOffer voicemail or a message instead, and say clearly what happens next.
  5. If the queue closesExplain opening hours and offer a message or callback for next time.

Using Callbacks and Voicemail in Your IVR goes into the mechanics of each option, including the honesty rules for promising a call-back time.

Music, silence and frequency

Silence makes callers think the line has dropped, so use music or soft audio between messages. Choose licensed music or audio you have rights to use, and keep the volume steady, because sudden loud jumps annoy people wearing headsets. Messages should be spaced out so the music has room: a short message every thirty to sixty seconds is a typical rhythm. Too many interruptions are as irritating as none.

Writing for the ear

Sample messages for different moments

These are starting points to adapt to your own voice and services. Keep your tone consistent with the rest of the menu.

MomentSample wording
Entering the queue"Thank you for holding. You are in the support queue, and we will take your call in the order it arrived."
Callback offer"If you would prefer not to wait, press 2 and we will call you back. You will keep your place in line."
Mid-wait reassurance"Thanks for your patience. Everyone in the team is on a call, and the next available adviser will be with you shortly."
Self-service pointer"Many questions can be answered on our help page, which you can find on our website."
Long wait"We are very busy at the moment. You can stay on the line, leave a message, or call back later."
Before closing time"Our lines close soon. If you are still waiting at closing time, we will take your message instead."

Notice what the samples avoid. They do not claim to know the caller's feelings, they do not promise times they cannot keep, and they do not make the caller listen to anything unrelated to their wait.

Different callers, different needs

Not everyone waits the same way. A caller with an urgent problem needs a quicker route than one asking about opening hours. Where your system allows it, consider these refinements.

Reviewing your messages

Messages go stale. A phrase such as "we are open until six" becomes false the day your hours change. Put queue messages in a calendar for review: after any change to hours or services, and at least each season. Listen to them as a caller would, from a mobile phone, on speaker, and ask someone unfamiliar with your business what they understood. A message that confuses a newcomer is probably confusing to customers too.

Queue messages in Call

In Call, each queue has settings for how long it will ring agents, which overflow queue calls go to, and a recording announcement that plays to the caller before the call is connected. A queue can also offer a web chat address to callers who wait past its threshold, and a report shows how many callers accepted such offers. Queues also have hours and a closed greeting that callers hear outside opening times. Alerts can be set for the longest wait, the number of calls waiting and the abandon rate, so supervisors know when a queue needs attention. See Setting Up Call Queues in Call for the full walkthrough.

For the measures behind these decisions, read Answer Rate and Abandon Rate.

Frequently asked questions

How often should a queue message play?

Roughly every thirty to sixty seconds is a common rhythm, with music in between. Shorten the gap only for important updates, such as a new callback offer.

Should I tell callers their position in the queue?

It can reassure them if queues move steadily. If positions stall or jump, a general statement about waits is safer.

When should I offer a callback?

Early enough that it helps, often within the first minute, and again at intervals. Offering it only after a very long wait feels like an afterthought.

Can I play marketing messages while people wait?

Keep them minimal. Callers are already waiting, and heavy promotion makes the experience worse. One short, useful mention is usually the limit.

Do I need a different message for each queue?

Often yes for the first message, because it should confirm where the caller is. Shared wording for reassurance and callback offers keeps maintenance simple.

How do I know if my messages work?

Compare how many callers hang up during the wait before and after a change, and how many take callback offers. Make one change at a time so you can tell what helped.

Set up queue waits and callback options in Call

In the demo console you can try incoming calls in a simulation.

Related guides