Practice email, where the reception phone is already ringing
A practice reception has a phone ringing, someone at the desk, and an inbox nobody is watching. The email queue is appointments, reminders, forms, and the same eight questions, and it gets answered in the gaps between everything else, which means slowly.
4 min read
The clinical line
Before anything else, because it is the only rule that matters absolutely: the agent never gives clinical advice, never interprets symptoms, and never says whether something needs to be seen urgently.
Not a softened version, not a general reassurance, not "that does not sound serious". Anything describing a symptom, an injury, a reaction, or a worry about one goes to a clinician, immediately, with the agent doing nothing more than acknowledging and saying who is coming.
The failure here is not embarrassment, it is harm, and it is the reason the safe categories below are drawn narrowly.
What is safe
Appointments. Booking, moving, cancelling, and the waiting-list backfill when someone drops out. The scheduling loop, against real availability, per appointment reminders that can handle the reply.
Reminders. With the practical details, and crucially with a reply path so "can we move it" is handled rather than ignored.
Practical questions. Opening hours, parking, what to bring, how long an appointment takes, whether a form needs completing beforehand, what happens if you are late.
Forms and paperwork. Sending the right one, chasing the ones outstanding, and confirming receipt. This is where a lot of reception time goes and none of it needs judgement.
Payment and invoice logistics. Amounts owed, how to pay, receipts. Not discounts or disputes.
| Message | Agent | Practice |
|---|---|---|
| Book, move, or cancel an appointment | Yes | |
| What to bring, where to park, how long | Yes | |
| Send and chase forms | Yes | |
| Invoice and payment logistics | Yes | |
| Any symptom, worry, or clinical question | Immediately | |
| Results, or anything about a diagnosis | Always | |
| Medication, dosage, or a reaction | Immediately | |
| Complaints | Always |
Recognise urgency, do not assess it
The distinction that makes the safe list workable. The agent is not judging whether something is serious, it is recognising that a message contains clinical content at all and routing it fast.
Design that route explicitly, including what happens outside opening hours. A message arriving at 22:00 describing a symptom needs a reply that names the emergency number and says when the practice opens, rather than a cheerful confirmation that somebody will look tomorrow. That reply is written once and matters enormously the night it is used.
Health information in an inbox
Even a practice agent that only books appointments will receive messages containing health information, because patients include it whether you ask for them to or not.
Three consequences worth deciding deliberately rather than discovering. Send the model only what the task needs, per sending the model less than you think it needs. Know which provider processes message content and under what terms, per where the mail actually goes. And keep message bodies out of application logs, which is the most common accidental copy.
Whether email is an appropriate channel for particular content at all is a decision for the practice under its own regulatory obligations, and one worth taking before deployment rather than after.
Where the return is
Two places, both boring and both large for a small team.
Backfilling cancellations. A slot freed on Tuesday morning is revenue that evaporates unless somebody contacts the waiting list, and nobody has time to do that at 8am. An agent offering it to the next person in a thread is immediate money.
Reducing no-shows. A reminder with a reply path catches the person who meant to rearrange and would otherwise have simply not turned up. That is the single most measurable effect, and it is a reminder, not an intervention.
Starting
Appointments and practical questions only, with everything clinical routed from day one, and a fortnight of reading every thread, per the first week with an email agent. Reception staff should be the ones reviewing, because they will spot a wrong answer faster than anyone else and they know which questions they are tired of.
Questions
- Can an AI agent handle email for a dental or veterinary practice?
- For appointments, reminders, forms, practical questions, and payment logistics. Never for anything clinical, which is routed immediately to a person.
- What counts as clinical?
- Any symptom, worry, injury, medication question, result, or reaction. The agent recognises that clinical content is present and routes it; it does not assess how serious it is.
- What should happen out of hours?
- A reply that names the emergency route and says when the practice opens. Written once, and the most important message in the whole setup.
- What is the biggest financial return?
- Backfilling cancelled slots from the waiting list, which nobody has time to do manually, followed by fewer no-shows from reminders that can be replied to.
- Is health information in the inbox a problem?
- It arrives whether you invite it or not, so decide deliberately what reaches a model, which provider processes it, and what your logs retain.
- Who should review the threads?
- Reception staff. They spot a wrong answer fastest and know which questions are eating their day.
Give your agent an address it can answer from.
Create an inbox