Dentally integration
An AI receptionist for Dentally practices in the UK.
UK dental practices running private and NHS lists side by side, where booking someone onto the wrong one is a conversation nobody wants at reception.
Writing to Dentally
Real time, on the call
Writing…
Encrypted in transit, audit-logged
Who runs Dentally
Dentally runs UK dental practices, many carrying both private and NHS lists with different availability, different fees and a different conversation on the phone.
The problem
What is actually breaking.
The things practices tell us cost them the most, in the order they raise them.
Two lists, one phone number
Which list a patient is on changes availability, fees and what you can offer them.
The fee question comes first
Most callers open with cost, and the answer depends on the list.
Emergency demand is unpredictable
Pain calls arrive without warning and cannot wait for the next routine opening.
Recall is known but not worked
Intervals differ between lists and the calls do not get made.
How it connects
Real time
Written while the patient is still on the line. Every write logged and reversible.
How 2care solves it
One platform, not a point fix.
Inbound answering, outbound outreach, write-back and escalation are the same agent - which is why the whole problem moves rather than one part of it.
The right list, every time
The agent establishes which list the patient is on and books against that list's availability and rules.
Fees answered on the call
What a visit costs under the relevant list, handled without deferring to reception.
Pain routed to held slots
Urgent presentations reach emergency capacity, and anything clinical escalates.
Recall per list
Outbound respects the different intervals each list carries.
Scope
What it touches in Dentally.
Three passes. Across several sites, the third is what keeps the boundary consistent.
- Operatory and provider
- Practitioner availability in Dentally, per site, at the moment of the call.
- Appointment type
- Appointment reasons and their durations.
- Recall status
- Recall status, so the overdue list is your own.
- Patient record
- Patient records across sites, so nobody is duplicated.
- Benefit detail
- Plan and payment details already held.
A Dentally practice, in their words
The recall list used to be the thing we felt guilty about. Now it just gets done.
Operations Lead, Providence Dental Practice- 62
- hygiene recalls booked in month one
- 2
- sites on one number
- 24/7
- emergency triage cover
The difference
What changes on the Dentally phone.
Slotting an NHS patient into private availability sparks the sort of talk no one at the desk wants.
How it runs today
With 2care on Dentally
Two lists, one phone number
The list a patient belongs to alters availability, fees and what can be offered
The agent works out which list the caller belongs to, then books to that list's own availability and rules
The fee question comes first
Nearly everyone leads with price, and the reply hinges on the list
The cost of a visit on the applicable list is given without passing it to reception
Emergency demand is unpredictable
Calls about pain come with no notice and cannot hold out for the next routine slot
Emergencies are directed to emergency capacity, and anything clinical is escalated
Recall is known but not worked
The lists carry different intervals, and those calls simply never happen
Outbound honours the separate interval each list sets
Straight answers
What Dentally practices ask before connecting it.
We run several practices on one number. Does that work?
Yes, and it is the case this handles well. The site is resolved from what the caller says before any availability is offered, so they are not booked across town.
Can it work our recall list?
Yes, from Dentally itself, at the cadence you set, with the appointment booked during the call.
Does it handle NHS and private lists differently?
It books whatever Dentally defines for each, including different appointment reasons and durations, rather than treating them as interchangeable.
We are not granting broad write access to Dentally.
Nor should you. Sites, practitioners and appointment reasons as Dentally holds them. Clinical documentation sits outside the scope entirely.
At a glance
The Dentally connection, in the terms a review will ask about.
Dentally powers UK dental practices, plenty of them running both private and NHS lists, each with its own availability, its own fees and its own kind of phone conversation.
Go live
Weeks, not quarters.
Most practices on Dentally are live inside a few weeks of authorising the connection.
Authorise the connection
Your Dentally administrator approves API access. Nothing is installed, and nothing changes about how your team uses Dentally.
Map your rules
We map your providers, locations, appointment types, booking rules and escalation paths - the things that make your schedule yours.
Test, then go live
We run your real scenarios against a test environment with your team watching, fix what surfaces, then switch the line over and monitor.
See it work
A call, a booking, and a write-back into Dentally.
Recorded end to end. The system on screen is not yours, but the flow is the one described above.
Before you connect it
Questions about Dentally.
Yes. It determines the list the patient belongs to and books to that list's availability, rules and fees.
Yes, the fee for a visit under the list that applies is quoted during the call.
People search it both ways. A Dentally answering service describes covering the phone. A Dentally integration describes what connects to what. Here they are one product: cover for the line that reads your diary and writes the booking straight into it.
Sites, practitioners and appointment reasons as Dentally holds them, confirmed while the caller is still speaking.
No. Callers are matched against what Dentally already holds before anything new is created.
Yes. Retained against the patient across whichever site they were booked into.
See 2care book into Dentally.
30 minutes, on your own call flows. No commitment.
- 18 specialties covered
- ·Live in weeks, not months
- ·HIPAA, GDPR and DPDP