Call-back
A call the clinic makes to a patient after a missed call, a website enquiry, or when the patient asked to be contacted later. The result depends on how quickly and how well prepared the front desk is when it calls.
≈ call-backs · callback · calling back · return call · call back
What a call-back is and where it goes wrong
A call-back is needed in three situations: the patient's call was missed, an enquiry came in from the website or social media, or the patient asked to be contacted later. In each case the next move is the clinic's, and the patient is waiting for it. The longer the gap, the less likely they are still choosing.
The weak spot is a call-back nobody owns. Each receptionist assumes a colleague will ring, and there is no task in the CRM with a deadline and a name. The patient ends up being called late, called twice, or not called at all. Enquiries that arrive in the evening or at the weekend are a particular risk: the next morning they should be first in the queue, not wait until the current calls are dealt with.
How to organise call-backs
- every missed call and every enquiry automatically becomes a task in the CRM;
- each task has an owner and a deadline set in the front-desk procedures;
- before calling, the receptionist checks where the patient came from and what they asked;
- if there's no answer, they send a message and schedule another attempt;
- the outcome is logged: booked, thinking it over, declined with a reason, unreachable.
Measures to track: the share of enquiries that got a call-back, the time to call-back, and the share of call-backs that ended in a booking. The last one shows the quality of the conversation; the first two show discipline.
A common mistake is opening with "did you call us?". It's better for the receptionist to introduce themselves, name the clinic and offer help with the patient's question straight away. That needs a separate call-back scenario in the receptionist script. You can check how call-backs work in your clinic with the self-check.