Public website

Customer conversation platform

Every conversation. One clear next step.

DripTell brings WhatsApp, Instagram, Messenger, Telegram and web chat into one workspace, with shared ownership, customer context, automation and AI assistance.

You are viewing the compatibility version because this browser does not support the modern website presentation. This is the public DripTell website; no customer workspace or account data is shown.

DripTell

Messaging Operations

How to Handle Appointment Messages From a Patient's Family Member

Check identity, permission, scope, booking state and review point before acting on an appointment request from a family member or carer.

By DripTell EditorialPublished November 13, 2026Reading time 4 min read
Clinic practice manager reviews two blank scope cards while an adult family carer holds a sealed envelope

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”.

Four trays separate messenger identity, permission, appointment action and review using blank physical objects
Identity, permission, the appointment action and the review point need separate evidence.
Five facts before an appointment actionKeep identity, authority, task, booking state and review separate.
  1. 1MessengerRecord who is asking and the approved identity check.
  2. 2PermissionName the accepted source of authority.
  3. 3ScopeLimit access to the exact appointment task.
  4. 4Booking stateUse the authorised system as the source of truth.
  5. 5ReviewSet a review, expiry or specialist handoff point.
  1. Messenger: who is asking and how the clinic checked that identity under its approved process.
  2. Permission: the source of authority, such as recorded patient consent or an approved proxy-access process.
  3. Scope: the exact task allowed, such as booking or cancelling an appointment.
  4. Booking state: what the authorised appointment system currently shows.
  5. 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 requestMinimum operational checkSafe next step
Book an available appointmentMessenger, permission and booking scope are currentOffer approved options and record the chosen slot
Move or cancel an appointmentPermission covers changes and the booking is foundUpdate the booking system before confirming
Ask whether an appointment existsDisclosure is within the recorded scopeAnswer only through the approved channel
Request results or clinical adviceAdministrative scope is insufficientRoute to the clinic’s authorised clinical process
Permission is missing or unclearIdentity or authority is not establishedPause, 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

All fields are required.

+971

Your request goes to a person, not a mailing list.

By sending this, you agree to an acknowledgment and follow-ups about your request from DripTell on WhatsApp or email, including automated messages. You can ask us to stop at any time. See our privacy policy. Google Analytics counts each request. Depending on your cookie choice, Meta and OpenAI are also told, so we can measure our ads, and Meta receives your contact details in hashed form.

DT

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