Patient communication · Documents · messages · recorded attempts
Message from the clinic record—not a personal phone.
Share appointment details, consent links, bills and clinic-approved post-op instructions through supported WhatsApp workflows. Keep the message attempt connected to the record behind it.
01Explicit WhatsApp consent and suppression states
02Supported appointment, invoice, consent and post-op sharing workflows
03Message and delivery-attempt history connected to record context
04Clinic-branded public contact card with QR, link and vCard sharing
Why this workflow matters
THE CLINIC MOMENT
A delivered message is not a clinic outcome.
The patient needs a consent link before treatment, an invoice after care and approved instructions to take home. Sending each from a personal phone loses the clinic record and makes it harder for the next team member to see what happened.
×Messages sent from personal phones are difficult to govern, relate to clinic records or review when a patient asks what was sent.
×The next owner and source record are unclear.
✓Share appointment details, consent links, bills and clinic-approved post-op instructions through supported WhatsApp workflows. Keep the message attempt connected to the record behind it.
✓Open the record you need without searching for the patient again.
HOW IT WORKS
Check eligibility, template, attempt and source-record outcome.
Follow the task from its first entry to the next person who needs it.
- 01
Qualify
Check consent, DND or suppression, phone number, template and event eligibility.
- 02
Preview and send
Review the appointment details, consent link, invoice or aftercare document and submit through the supported provider workflow.
- 03
Return to the source
Review the message attempt separately from the signed consent, payment or saved appointment outcome.
ONE WORKFLOW · 4 CHECKPOINTS
Send the right clinic document from the right record.
Appointment details, consent links, bills and post-op instructions have different purposes. Keep each sharing attempt distinct from the outcome it supports.
Check consent, suppression and recipient eligibility.
A workflow can be blocked before content is submitted to a provider.
PATIENT CONTEXTPatient 024Crown delivery · connected records
ConnectedPreview the document and its message.
Use clinic-approved post-op instructions and the supported provider template. Check the patient, visit and link before sending.
PATIENT CONTEXTPatient 024Crown delivery · connected records
ConnectedRetain the provider submission state.
Submitted, delivered and failed are different provider states; none proves the clinic outcome.
PATIENT CONTEXTPatient 024Crown delivery · connected records
ConnectedKeep sharing history with the visit.
Review the recorded attempt in its clinic context. Sending the link does not prove that the patient read or followed the instructions.
PATIENT CONTEXTPatient 024Crown delivery · connected records
ConnectedUseful messages, in context
One patient conversation. Several distinct clinic tasks.
Start from the record that explains the message. Share supported appointment details, a treatment proposal, a consent request, an invoice or post-op instructions through the relevant clinic workflow.
Each message has a purpose and an owner. A patient receiving a document is different from a patient signing consent, paying a bill or confirming a visit; those outcomes belong in their source records.
What the team shares—and what it checks next
What the team shares—and what it checks next
| Checkpoint | Patient-facing item | Source to review |
|---|---|---|
| Appointment | Visit details or eligible reminder | The saved appointment and its status |
| Consent | Secure document review and signing link | The treatment’s consent record |
| Bill | Secure invoice link | Invoice, payment history and balance |
| Post-op care | Clinic-approved aftercare link | The appointment’s instruction and sharing history |
Appointment
Patient-facing itemVisit details or eligible reminder
Source to reviewThe saved appointment and its status
Consent
Patient-facing itemSecure document review and signing link
Source to reviewThe treatment’s consent record
Bill
Patient-facing itemSecure invoice link
Source to reviewInvoice, payment history and balance
Post-op care
Patient-facing itemClinic-approved aftercare link
Source to reviewThe appointment’s instruction and sharing history
Consent first
Make eligibility part of the workflow
Thirty2OS stores WhatsApp consent state and distinguishes staff-recorded consent from provider suppression. DND and automation rules are evaluated before eligible automated or preselected communication paths proceed.
A clinic cannot remove a provider suppression simply by toggling a local opt-in.
Approved templates
Keep production messages aligned with provider requirements
Choose an approved template, review the patient-specific details and check its approval status before sending. Live WhatsApp messages follow the clinic’s configured provider workflow.
Supported contexts include appointment confirmations and reminders, recall reminders, invoice reminders, payment acknowledgements, consent follow-up and selected manual messages.
Measure your own result
Track sends and clinic outcomes separately
Message and delivery-attempt history shows what the platform submitted and the provider state available to it. Appointment status and payment records show the operational outcome.
Care after the visit
Send the clinic’s approved post-op instructions
Choose the clinic-approved post-op template for the appointment, attach it to the visit and preview the patient-facing instructions. Staff can use the supported print, link, WhatsApp or email workflow as appropriate.
An authorised team member deliberately shares the instructions and can review the recorded attempt. When the clinic requires post-op instructions and they are missing or not yet shared, eligible work can appear in the Action Engine.
Prepare the instructions, then share deliberately
Prepare the instructions, then share deliberately
- 01Select and attach
Use the clinic-approved template relevant to the recorded treatment.
- 02Preview
Check the instructions and patient context before the link leaves the clinic.
- 03Share and review
Send through an eligible channel and keep the sharing attempt with the visit.
A trusted clinic contact
Give patients one clinic-branded card they can open, share and save
Publish a clinic contact card with the phone number, WhatsApp, email, directions, hours, services, website and social links the clinic chooses to show. Patients can open the public link, scan its QR code and use its downloadable vCard to save the clinic.
Visibility controls and readiness warnings help the clinic review what is public. If a link needs to be retired, an authorised user can rotate it and share the replacement.
From clinic details to a saved contact
From clinic details to a saved contact
- 01Choose what is visible
Review phone, WhatsApp, email, address, hours, services, website and social links.
- 02Share the public card
Copy the link or use the generated QR code in the clinic.
- 03Help the patient save it
The patient can call, message, open directions or download the clinic vCard.
- 04Review or rotate
Use readiness warnings, visibility controls and link rotation when details change.
Permissions and workflow boundaries
ROLES & PERMISSIONS
Provider state and clinic responsibility remain separate.
Message access and live messaging setup should be limited to authorised users. Clinical and front-desk roles may have different responsibilities around template content and operational follow-up.
WHERE IT STOPS
What your team still decides.
Provider setup and template approval are required. Submission is not handset delivery or patient response. The contact card does not capture enquiries or create patient records. No active SMS delivery or guaranteed no-show reduction is claimed.
Plan your trial
TRIAL PLAN
Test one eligible and one blocked message.
Try these tasks with fictional patient details and the roles your team uses. Note any setup question or step that needs a different process.
- Test opted-in and suppressed patients
- Preview a consent and invoice link
- Attach and share clinic-approved post-op instructions
- Inspect a failed delivery attempt
- Review contact-card visibility and readiness warnings
- Scan its QR and download the vCard
QUESTIONS TO ASK
Can staff send unrestricted production messages?
Do not assume that. Production workflows should use approved templates and configured provider controls.
Does WhatsApp guarantee fewer no-shows?
No. Communication can support a workflow; attendance depends on many factors and should be measured separately.
YOUR CLINIC · YOUR EXCEPTION
Bring the handoff that keeps breaking.
Start free to test the workflow yourself, or book a guided demo when you want help mapping the exception.