How the practice works
Opening hours, which services are offered, how to register, what to bring, where to park, which door.
PRACTICE FRONT DESK
In a medical practice an AI receptionist should be scoped narrowly: opening hours, how to register, how repeat prescriptions work, how results are given out, and booking a routine appointment. Symptoms, triage, results and emergencies belong to people, without exception.
Practice phone lines fail in a predictable way: everyone calls at once, at the moment the lines open, for a mixture of reasons that mostly are not appointments. Repeat prescriptions, sick notes, results, registration questions, and directions. The clinical calls queue behind the administrative ones.
A messaging receptionist changes the shape of the queue rather than the size of it. Administrative questions are answered as they arrive, at any hour, and the phone line carries fewer of them. That leaves the people answering phones with more capacity for the calls that genuinely need a person.
None of this makes the software clinical. It is deliberately the opposite: it deals with the part of the front desk that is pure process.
Opening hours, which services are offered, how to register, what to bring, where to park, which door.
How to request one, how long it takes, where to collect it. The process, never the medication.
When to expect them and how they are given out. Never the results themselves, and never over a message.
For appointment types the practice has agreed can be booked without clinical assessment.
Sick notes, referral letters, registration paperwork: what is needed and how long it takes.
Anything outside the agreed list goes to a person, with what the patient already said attached.
If a vendor is willing to let their software triage, treat that as information about the vendor.
Two conversations should happen before the technical one. The first is with whoever owns information governance at the practice: what is being sent, where it is processed, what is retained and for how long. A practice remains responsible for patient information whichever tool it uses.
The second is about scope, written down. Agree the exact list of things the receptionist may answer, and the exact triggers that hand over. Practices that skip this end up discovering the boundary through a complaint.
Elily runs on your practice's own WhatsApp number through the official WhatsApp Business Platform. That is a starting point for the governance conversation, not the end of it.
Send Elily your practice website on WhatsApp. Ask her the five questions your reception team answers most, and check that the sixth one, the clinical one, stops and fetches a person.
QUESTIONS BEFORE YOU START
It should not, and Elily is not set up to. Triage is a clinical judgement about urgency and belongs to clinical staff. The safe scope is process questions and routine booking, with an immediate handover for anything describing symptoms.
It can explain your process, tell a patient what you need and how long it takes, and route the request to the right place. It should not make decisions about medication or confirm that a prescription will be issued.
The conversation should hand over immediately and tell the patient to use their local emergency number rather than waiting for a reply. Configure and test that path before anything else goes live.
That is a decision for the practice, not for a vendor. It depends on your local rules, your information-governance position and what you are willing to send in a message. Elily runs on your own number through the official Platform; the policy call remains yours.
KEEP READING
THE NEXT MESSAGE CAN BE HERS
Send Elily your practice website on WhatsApp and test where she answers, where she routes and where she refuses.
Last updated