Fast, polite replies to new-patient and treatment enquiries, designed so that no clinical or health details are requested or stored by the automation.
The auto-reply thanks the person, says when the team will be in touch and asks only for non-clinical details, such as the type of enquiry and the best time to call. It never asks about symptoms or medical history, because health information is special category data under UK GDPR and belongs in your clinical systems.
No. It sits in front of it, handling website and email enquiries that arrive outside the booking system, alerting reception and logging each one so none are missed. It does not connect to clinical records. Anything that would touch patient records is out of scope unless your data protection lead approves it.
You and your data protection lead review the reply wording, the fields collected and where data is stored before anything goes live. I provide a plain description of every step, what data it touches and how to switch it off, so it can be checked against your policies. I am not a compliance adviser.
A good first reply thanks the person, says when a human will be in touch and asks only for what is still missing. For dental practices, that usually means:
OpenAtoZ · AI automationOne repetitive task automated properly, in tools you already own, then handed over with written notes.
OpenAtoZ · WebsitesAnswers common questions from your own approved FAQ and collects the visitor’s name and number into a sheet you own.
OpenAtoZ · AI automationBroken Zap, half-finished n8n flow or a script nobody understands? I trace it, fix it, add error alerts and write a one-page guide.
OpenAtoZ · WebsitesA fast, simple website with an enquiry form that can feed straight into instant replies. You own the domain and hosting.
Describe the job in a few lines. You get a fixed-price scope, or an honest “not for me”.
The auto-reply thanks the person, says when the team will be in touch and asks only for non-clinical details, such as the type of enquiry and the best time to call. It never asks about symptoms or medical history, because health information is special category data under UK GDPR and belongs in your clinical systems.
No. It sits in front of it, handling website and email enquiries that arrive outside the booking system, alerting reception and logging each one so none are missed. It does not connect to clinical records. Anything that would touch patient records is out of scope unless your data protection lead approves it.
You and your data protection lead review the reply wording, the fields collected and where data is stored before anything goes live. I provide a plain description of every step, what data it touches and how to switch it off, so it can be checked against your policies. I am not a compliance adviser.
No. Replies should direct urgent issues to your phone line or NHS 111 as your practice prefers.
It is a fixed quote after scoping.