Operations HQ connects Plato to your clinic's WhatsApp number. Patients book, move and cancel by chat, and every change lands in Plato in your front desk's own note format.
The appointment note before and after. Only the time changes.
Logged: patient matched by phone, Dr Tan on duty Saturday, slot re-checked, written by the assistant after the patient confirmed.
Your clinic creates a Plato API key that can only call the endpoints you tick. Plato refuses every other request made with it.
A selection. The full list, with screenshots of each box to tick and the ones to leave alone, is in the Plato setup guide.
Operations HQ applies the rules your team already follows, set once in settings and changeable by your staff.
The treatment and requested doctor are read from notes like "Check-up · Request Dr Tan" and written back the same way.
An approved list, such as "Scalling" for "Scaling". A note that still matches nothing goes to your team, never guessed.
Only practitioners on duty who perform that treatment are offered, for the full length of the treatment.
Each outlet sets how many of each treatment a slot can hold, for example up to 4 consultations and 1 health screening at 1pm.
Mark a practitioner's leave in Operations HQ. Their slots stop being offered and the outlet gets the list of bookings to rearrange.
When Plato marks a treatment completed or an invoice issued, after-care, review and next-visit messages start on their own.
The clinic and patients are fictional. See all eight examples.
respond.io runs the WhatsApp conversation. Operations HQ does the multi-step booking work against Plato that a chat platform is not built to do on its own.
In the first 3 working days we confirm what your Plato allows and send the findings in writing. If an endpoint is missing, we agree an alternative or take that feature out of scope. Nothing extra is charged without your written agreement.
The scoped key works for appointments, slots, calendars and patient look-up.
One Plato per brand, or a shared account where brands, outlets and doctors are clearly identified.
Your note format, treatment list and whether package balances and recalls are readable.
Every reminder and auto-reply already running, so patients never get two.
No. Zelix Labs is an independent company that connects to Plato through the API key your clinic creates. Plato is a trademark of its owner.
No. The scoped key covers appointments, available slots and patient look-up only. Clinical notes, lab results, payments and stock stay out of reach, and Plato refuses any request outside the endpoints you tick.
Any Plato fee for API access is between your clinic and Plato. It is paid directly and not marked up by us.
No. Before go-live we list every existing reminder, auto-reply and broadcast. Those that duplicate the assistant are switched off with your written approval.
Yes. Each brand gets its own compartment in Operations HQ, connected only to that brand's Plato and that brand's WhatsApp workspace, with its own API key.
Plato is checked again immediately before every write. If the slot has changed, the patient is offered times again and nothing is overwritten.
Message us on WhatsApp. We will run the demo with your treatment list and note format.
Book a 20-minute demo