Start with the enquiry
A patient messages your clinic on WhatsApp. Your team can share a booking link, and configured appointment replies can direct the patient to the relevant doctor and location.
From WhatsApp enquiry to your Plato booking calendar.
Ekko shares the right booking link for the doctor and clinic location. Your patient books in Plato's own calendar, and Plato sends patient and appointment updates back to Ekko by webhook.
Book in Plato's calendar
The link opens the configured Plato booking calendar. The patient chooses an available time and completes the booking in Plato.
Keep Ekko in step
Plato sends webhook updates for patient changes and appointment changes or cancellations. Ekko processes these updates to keep supported records and reminder workflows in step.
See the flow
Watch the patient booking journey
The WhatsApp message, the booking link and the appointment in Plato.
Set up the right doctors, calendars and locations.
A solo practice has fewer mappings to configure. A multi-doctor or multi-location clinic needs each assignment reviewed so patients reach the right booking calendar.
- Connect Plato using your clinic's database and integration credentials.
- Choose the patient import scope per doctor.
- Map Plato calendar colours to the appropriate doctors in Ekko.
- Configure a booking link for each doctor at each clinic location.
- Review the booking journey and sync with the Ekko team during onboarding.
Another workspace, without another manual sync.
Patient changes, appointment changes and cancellations trigger Plato webhooks. Ekko processes them in near real time to keep supported patient records and reminder workflows in step.
- Patient created or updated: patient:upsert.
- Appointment created or updated: appointment:upsert.
- Appointment cancelled or deleted: appointment:delete.
- Supported appointment updates feed Ekko's reminder workflows.
Before you connect
Plato Medical integration questions
Does Ekko create appointments directly in Plato through an API?
In the current patient booking flow, Ekko provides the configured booking link for the doctor and location. The patient opens Plato's booking calendar and books there. Plato then sends appointment updates back to Ekko by webhook.
Can we choose which doctors' patients are imported?
Yes. Patient import scope is controlled per doctor, so the practice can choose who is included when configuring the Plato connection.
How are different doctors and clinic locations configured?
Ekko supports calendar colour mappings to doctors and a booking link for each doctor at each clinic location. Multi-doctor and multi-location practices need these assignments reviewed during setup.
What changes sync from Plato to Ekko?
Plato sends patient:upsert, appointment:upsert and appointment:delete webhooks. Ekko processes these to update supported patient records and appointment reminder workflows in near real time, subject to webhook delivery and processing.
Is the Plato connection credentialed?
Yes. The connection uses your clinic's Plato database and integration credentials. Patient import scope is controlled per doctor. It is not the same connection flow as authorising a messaging account.
Is Plato integration included in Solo and Clinic?
Yes. Plato integration is included in both Solo and Clinic plans. Your clinic needs the appropriate Plato access and connection configuration.
Built around your clinic
Request an integration
Which system would make the biggest difference to your clinic? Tell us what you use. Your request goes to Unni and helps us decide what to connect next.