Key points
- One thread per patient keeps email, WhatsApp, web forms and calls in a single history the whole team can read.
- Match on a verified phone number or email address, and confirm two details before sharing anything personal with a new one.
- In an audit of 2,241 US companies, 23% never replied to a web enquiry.3 A single queue makes every unanswered message visible.
- In the UK, a patient can make a subject access request in writing or verbally, including via social media, and the clinic usually has one month to respond.1
- wai keeps every channel in one thread per patient, drafts each reply and holds it for the team's approval.4
Summary
Match every email, WhatsApp message, web form and call to one thread per patient, give each kind of message an owner, and have a person approve every reply. Anyone on the team can then pick up the full history, with an audit trail of who said what.
Every patient message lands in one thread, so whoever answers already has the whole history in front of them. A patient who emailed on Monday and rings on Friday has an approved reply within minutes and never repeats themselves.
See it in your clinicThirty minutes on your own patients and doctors.
Request a demoSee an email and a WhatsApp message from the same patient land in one thread, with a reply drafted for your team to approve.
| Channel | Identifier used to match | What to set up | Watch for |
|---|---|---|---|
| Email address | Route the clinic's shared address into the inbox | Family members writing for a patient from their own address | |
| Mobile number | Use one clinic business number on every channel | Personal numbers clinicians have given out | |
| Web form | Email or mobile typed by the patient | Make both fields required and check the format | Typos that create a duplicate patient |
| Phone call | Caller's number | Log every call, answered or missed, to the thread | Withheld numbers and shared landlines |
| Text message | Mobile number | Send texts from the clinic's name and number | Replies to old reminders landing outside the inbox |
Why one thread per patient
The receptionist who picks up Friday's call sees Monday's email and Tuesday's WhatsApp, so the patient hears the same price and the same answer from everyone.
In an audit of 2,241 US companies sent a test web enquiry, 23% never responded at all.3 A single queue of open threads shows every message still waiting.
In a 2020 survey of 30 finance executives at large US health systems, 53% named multiple disparate software platforms as a challenge in meeting data-sharing requirements.2
Matching each message to the right patient
Each channel arrives with its own identifier, a phone number for WhatsApp, texts and calls, an email address for email, and whatever the patient typed into a web form. A message joins an existing thread when its identifier matches one already verified on that patient's record.
When a new number or address claims to be an existing patient, the reply confirms two details, usually date of birth and postcode or the date of the last appointment, before it shares anything personal. Never merge threads on a name alone, since a few thousand patients will include two who share one.
Who owns which message
Ownership follows the type of message, whatever channel it came from. A booking change belongs to the front desk and a question about a result belongs to a clinician.
Each open thread has one named owner at a time, shown in the queue. When the owner changes, the thread moves with its whole history attached. The guide to human approval for patient messages sets out a starting map of who approves what.
Approval and an audit trail
wai Admin drafts each reply inside the patient's thread in the clinic's voice, across email, web forms, WhatsApp and calls, with missed calls answered by a drafted text.4 Nothing operational sends without the team's approval, and nothing clinical sends without a clinician's signature.5
Every message, draft, approval and signature is written to an event log the clinic can export.5 The ICO says a person can make a subject access request verbally or in writing, including via social media, that an organisation must make a reasonable and proportionate search, and that it should respond within one month.1 One thread per patient and an exportable log make that search a single export.
Setting it up in a week
Inventory every way a patient can reach the clinic, including the personal mobile a clinician once gave out and the old contact form. Bring each one into the inbox or close it with a message pointing to one that is.
Route each channel into the shared inbox, set the matching rules, agree owners by message type and write a one-page tone guide on greetings, sign-offs and what the clinic never says by message. Run old and new inboxes side by side for one week, then switch the old ones off.
Where to start
List every channel and count last month's messages on each. Write the matching rule and the two confirmation details. Agree the owner for bookings, payments, clinical questions and complaints, and name a deputy for each.
Measure the time from a patient's message to the approved reply, by channel, before and after the switch. Calls need their own plan, covered in the guide to missed-call follow-up.
Bring a sample of your own messages from each channel. We show you how they land in one thread per patient, with drafts and approval.
Frequently asked questions
Can WhatsApp, email and calls really share one thread?
Yes. wai Admin keeps email, web forms, WhatsApp and calls in one thread per patient, with full history, and drafts each reply inside that thread.4
How are messages matched to the right patient?
By a verified phone number or email address on the record. A message from a new identifier that claims to be an existing patient is confirmed with two details before anything personal is shared.
Who should own a message that arrives on WhatsApp?
Whoever owns that type of message. Bookings and payments go to the front desk, clinical questions to a clinician and complaints to a named senior team member.
Does a single inbox help with subject access requests?
Does the AI send replies on its own?
No. Every reply is drafted and held, and a person at the clinic approves it before it sends.5
How long does the switch take?
About a week. Inventory the channels, set rules and owners, then run the old and new inboxes side by side for seven days before switching the old ones off.
Sources
- 1Information Commissioner's OfficeA guide to subject accessRead 14 October 2026Read source
- 2Deloitte, 2021Greater transparency and interoperability in health careRead 14 October 2026Read source
- 3Harvard Business Review, Oldroyd, McElheran and Elkington, 2011The Short Life of Online Sales LeadsRead 14 October 2026Read source
- 4wai, 2026wai Admin, the front desk and back officeRead 14 October 2026Read source
- 5wai, 2026Security at waiRead 14 October 2026Read source
Every patient answered in minutes, with the whole history in view
Fifteen minutes on your own inboxes and phones, with every reply drafted by wai and approved by your team. We reply within one working day.
Partner with us
See it on your own patients, then build it with us
Thirty minutes on your own patients, doctors and rules, in your market. We reply within one working day, and the clinics that partner with us early shape what we build next.
Read how doctor on demand works in a clinic