Using Call

Per-Queue Voicemail in Call: Setup and Follow-Up

How to plan voicemail for each call queue: when callers reach it, what the greeting says, who follows up and how to turn messages into call-backs in Call.

Call editorial team · Published · 6 min read

Many businesses treat voicemail as a safety net and forget it. Callers leave messages, nobody listens, and the caller concludes that the company does not care. Voicemail is only worth offering if there is a process behind it.

A person listening to a recorded message on a headset at a desk
Illustrative image

This guide covers the whole loop for a call queue: when callers should reach voicemail, what they hear, who handles the messages and how to measure the result. It ends with the steps in Call. For the related topic of call-backs in menus, see Using Callbacks and Voicemail in Your IVR.

When callers should reach voicemail

Voicemail should be the planned outcome of specific situations, not the place calls fall into by accident. Three situations are worth offering it.

Where voicemail makes sense

  • The queue is closedOutside hours or on a holiday, a message is the natural alternative to a dead line.
  • Nobody answersIf every phone rang for the full time and no one picked up, the caller can leave a message instead of hearing silence.
  • The caller prefers itSome callers would rather leave details than wait. Offer the choice when queues are long.

What voicemail should not be is a way to avoid staffing. If a queue regularly sends callers to voicemail during open hours, it is understaffed or its alerts are being ignored. Treat each such message as a signal.

Why each queue needs its own voicemail setup

A single shared mailbox is easy to build and hard to run. When billing, technical support and sales messages land together, someone has to sort them first, and the one who sorts is usually the busiest person. Messages wait, and callers lose patience.

Giving each queue its own handling keeps the loop short. Messages for billing go to billing; the greeting can mention billing, so the caller knows they are in the right place; and the people who listen already know the topic. It also lets you apply different expectations: an urgent technical queue might promise a same-day call-back, while a general enquiries queue might promise the next working day.

One shared mailbox vs one per queue

SharedPer queue
SortingSomeone sorts firstMessages arrive already sorted
GreetingGenericMatches the team and its promise
OwnershipUnclearOne team is responsible
ReportsOne mixed pileWait and volume per team

Writing the greeting

The greeting is the only thing the caller will hear, so it must do four jobs in a few seconds: acknowledge the situation, say what to leave, say what happens next and tell them when.

What to include

What to avoid

Sample: "You have reached the billing team. We are closed right now. After the tone, please say your name, your number and what your question is about. We will call you back by the end of the next working day."

Building the follow-up process

A message is only the start of the work. The process that follows should be simple enough that everyone can follow it on a busy day.

From message to finished call-back

  1. Message arrivesThe caller leaves a message in the queue's voicemail.
  2. Someone reads itA named person or rota checks the new messages at set times.
  3. Turn it into a call-backThe message becomes a call-back item with an owner.
  4. Call the callerWhoever takes it calls, and records whether they reached the person.
  5. Close the loopIf there was no answer, try again at another time and then leave a message or send a note.

Set check times that match your promise. If you promise a same-day call-back, check at least twice a day. If your promise is the next working day, the first thing each morning works. Write the times where the team can see them.

Who owns the mailbox

Name an owner, and a backup. Without a name, voicemail is checked by whoever remembers, which means rarely. On small teams the owner can rotate weekly; on larger teams the supervisor of the queue is the natural choice. See What Contact Center Supervisors Should Monitor for how supervisors keep an eye on waiting work.

Measuring voicemail

Three simple measures tell you if the process works: how many messages arrive, how long they wait before someone calls back, and what share of call-backs reach the person. For the last one, Callback Completion Rate explains the idea in more depth.

MeasureWhat it showsIf it looks bad
Messages per day, per queueDemand outside answered callsCheck staffing and hours
Age of the oldest unread messageWhether the loop is workingAdd check times or owners
Call-backs that reached the callerHow well timing and numbers workTry other times of day

Review the oldest unread message every day. It is the best single sign of whether the process is alive.

Common problems and how to avoid them

Most voicemail failures are process failures rather than technical ones. They repeat across teams, so it pays to look for them early.

It also helps to review a handful of real messages together once a month. Listen for callers who sound frustrated, for questions that keep coming back and for details the greeting should have asked for. Voicemail is one of the few places where customers speak freely without an agent shaping the conversation, which makes it a useful source of ideas for fixing menus, answers and opening hours.

Setting it up in Call

In Call, each queue decides what a caller gets when the queue is closed. Under Calls, Queues & SLA, press Configure on a queue and open the Hours tab. In the When closed list, choose Take a message to send callers to voicemail, or send them to the overflow queue instead. Write the Closed greeting that callers hear. Callers also leave a message when nobody answers a call. Only owners, administrators and managers can configure queues.

Messages appear under Calls, Inbound ops, in a Voicemail area that shows when there is new voicemail. Each message lists who called, which queue it was for, when it was left and the transcript. Press To callback to add the caller to the Callbacks list. There, someone presses Take to make the call-back theirs, calls the customer and presses Reached or No answer. Overdue call-backs are listed first, with the promised time and how long they have waited, and a card shows the share completed on time over seven days.

To check the setup, use the routing simulator on the same page: it shows where a call to a queue would end up at the time and day you test, without dialling anyone. For closing hours and holidays, see Business Hours, Holidays and Closures in Call.

Frequently asked questions

Should every queue have voicemail?

Not necessarily. Queues that are always staffed and have an overflow route may not need it. Any queue with closing hours should offer a way to leave a message, so callers are not left with a dead end.

How long should a voicemail greeting be?

Aim for under fifteen seconds. State why they reached voicemail, what to leave and when they will hear back, and stop there.

How often should we check voicemail?

Match your promise. For same-day call-backs, check at least twice a day. For next-working-day promises, check first thing each morning, and also look at the oldest unread message daily.

What if the caller does not answer the call-back?

Record it as no answer, try again at a different time of day, and then leave a short message or send a written note if you have the caller's consent to contact them that way.

Is a transcript as good as listening?

A transcript is a quick way to sort messages and spot urgent ones, but it can contain errors, especially with names and numbers. For anything important, listen to the original or confirm details when you call back.

Should callers leave sensitive details in voicemail?

It is better not to ask for them. Ask for a name, a number and a short reason, and collect sensitive information during the live call-back.

Set up per-queue voicemail and follow-up in Call

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

Related guides