New and existing dental patients often need different administrative workflows. Treating every caller as new creates duplicate records; treating a phone match as proof of identity can attach requests to the wrong person.
Ask whether the caller has visited the practice before, then use the practice's approved matching process. Keep “caller says existing patient” separate from “record matched.” Shared family numbers and changed names require an ambiguity path.
Define the minimum facts for each route
For new patients, collect the information needed for the approved first-contact or booking process. For existing patients, confirm the relevant record without reading unrelated history aloud. Record uncertainty rather than asking the model to choose the most plausible household member.
The American Dental Association publishes patient telephone guidance. Use it as background for a practice-approved administrative script, with the practice controlling verification and clinical escalation.
Work through a fictional family number
A parent calls from the number associated with two children and another adult. They want an appointment for themselves and believe they visited years ago. The agent should not automatically attach the request to the first family record returned by search.
It gathers the approved confirming details and routes unresolved matching to staff. If a new-patient request is captured, mark the possible existing record so staff can reconcile it before creating unnecessary duplicates.
| Caller situation | Proposed route |
|---|---|
| Clearly matched existing patient | Eligible existing-patient workflow |
| No previous visit reported | Approved new-patient intake |
| Shared phone, several records | Limited clarification and review |
| Past patient, no clear match | Unresolved identity request |
| Caller asks about urgent concern | Approved escalation regardless of booking route |
Keep booking eligibility separate from identity
A matched record does not establish that every appointment type is appropriate or that the caller can change another person's visit. Check action authority and the practice's scheduling policy independently.
Separate routes add questions but preserve the context staff need. A single generic form is easier to implement while increasing duplicate records and inappropriate appointment selection. Start with the smallest meaningful distinction and test ambiguous household calls.
Keep messages about the administrative next step accurate. A captured new-patient enquiry is not automatically a confirmed appointment, and an existing patient's callback request is not a clinical response. Review customer detail collection for correction and readback handling.
Questions about patient status
Should returning patients repeat the entire intake?
Only collect what the current action needs. Staff may need to verify changes without rebuilding a complete record on every call.
Can a family member manage another appointment?
Follow the practice's approved authority and verification process. A shared number alone does not resolve that question.
What if the patient status remains unknown?
Create a clearly marked administrative request with an owner and safe contact route. Staff can resolve the record before consequential scheduling or disclosure.