From dental call to callback: a reception handover checklist

Agree a small, useful enquiry record

Start with the action reception will take. A request for a callback needs enough information to contact the caller and understand the enquiry. Collect the details agreed with the practice rather than adding fields that nobody will use.

• Caller’s name: record what the caller provides and read it back where needed.
• Callback number: ask for the number to use, including any relevant country code. Caller ID may not be the preferred contact.
• Reason for calling: use a short factual description, distinguishing the caller’s request from a decision by the practice.
• Preferred callback time: capture a date and window, with timezone if relevant; do not promise the team is available.
• Call reference and time: keep a reference your team can use to locate the record, plus an unambiguous timestamp.
• Next action and owner: identify the reception contact or queue that will review the request.

The practice approves what is appropriate to collect, who may access it and the handling arrangements. A public demonstration should use fictional details.

A fictional example reception can review

The example number is within Ofcom’s published mobile range for drama. The example contains no real patient information. A real system should show unknown or unconfirmed information as such.

Choose the recipient and the follow-up owner

A summary in a mailbox does not itself give somebody responsibility to call back. Name the reception inbox, person or shared queue, and decide who covers absences. Agree when that destination is monitored and what happens to a request received after closing.

For an email handover, decide which details belong in the subject and body and how the recipient opens any further record. For SMS, agree whether it is an alert for staff or an acknowledgement to a caller; these are separate uses, recipients and costs. Patient messages should use wording approved by the practice.

In a ClinicVoice setup, these routes require configuration and testing. The current public voice demo does not send emails or SMS. A screen shown in a demonstration is an illustration of a possible workflow, not evidence of delivery.

Check delivery and accuracy separately

Use a test record and a destination controlled by the practice. Agree acceptance criteria before running the test and record the observed result for each stage:

1. Capture: compare the agreed details in the record with what the fictional caller actually said. Check digit corrections, unclear names and date interpretation.
2. Send: confirm that the configured route attempted the handover and keep the available reference and time.
3. Receive: have the nominated contact locate the actual message. Check the intended inbox and relevant junk or filtering rules rather than relying only on a sent indicator.
4. Act: ask the reception contact to identify the next action and where its completion is recorded. A received message is not proof that the caller has been contacted.
5. Recover: agree who is alerted if the handover fails, where an enquiry can be recovered and how repeated delivery is recognised.

This article does not report that those tests have passed. Keep the test date, reference, expected result, actual result, reviewer and any action required. Record each stage separately so a conversation test is not mistaken for a working notification.

Keep a request separate from a confirmed appointment

Use wording that reflects the actual state: “callback requested”, “reception reviewing” or “appointment confirmed” only when the practice’s process has reached that step. An available-looking time in a conversation is not a diary reservation.

Without an agreed booking integration, reception checks availability, speaks to the caller and confirms any appointment. Direct booking requires a compatible connection, approved rules and a separate acceptance test. Alice does not diagnose, assess treatment suitability or decide clinical priority.

Give the practice’s clinical lead responsibility for urgent-call instructions and the approved escalation route. Do not rely on a routine email queue as an assumed urgent-response service.

Review the whole route before accepting the setup

Link this checklist to your telephone-diversion plan. Record the call destination, the details collected, the handover recipient, the follow-up owner, the fallback and the evidence for each tested step.

The written scope should also identify relevant providers, access, retention, international processing, costs and support arrangements. Our setup and acceptance process and website privacy notice explain the current service boundaries; the practice-specific arrangements must be agreed before patient calls are handled.

Use the cost guide to check the subscription alongside notification and integration charges. Then send a practice enquiry about the cover you need.

Sources and scope

Prepared by Aleo Li at ClinicVoice and reviewed on 21 October 2026. The format, checklist and fictional record are original planning material by a service supplier. They are not an independent clinical standard, customer case study or report of a completed end-to-end test.

Ofcom: numbers for TV and radio drama is the source for the illustrative telephone number range. Clinical instructions, real patient-data handling and reception responsibilities are agreed with the practice; a published checklist does not establish that a particular integration works.