Using Call

Callback Requests in Call: From Menu Option to Done

How a callback request travels through Call: where waiting call-backs appear, how to take one, record the result and stop promises from slipping.

Call editorial team · Published · 6 min read

Few things annoy a caller more than being told "we will call you back" and then hearing nothing. Few things please them more than a call-back that arrives when promised. The difference is rarely the phone system; it is whether the promise is visible to the whole team and whether someone owns it.

A support agent with a headset reviewing a list of people waiting for a call back
Illustrative image

This guide follows a call-back from the moment it is created to the moment it is closed, and shows how to run that list in Call. For the wider picture of offering call-backs in a phone menu, see Using Callbacks and Voicemail in Your IVR.

Where call-backs come from

A call-back is any caller who should be rung rather than left alone. They reach your list in a few ways, and it helps to know all of them because each one tells you something different about your phone service.

Sources of call-backs

  • Waiting calls turned into call-backsWhen a manager drains a queue, everyone still waiting becomes a call-back, as long as their number is known.
  • VoicemailA message left when a queue is closed or nobody answers can be turned into a call-back with one button.
  • Abandoned callersCallers who hung up before anyone answered can be added back to the list as a group.
  • Online bookingCall-backs requested on an online booking page also appear in the calendar, so they are not lost between tools.

Each source has a different expectation. A person who left a voicemail chose to wait. A person who hung up after a long queue did not, so the call-back to them deserves more urgency and a short apology.

The call-back list in Inbound ops

Open Calls, then Inbound ops. The Callbacks table lists the people waiting, with overdue ones first. For each row you can see the customer, the queue, the reason, the promised time (or "as soon as possible"), how long they waited and how many attempts have been made. The cards at the top show how many call-backs are waiting, how many are past their promised time and how many were completed on time over the last seven days.

Those cards are worth reading at the start of every shift. A red overdue card is a to-do list; a falling on-time figure is an early warning that you are promising more than the team can deliver. The metric is covered in more depth in Callback Completion Rate: A Metric Worth Tracking.

Working one call-back, step by step

From waiting to closed

  1. Take itPress Take on the row. It moves to your own list, so nobody else dials the same person.
  2. Call the customerRing the number, state who you are and why you are calling, and handle the original reason.
  3. Record the resultPress Reached if you spoke to them, or No answer if you did not.
  4. Let the list do the restA No answer goes back on the list to be tried again later; after three attempts it is closed as failed.

Only the person a call-back is assigned to, or a manager, can mark it Reached or No answer. This is deliberate: it keeps the record honest and stops a colleague from closing something they did not do.

What happens after a No answer

A No answer puts the call-back back on the list to be tried again in about half an hour. After the third attempt it is closed as failed. That gives a sensible rhythm without anyone setting reminders, but it also means a failed call-back is a loose end. Consider a follow-up by message or email for those, written as a general practice and sent through the channel your customer prefers.

Managing the backlog as a supervisor

Administrators and managers have a few extra controls on the same screen. They are powerful, so use them with intent.

Making promises you can keep

The software can track a promise, but only people can keep one. Three habits make the biggest difference.

  1. Promise a window you can meet. "Within the hour" that you reach in forty minutes beats "in ten minutes" that slips to the afternoon.
  2. Give call-backs a regular slot in the day. A call-back hour after lunch, for example, stops them being squeezed out by incoming calls.
  3. Review overdue items before the shift ends. If something cannot be rung today, tell someone, and decide whether a message is a fair substitute.

Healthy and unhealthy call-back habits

HealthyUnhealthy
OwnershipEvery call-back is taken by one named personRows sit untouched; anyone might ring
RecordingReached or No answer pressed straight after the callResults recorded at the end of the week, if at all
Overdue itemsChecked at the start and end of each shiftOnly noticed when a customer complains
PromisesWindows matched to staffingShort promises made to end the call quickly

What to say when you ring back

The first ten seconds of a call-back set the tone. The customer may not remember asking, may be in the middle of something, or may be wary because the number is unfamiliar. A short, steady opening works in almost every case: your name, your business, the reason you are calling, and a quick question about whether it is a good moment.

If the original call reached a voicemail, say so: "You left us a message and I am returning it." That small phrase tells people their message was heard. For more on openings and closings, see How to Open and Close a Support Call.

Measuring whether it works

Three numbers tell you most of what you need: how many call-backs are waiting, how many are overdue, and how many were completed by their promised time. If overdue grows after lunchtime every day, you have a staffing pattern, not a discipline problem. Take that to your schedule; Shift Planning Basics for Phone Teams explains how to match cover to demand.

Also read the reasons. If many call-backs begin with the same question, that question belongs in your menu, your knowledge base or your voicemail greeting. Fixing it removes a call, which is better than returning it quickly.

Doing it in Call

Daily call-back routine in Call

  • Open Calls, then Inbound ops, and read the Callbacks cards.
  • Work overdue rows first: Take, call, then press Reached or No answer.
  • Turn new voicemail into call-backs with To callback.
  • After a busy spell, managers can press Recover abandoned.
  • Before closing, check the overdue count and decide what waits until tomorrow.

Call-backs requested through online booking also appear in the Call-backs tab of the calendar, where you can open the entry and then jump to Inbound ops to work it. The calendar does not give a call-back a time slot; it is measured against the queue's call-back target instead.

Frequently asked questions

What is a call-back request?

It is a record that a caller should be rung back instead of staying on hold or being forgotten. It carries the number, the queue, the reason and a promised time.

What is the difference between voicemail and a call-back?

Voicemail is the message a caller leaves. A call-back is the task to ring them. In Call you can turn a voicemail into a call-back so the task is tracked.

What does Take do?

Take makes the call-back yours, so two people do not ring the same customer. Only the assigned person or a manager can then mark it Reached or No answer.

What happens if nobody answers my call-back?

Press No answer. It returns to the list for another try later, and after the third attempt it is closed as failed so it does not sit there forever.

Can callers who hung up be rung back?

Yes. Administrators and managers can add a call-back for callers from the last two hours who hung up before being answered, using Recover abandoned.

Does Call send a text to confirm the call-back?

No. Call does not send SMS by itself. If you want to confirm by message, do it through a channel your team has set up.

Work your call-back list in Call

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

Related guides