Nearly every clinic we onboard runs enquiries through WhatsApp, and nearly every one of them defends it with the same argument: it is where the patients are. That argument is correct. Patients in Germany, the Gulf and the UK do live in chat apps, they will not install anything new to talk to you, and a clinic that insists on a web form loses to the clinic that answers on the channel the patient already has open. The problem is not the channel. The problem is what happens when the channel is also your CRM, your inbox, your audit trail and your reporting layer at the same time.
The failure is a handover failure
At ten enquiries a month, one coordinator with a phone is a perfectly good system. At fifty, cracks appear. At a hundred and fifty, across three coordinators and two time zones, the thing that breaks is almost never the messaging — it is the handover. A patient writes at 23:40. The coordinator who was chatting with them is off tomorrow. Nobody else can see the thread, nobody knows a quote was verbally promised, and the patient — who is comparing four clinics — books with whichever one replied by lunchtime.
Trace the specific breakages and they are consistent across every clinic that has outgrown the setup:
- Threads are trapped on a device. A coordinator on leave, sick, or resigning takes the pipeline with them. Some clinics have literally bought a phone back from a departing employee.
- No ownership. Either two people answer the same patient with two different prices, or nobody does because each assumed the other had it.
- No status. "Quoted", "waiting on scans", "deposit sent" exist only in someone's head. There is no list of patients who went quiet nine days ago, so nobody chases them.
- Quotes rot. A price typed into a chat bubble at midnight cannot be versioned, cannot be corrected cleanly, and will be screenshotted back at you at the front desk four months later.
- Clinical documents in a consumer app. Scans, blood work and photographs sitting in a personal chat backup is a data-protection exposure most clinic owners have not actually priced.
- No numbers. You cannot answer "how many enquiries did we get last month, and what share converted" without a person scrolling a phone for an afternoon.
Speed is why you tolerate all of it
Be fair to the incumbent: WhatsApp wins on the one metric that matters most. Health-tourism patients contact several clinics and disproportionately book with one of the first to come back with something concrete. A chat app gives you a notification on the device that is already in the coordinator's hand, and that is a real operational advantage over a webmail inbox nobody has open.
So the goal is not to move patients off chat. It is to stop the clinic side from being a personal phone. Those are different problems, and conflating them is why so many clinics buy a heavy CRM, watch the coordinators quietly keep using WhatsApp because the CRM is slower, and end up with two systems and no truth in either.
What a shared inbox has to do to earn the switch
A patient inbox that a coordinator will actually adopt is judged on friction, not features. Ours is a short list, and any tool that fails it will lose to the phone:
- Every thread visible to the whole team. Not shared on request — shared by default, with the full history including what was quoted and when.
- One named owner per enquiry, reassignable in a click, so the question "who has this patient" always has an answer.
- Status you can filter. New, quoted, awaiting documents, booked, lost. If you cannot pull "everything quoted more than seven days ago with no reply", you will not follow up, and follow-up is where a large slice of your bookings actually comes from.
- Quotes as objects, not prose. Itemized, versioned, with a date, so "what did we offer this patient" is a lookup rather than an argument.
- Documents attached to the patient, not to a phone's photo roll.
- Reply speed measured, per coordinator and per week, because the metric you do not measure is the one that drifts.
On GetClinic: enquiries land in a routed lead inbox shared by your whole team, with treatment, budget and timeline already stated. From the same thread you build an itemized quote, keep talking in patient chat, run a video consult, and put the date on the booking calendar — and the analytics view tells you how many leads became quotes and how many quotes became bookings, without anyone scrolling a phone.
Run them side by side, deliberately
The pragmatic answer for most clinics in 2026 is not "portal instead of chat". It is chat as a notification surface, portal as the system of record. Patients keep messaging where they are comfortable. The clinic keeps one place where the thread, the quote, the documents and the booking live, and where a second coordinator can pick up a conversation cold and be useful in thirty seconds.
What makes that work is a rule the team actually follows: nothing is real until it is in the portal. A price agreed in chat is not a quote until it is issued as one. A date agreed in chat is not a booking until it is on the calendar. Coordinators will resist this for about a fortnight and then defend it, because it is the rule that stops them being personally liable for a number they typed at midnight.
The migration, honestly
Do not export three years of chat history. It is not worth it and nobody will read it. Draw a line on a Monday: every new enquiry from that date is created in the shared inbox, and open threads with a live quote get transcribed once, by hand, with the current quote and status. Two hours of work for most clinics. Everything else is allowed to die where it is.
Then watch two numbers for a month. Median first-reply time should hold or improve — if it worsens, your new tool is too slow and the team will drift back to the phone. And the number of enquiries with no activity for over seven days should fall sharply, because for the first time somebody can see them. That second number is where the switch pays for itself: those patients were always there. You just could not find them.