A woman messages a clinic to move her father’s appointment. She knows his name and date of birth, but the receptionist still has two separate questions: is she allowed to act for him, and what exactly is she allowed to do? Family relationship alone does not answer either question.
This is an administrative workflow, not medical or legal advice. Every clinic needs an approved identity, consent, privacy and safeguarding process. The goal is to act without disclosing more than the person may receive.
Start with the request, not the relationship
Ask what the messenger wants done. Booking, cancelling, changing contact details, requesting results and seeking clinical advice are different tasks. The last two need a different authorised route.
Use the clinic’s administrative and clinical routing boundary whenever the message crosses into symptoms, medication, results or suitability for care. Do not let a familiar surname turn a clinical question into a reception task.
Keep one five part proxy record
A useful record separates five facts instead of marking the contact simply “verified”.

- 1MessengerRecord who is asking and the approved identity check.
- 2PermissionName the accepted source of authority.
- 3ScopeLimit access to the exact appointment task.
- 4Booking stateUse the authorised system as the source of truth.
- 5ReviewSet a review, expiry or specialist handoff point.
- Messenger: who is asking and how the clinic checked that identity under its approved process.
- Permission: the source of authority, such as recorded patient consent or an approved proxy-access process.
- Scope: the exact task allowed, such as booking or cancelling an appointment.
- Booking state: what the authorised appointment system currently shows.
- Review: when the permission should be checked again, expire or return to a specialist owner.
The customer verification guide explains why teams should use an approved route rather than ask people to post passwords, one-time codes or excessive personal details in a conversation.
Match the reply to the evidence
Do not use one script for every family or carer message. Give staff a small decision table.
| Incoming request | Minimum operational check | Safe next step |
|---|---|---|
| Book an available appointment | Messenger, permission and booking scope are current | Offer approved options and record the chosen slot |
| Move or cancel an appointment | Permission covers changes and the booking is found | Update the booking system before confirming |
| Ask whether an appointment exists | Disclosure is within the recorded scope | Answer only through the approved channel |
| Request results or clinical advice | Administrative scope is insufficient | Route to the clinic’s authorised clinical process |
| Permission is missing or unclear | Identity or authority is not established | Pause, explain the verification route and assign an owner |
NHS England guidance says practices assess a proxy request, agree its service scope, use consent where appropriate, verify identity and review access. This is a UK operating example, not a universal rule.
Keep permission narrower than the conversation
A patient may permit a daughter to reschedule but not view records. Record the permitted action instead of assuming unlimited access.
If the messenger adds a new request, check it separately. Permission to cancel one appointment does not automatically cover future bookings, marketing messages, billing questions or clinical information. The case-note guide helps staff record source, decision, owner and next checkpoint without copying unnecessary sensitive detail.
Update the booking source before confirming
The conversation is not the appointment record. Check the authorised booking system, apply the permitted change there, then send the confirmation. This prevents a chat message from saying “moved” while the old slot remains active.
Use the appointment rescheduling workflow for old and new time, timezone, owner and final confirmation. Use the reminder-reply workflow when a family member replies to an automated reminder, because delivery, reply and booking state still need separate evidence.
Give unclear requests one owner
In a shared team inbox, assign the conversation to one person while verification is pending. A note should show what was requested, which check is incomplete, who owns it and when the clinic will respond. Avoid several agents asking the family member for the same details.
DripTell can keep a supported conversation, owner and internal note visible when correctly configured. It does not grant proxy authority, decide capacity, verify a legal relationship or replace the clinic’s booking and clinical systems.
Frequently asked questions
Can a family member book an appointment for another adult?
Only through the clinic’s approved process. Confirm the messenger’s identity, the patient’s permission or other accepted authority, and the exact booking scope before acting.
Is knowing the patient’s details enough?
No. Knowing a name, birth date or appointment detail does not by itself prove permission. Use the clinic’s approved verification route and collect only what that process requires.
Should proxy access stay open forever?
Not automatically. Record a review or expiry point and recheck when circumstances change.
Sources
Want help applying this guide?Ask the DripTell team
From reading to action
Want help applying this to your business?
Share your details. We will read the article you are on and start with a useful answer for your team.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy



