A returning caller asks, “What time is my appointment?” The incoming number matches a customer record, but it is a shared family phone. Reading out every upcoming visit could reveal another person's information.
Recognition can help route a call. It is not automatically permission to disclose appointment details.
Separate recognising a number from verifying access
Define what the business can use caller identity for: greeting, record lookup, appointment disclosure, or a change request. More sensitive actions may need additional checks.
A number can be shared, reassigned, forwarded, or captured incorrectly. Treat it as one signal within the approved policy rather than a universal identity credential.
| Requested action | Boundary to establish |
|---|---|
| General business question | No private appointment data needed |
| Appointment lookup | Authorised relationship to the appointment |
| Reschedule | Authority plus exact booking selection |
| Change account details | A separately approved verification process |
Keep the policy specific to the business and the sensitivity of the information involved.
Do not reveal private details while clarifying
An unverified caller should not receive a menu of other people's names, services, or dates to choose from. Ask permitted questions that help establish the intended relationship without disclosing unnecessary information.
For a fictional household account, the receptionist might need staff review when several appointments share a contact number. It should not choose the first match because that produces a shorter conversation.
Preserve the verified context through tool calls
The application should carry the authorised account and resource scope to the appointment lookup. A model-provided customer identifier does not establish the caller's rights.
Limit responses to the required administrative information. If the request is only for the time, the tool does not need to return unrelated private notes.
The private-document access article covers a parallel boundary in knowledge retrieval. The principle is the same: permitted context must be enforced before the answer exposes it.
Test shared and stale identifiers
Use fictional records with shared numbers, similar names, two bookings, and an outdated contact number. Include a denied caller and verify that neither the conversation nor error messages reveal the private record.
A human fallback may require another verification step too. Transferring to staff does not by itself establish authority.
The cancellation-matching guide describes how the same ambiguity becomes more serious when a caller asks to change a booking.
Returning-caller questions
Is a familiar phone number enough for every action?
No. Match the verification to the requested operation.
Should the AI return full records for convenience?
Return only the information required for the authorised task.
What belongs in a pilot?
Include shared numbers, ambiguous matches, and denied disclosures in the review cases.