AI Receptionist for Dentally Dental Practices

A UK dental practice runs two businesses through one phone, and the caller rarely knows which one they belong to. "Am I NHS or private with you?" is one of the most common opening questions a dental receptionist hears, and getting the answer wrong, booking an NHS patient into a private slot or quoting a private fee to someone entitled to an NHS check-up, is the kind of mistake that ends in an awkward conversation at the desk and a patient who feels misled. On a Dentally practice, the first job of the phone is not booking; it is knowing which of the two books the caller belongs in.

We build the Dentally connection, and this is about keeping those two books straight: sending each caller to the right list, at the right rules, and writing the appointment into Dentally where it belongs.

The NHS book and the private book are not just two calendars; they run on different rules. NHS recall intervals are set by clinical need and by what the contract allows, private slots carry a fee, and a new patient's route depends on whether the practice has NHS capacity at all. 2care determines which book a caller belongs in from the practice's own Dentally setup and books them there, so the two lists stay separate the way the practice needs them to.

The caller	What the agent determines	Where it books
An NHS patient, check-up due	Their recall interval on the NHS list	The NHS book, at the right interval
A private patient	The fee and private availability	The private book, with the fee quoted
A new patient, unsure which	Whether the practice has NHS capacity	The list with room, explained plainly
A cancelled private slot	The waitlist for that treatment	Offered to the next private patient
An urgent problem	The urgency, on either list	An urgent slot, or a person

The middle row is the delicate one. Where a practice's NHS list is full, the honest answer is that the patient can go on a waiting list or be seen privately, and the agent gives exactly that answer rather than quietly booking them privately as though there were no choice. Being straight about NHS availability is what keeps a practice out of trouble and a patient feeling fairly treated.

That honesty is not only ethical, it is protective. A practice found to be steering entitled patients into private care, even inadvertently through a rushed phone answer, has a real problem, and the risk is highest precisely when the line is busy and the person answering is under pressure to just book something. Because the agent reads the practice's actual NHS capacity from Dentally rather than guessing, it gives the same fair answer on the busiest Monday as on the quietest afternoon, which is the version of consistency a practice most wants on this particular question.

How a Dentally booking is made, over GraphQL

Underneath, one connection carries both books. 2care connects to Dentally through its GraphQL API, authorised with a scoped credential set during onboarding, with nothing installed at the practice. Availability is read live for the relevant list and provider, so an offered slot genuinely exists, and the appointment is written against the resolved patient onto the correct book, validated by Dentally's own rules, so a slot taken during a call fails cleanly rather than being assumed free.

Speed is what makes reading the right book invisible to the caller. A reply lands in about 480 milliseconds, ninety-fifth percentile under 700, on a voice pipeline we build and run ourselves rather than a chain of outside services, so working out NHS or private and reading live availability happens inside a conversational beat. Reliability holds at 99.9 per cent, the line answers well over a thousand calls at the same time, and every booking write is idempotent, so a stutter on the network never doubles an appointment or lands one on both books at once. Endpointing holds for a complete thought, so a patient explaining their situation is not clipped before the agent knows which list they belong on.

NHS recall, private fees, and keeping them apart

Most of the recurring work on a UK dental line is recall, and recall differs by book. An NHS patient due for a check-up is called and booked at the interval the practice has set for them; a private patient is offered their appointment with the fee stated up front. 2care works both recall lists from Dentally, so patients due on either book are called and rebooked before they drift, and the outcome is written back to the right list, with nothing sitting on a spreadsheet to reconcile against the diary.

Private fees are handled the way a good receptionist handles them: stated clearly on the call, from what the practice has set, so a private patient books knowing the cost rather than being surprised at reception. Where a treatment's fee genuinely depends on an examination first, the agent says so and books the assessment, rather than inventing a number it cannot stand behind. Being clear about money on the private book, and clear about entitlement on the NHS book, are the two halves of keeping a UK dental phone honest.

The emergency, and the evening enquiry

Dentistry has real emergencies, and they keep no office hours. A tooth knocked clean out, a socket that will not stop bleeding after an extraction, a swelling pushing toward an eye: whichever book the patient is on, these leave the booking flow immediately and put a person on the line within seconds, the caller's own words carried across. The agent forms no view on how serious it is; it recognises that the description belongs with a human and routes it, holding the recognition-not-assessment line the platform is built on, configured in triage and routing.

The ordinary evening enquiry matters too, because a UK dental practice loses as many patients to a full answering machine as to anything else. Every call is answered on the first ring in about 2 seconds, at any hour, so the enquiry that used to hit voicemail at seven in the evening is answered and booked onto the right list, and the morning starts with appointments made rather than messages to return.

The record, and where UK data lives

Before anything is written, the caller is matched to their existing Dentally record and confirmed on a date of birth, so a returning patient keeps one file; a genuinely ambiguous match is passed to a person rather than guessed, using patient matching. Intake is captured in the same breath and written to Dentally as structured fields, and the same capture feeds patient intake whether the patient rang, messaged or used a form.

For a UK practice, where the data lives is not an afterthought. A booking that builds a transcript, matches a patient and writes to Dentally is processing personal data, which makes the vendor a data processor under UK GDPR, and a business associate under HHS guidance for any US work. So the data is held in region, a data processing agreement sits alongside the arrangement, everything is encrypted in transit and at rest, no model behind the conversation trains on it, and every write is reversible. The compliance page sets out which framework applies where.

What 2care changes for a Dentally practice

A Dentally practice is not short of a system that can run two books; it is short of a phone that keeps them straight while answering every call. 2care answers each one, works out NHS or private, books to the right list at the right rules, runs recall on both books, deals with the emergency without overstepping, and records each outcome back into Dentally, all through a single voice pipeline we own end to end rather than a relay of tools passing a caller between them.

What a practice feels is not a faster booking on the calls the desk already took. It is the two books staying properly separate without a receptionist holding the distinction in her head all day, the evening enquiries onto the right list rather than a full mailbox, and the recall on both books worked to the end. Keeping NHS and private honest and separate is the particular thing a UK dental phone has to get right, and it is the thing 2care is built to hold.

There is a staffing dividend in it too. Holding the NHS-versus-private distinction in mind all day, across every call, while also quoting fees and working two recall lists, is genuinely tiring work, and it is the part of a dental receptionist's job most prone to slip when the practice is short-staffed or the phone is relentless. Taking that constant sorting off a person does not just prevent errors; it gives the front desk back the attention to look after the patients actually in the building.

Where this is right for Dentally, and getting live

This is right for a UK practice that runs both NHS and private books, keeps its lists, recall intervals and private fees current in Dentally, and keeps a dentist on call for the emergencies. With those in place, the value shows from the first day the line is live, and the clearest sign of it is a private fee never quoted to an NHS patient again, and an NHS slot never given away to someone who should have been on the waiting list.

Getting there is three moves over weeks. The connection is authorised to read availability on both books and to write appointments through the Dentally GraphQL API. The practice's setup is mapped: the NHS and private lists, providers, recall intervals, private fees, and the emergency route. Then the line is tested against a sandbox with the front desk listening before it is switched across, and the NHS-versus-private handling is tuned over the first days against real calls, each change backed by the trigger every escalation records.

Frequently asked questions

How does it know whether a caller is NHS or private?

From the practice's own Dentally records and rules, not a guess. A returning patient is resolved to their existing file, which already says which book they are on; a new patient is told plainly whether the practice has NHS capacity, and put on the list with room rather than steered to the more profitable one.

Does it quote private fees on the call?

Yes, from the fees the practice has set in Dentally, so the quote is consistent and correct. Where a fee truly depends on an examination first, it books the assessment and says so, rather than inventing a figure it cannot stand behind.

Will it book an NHS patient into a private slot by mistake?

No. The two books are kept separate, and a patient is booked onto the list they belong to. Being straight about NHS availability, including telling a patient when the NHS list is full and what their options are, is built into how it handles the call.

How is our data handled as a UK practice?

Your patients' data stays within the region, governed by a data processing agreement, encrypted on the wire and in storage, and never fed to a model as training data. A returning patient lands on a single Dentally record, and a doubtful match is passed to a person instead of becoming a duplicate.

What happens to after-hours calls?

They are answered every hour, at any volume, with no busy signal, and booked onto the right list. An evening enquiry that used to reach voicemail is answered and booked, and anything urgent follows the practice's out-of-hours escalation.

Hear it keep the two books straight

The call worth judging on a Dentally line is the one where the caller does not know whether they are NHS or private: sorted honestly to the right book, told plainly where they stand, and booked, without a private fee quoted to an NHS patient or an NHS slot given away by mistake.

See how the same connection runs on other systems across integrations, or hear an NHS and a private call handled on a live line when you book a demo.