Proof of work · In build
eMpilo
An AI assistant that handles clinic appointment booking so a doctor doesn't have to. The first demo: a single doctor at a South African government hospital, with no admin staff. This page describes the designed flow — the build is in progress, and no patient data appears here, or anywhere, until the hospital's own data-governance rules are settled.
The problem it's built for
A single practitioner with no admin staff, handling appointment requests over WhatsApp because that's where patients already are. The assistant needs to feel usable by one doctor from day one — not a system that assumes a front desk.
No screenshots here on purpose — nothing is deployed yet, and nothing with real patients will be shown until compliance is settled.
The designed flow
Patient side
Message the clinic's WhatsApp number → the assistant converses and books an open slot → a confirmation is sent → a reminder follows ahead of the appointment.
Doctor side
Booking confirmations arrive as they happen, visible on a calendar the doctor already uses. Moving, cancelling, or rescheduling is done by chatting with the assistant directly — the patient is notified automatically.
What's still open
Honestly, most of the stack: the WhatsApp channel (Meta's Cloud API vs. a BSP vs. Twilio), the orchestrator (a thin slice is being built on both n8n and an alternative before committing), which calendar to support first, and whether the calendar or a database is the system of record. The one thing that isn't open is compliance — this is patient health information at a government hospital, so explicit patient consent wording, data minimisation, and a retention position have to be settled, and the hospital's own data-governance rules confirmed, before any real patient passes through it.