Callback queue
The callback queue is where missed calls become handled work. When the receptionist takes a message, a caller needs a person, or a call ends unresolved, it becomes a callback: one item on a short list, most urgent first, that your staff work through each day.
At a glance
- Every loose end becomes a callback: a message, a request for a person, a voicemail, or a call that ended unresolved.
- Most urgent first, each with the caller and a short reason in plain words.
- Worked in one click: mark it called back, snooze it, or cancel it. Every action is recorded.
- Staff are alerted by email and text message when a new callback arrives, so your team knows at once.
What becomes a callback
The receptionist creates a callback whenever a conversation needs a person to finish it. That includes:
- A caller leaves a message or asks your team to call back.
- Someone needs a person: a question outside what you set up, or a request for a specific staff member.
- A caller asks to cancel, move, or confirm an appointment. Your team makes that change.
- A caller reaches voicemail. Each voicemail becomes one callback.
- A call ends without a resolution. Even if the caller hangs up, a backstop checks the finished call, so a real unresolved call still becomes a callback rather than disappearing.
- An appointment request needs staff to confirm it (see Booking modes).
- A caller needs a personor the call ends unresolved
- The details are takenname, number and reason
- Saved as a callbackranked by urgency
- Your team is alertedby email and text
Asked to talk with someone about a treatment plan.
+1 815 555 0148
It takes a message instead of guessing
How they are prioritized
Each callback carries a short reason and an urgency, so your front desk can see at a glance which ones matter most. Urgent follow ups sit above routine ones, an overdue callback says so, and each row shows the caller and one line on what they need: enough to act without opening the whole call.
Working the queue
Your team works the queue from the Callbacks page of the dashboard. Each callback has three buttons.
| Button | When to use it |
|---|---|
| Mark called back | The follow up is done: you called the person back, booked the appointment, or answered the question. It leaves the active queue. |
| Snooze 1 hour | Not now, but not done. It is scheduled for an hour from now, so it stays on the list without crowding the moment. |
| Cancel | No action needed: a duplicate, a wrong number, or something already handled another way. |
Every action is recorded
Alerts and the daily summary
A new callback sends your staff an alert by email and text message, and shows in your dashboard, so it does not sit unseen. Alerts are turned on for your account at launch, and before you go live we prove that a real alert reaches your team; see Getting started. The account owner also gets a daily summary email each evening with the callbacks still waiting. If an alert does not arrive, Troubleshooting lists what to check.
In staff confirm mode, the queue is the product
Every business starts in staff confirm. In that mode the queue is the whole workflow: the receptionist handles the conversation and the intake, and your front desk keeps the final say by working the queue. Even after a practice turns on direct booking, the queue stays as the safety net for the rare moments a schedule is out of reach, so a booking is kept as a request rather than lost.
Was this page helpful?
Keep exploring

