A calendar that matches your opening hours
The visible day window is configured per clinic, so the calendar shows your session times instead of a generic midnight-to-midnight grid.
Platform · Patients & messaging
The clinic that remembers to call the diabetic patient in month four is not more caring than the one that forgets. It has a system that knows who is due.
Patient A · 09:12
Doctor, can I come back tomorrow?
Front desk · on duty · 09:14
Dr A has 3pm free tomorrow. Shall I book it?
Template · appointment confirmed
18 Aug, 3:00pm · Dr A · Sample clinic
The thread lives on the patient, not on somebody’s phone.
Getting them in
Bookings, changes and reminders run through one schedule the whole front desk shares.
| Time | Doctor | Patient | Status |
|---|---|---|---|
| 14:00 | Dr A | A-031 | Confirmed · WhatsApp |
| 14:15 | Dr A | A-032 | Rescheduled |
| 14:30 | Dr B | Open | Bookable online |
Confirmations and changes go back and forth on WhatsApp, and the front desk sees the same schedule.
The visible day window is configured per clinic, so the calendar shows your session times instead of a generic midnight-to-midnight grid.
Bookings against the practitioner and the resource, including locum sessions, without double-booking the treatment room.
Scheduled reminders on the channel the patient actually reads, sent by a background worker rather than by someone remembering.
A booked patient checking in joins the same waiting-room queue as a walk-in, with the booking still visible.
Talking to them
Patients already message the clinic. The question is whether those messages live on one staff member’s personal phone.
Inbound WhatsApp arrives in a clinic inbox the whole front desk can see and answer, tied to the patient record rather than a private handset.
A conversation sits on the patient it belongs to, so the person answering has the visit history in front of them.
Appointment confirmations, results-ready notices and follow-up prompts as approved templates with the variables filled from the record.
Reach a cohort — a tag, a chronic group, a vaccination cycle — with delivery tracked per recipient.
A patient who stops marketing messages stops receiving them, while transactional messages like a medical certificate or a receipt still go through.
New inbound messages raise an in-app notification and an optional browser push, so a message at 4pm is not discovered at 7pm.
Bringing them back
Who needs to come back, reached on the channel they read, with a record of who it reached.
Chronic-disease patients due for follow-up are identified from their follow-up date, not from a list someone maintains by hand. CDMP support is coming soon.
Schedule-driven reminders for the doses that are due, including childhood series.
Any patient tag can drive a recall — corporate screening, post-procedure review, a specific medication cohort.
Delivery status per recipient, so a recall campaign is a measurable action rather than a hopeful one.
Seeing them remotely
Patients join from a mobile web page. Each doctor and channel can have its own link, so you know where a patient came from.
Online payment by PayNow or card, with the receipt issued from the same invoice the clinic sees.
It creates the same record as an in-person visit — coded, prescribable, submittable — not a note in a separate telehealth silo.
The MC is generated and delivered digitally, with the same numbering and searchability as one issued at the counter.
Questions
The clinic number is connected to WhatsApp Business; coexistence with an existing number in use on a phone is supported during onboarding.
Booking links can be shared per doctor or channel. What the patient can self-serve is a setting, not an all-or-nothing switch.
Marketing messages honour opt-out, transactional messages are kept separate, and every send is recorded against the patient.
Next step
Thirty minutes, screen shared, using your workflow — your busiest hour, your payer mix, your claim types. We will tell you plainly if we are the wrong fit.
No slide deck. No obligation.