01The front desk problem, plainly stated
Reception is where a dental practice quietly leaks work. The desk is staffed while you are open, and the people staffing it are also greeting patients, taking payments, chasing recalls and answering the phone. Every enquiry that arrives while all of that is happening waits — and every enquiry that arrives after the door is locked waits longer.
Two things go wrong, and they go wrong differently. Someone in pain does not wait politely: a broken tooth on a Sunday evening sends a person down the search results until a practice responds, and the practice that answers is the one that gets the patient. The quieter loss is the shopper — the person comparing two clinics on whether you take NHS patients, what a check-up costs, and how registration works, who books wherever they get a straight answer first.
Underneath both sits the repeat-question tax. Opening hours, parking, NHS versus private, what a first visit involves, whether you offer a particular treatment — the answers already sit on your website, and reception recites them anyway, one caller at a time, all morning.
02What an AI receptionist for a dental practice actually does
An AI receptionist, in the form Adoomi builds, is a chat assistant that sits on your own website and answers as your practice — there is a ready-made setup for dental practices specifically. It is trained on your website, your published fees and your FAQ pages, and it answers strictly from that approved content. Ask it something you have not published and it says so and hands the conversation to a human rather than improvising. It works around the clock and replies in the patient's own language.
The practical wins are narrow and real: the registration and fees questions answered from your own pages by the website chatbot instead of by a receptionist with a patient waiting at the desk, and the Sunday-evening enquiry that used to sit unread until Monday arriving as something your desk can act on.
03The desk list it answers, and the door it stops at
The useful mental model for a practice is a hard line drawn at the surgery door. On one side is the desk list — the administrative questions a receptionist answers all day without consulting anybody. On the other side is everything clinical, which is a handover, always, with no exceptions and no judgement calls made in chat.
| The message | What the assistant does |
|---|---|
| "Are you taking on NHS patients?" | Answers exactly as your own page states it, including if the answer is that it depends and to ring the practice. It does not promise availability you have not published. |
| "How much is a check-up?" | Gives the figure from your published fee list. Anything set at consultation — a plan, an implant, orthodontics — is captured and passed to the clinician, never estimated. |
| "I've had toothache since the weekend, should I be seen?" | Reads nothing into it. No cause, no urgency rating, no advice. It captures the patient's own words and contact details and emails the clinician you named. |
This is also what makes the review step at setup worth the time. You are not tuning a personality; you are deciding what the practice is willing to say in writing, overnight, to somebody it has never met.
04Out of hours, and the route for a patient in pain
Dental enquiries cluster exactly where the practice is not: the evening after work, the weekend, the bank-holiday Monday. That is when a crown comes off, when a parent starts worrying about a child's tooth, and when somebody finally sits down to compare two local clinics.
The assistant keeps answering the desk list through all of it. What it must never do is decide how urgent a symptom is. Instead it surfaces what your own emergency page already carries — your out-of-hours arrangement, the number to ring, the safety net — and flags the enquiry to the person you named. The instruction is yours; the assistant only relays it.
That published instruction needs no software at all, and it is worth writing whether or not you ever add an assistant. If your site does not carry one, adapt something like this and put it on your contact page — it works tonight, and it is exactly the content an assistant would later surface.
05From enquiry to something reception can act on
Most enquiries arrive unusable. "Do you have anything this week?" tells your desk nothing — not who is asking, not whether they are registered, not what for. The point of lead capture is that the assistant asks the boring questions before a human spends a minute on it, then attaches contact details, the need and the context to one structured enquiry.
- Name and best contact. Mobile for WhatsApp, plus email.
- The reason in the patient's own words. "Filling fell out on the bottom left" carries more than any dropdown, and it reaches the clinician unedited.
- New or registered. Registration status changes who handles the enquiry and how long it takes.
- NHS or private. Asked as your practice frames it, so nobody is told something your pages do not say.
- Urgency in their own terms. Captured as the patient described it — never rated, scored or triaged by the assistant.
Then the handoff. The patient can continue with your team on WhatsApp, and the original question plus every captured detail travels with them, so nobody opens with "hi, what's the problem?" at someone who has already explained it twice. Email alerts do the internal routing: fees and registration to reception, clinical wording to the clinician you named, and anything safeguarding-adjacent — a child patient, a vulnerable adult — to one named person rather than the general inbox.
The enquiry arrived on Sunday evening and was answered on Sunday evening. Your desk opened Monday to a named patient, a question in their own words, and a clinical flag already sitting with the right clinician.
06The lines it will not cross
In dentistry an assistant that oversteps is not an embarrassment, it is a risk. So the limits are the product, and they are worth reading before the features:
- No clinical advice, ever. It will not read a symptom, name a cause of pain, comment on an X-ray, suggest a painkiller or antibiotic, or say how soon someone should be seen. Each of those stops the conversation and emails the clinician you named.
- No invented fees. Figures come from your published fee list or not at all. Treatment set at consultation waits for the consultation — the assistant captures the enquiry instead of estimating.
- No booking, holding or moving appointments. It does not touch a diary and cannot see one. It captures who needs what and when they are free; your desk books.
- No NHS promises. Availability changes by practice and by season. It repeats what your page says today and nothing beyond it.
- No phone answering. Restated because "receptionist" implies otherwise: your phone line is untouched today, and the AI phone agent remains waitlist-only.
One more boundary, on data. Chats are EU-hosted, GDPR export and deletion are built in, logs hold no message content, and the chat window sets no tracking cookies. None of that makes your practice compliant with anything — compliance is your registration, your policies and your processes. It just means the assistant is not quietly working against them.
07Which patients the assistant reaches, and which ones ring
Some practices are phone-first, and the assistant does not change that. Adoomi answers on the practice website, not on the phone line, so a list that rings by habit also needs a telephone answering service. The assistant only meets patients who land on your website, so search traffic has to be there first. Where it is, Adoomi covers the patient who searched instead of ringing. They read the fee page on a Sunday evening, type a question and get an answer there and then, at any hour, without anyone at the desk touching it.
Otherwise, run the arithmetic from your own records rather than anyone's brochure:
- Count last month's misses. From the phone log, tally the evening and weekend calls nobody answered, then add the website and email enquiries that waited a day or more for a reply.
- Price the phone side. If you already pay an answering service, multiply those calls by your own per-call or per-minute rate from your tariff sheet — not an assumed market figure.
- Price the website side. Set that against a flat £8/month — Adoomi's Local plan, 200 message credits. The two catch different people: the service catches whoever rings, the assistant catches whoever searched, landed on your page and never picked up the phone.
Whatever step one shows arriving through the website is the share £8 a month covers. Those patients get answered without the desk touching it, and the fee and appointment questions that fill Monday morning arrive already handled. Plenty of practices run both, a person on the line and the assistant on the site, because each reaches patients the other never meets.
08Setup, cost and the review step that matters
Setup takes about ten minutes: connect your website, review the answers the assistant proposes to give, and add one line to your website. For a practice, the review step is the whole job. Read the out-of-hours wording as a patient in pain would read it. Confirm that anything clinical hands straight over. Check every fee against your published list, and check the NHS wording says what your page says — not more.
Pricing is flat and practice-shaped: a Free plan at £0 with 50 message credits a month — one credit covers one AI answer — then £8/month (Local, 200 credits), £20/month (Growth, 500) and £75/month (Scale, 4,000). The full plan comparison has the detail. Hosting is EU-based, with GDPR data export and deletion built in and no tracking cookies in the chat window.
Frequently asked questions
The questions practice managers ask in the first 20 minutes of a demo, in order.