For UK dental practices using Dentally
Give dental reception a clear next step without duplicating Dentally recalls
Missed calls, recall enquiries and new-patient questions often arrive while the team is busy. We map one reception process, agree the human handover and check what your Dentally account permits before proposing any connection.
Discuss your reception workflowStart with a task reception can measure
Missed calls
Capture a request for a call back without asking for a clinical history. Give reception a clear owner and a list of calls still pending.
Recall planning
Review existing due dates, status, prebooked appointments and past contact before considering another reminder. Reception approves the next step; access to the recall list must first be enabled and tested.
New-patient enquiries
Collect administrative questions and prepare a response for staff. Reception confirms availability and makes any appointment in Dentally.
Use Dentally's existing recalls before adding follow-up
Dentally's developer documentation describes GET /v1/recalls and records with a due date, status, prebooked and times_contacted. We first ask reception which recalls are already booked, completed or previously contacted. A separate workflow should address an actual gap, rather than send a second message to the same patient.
Dentally API access comes after the workflow
The practice must have API access enabled. The credential's scope cannot exceed the Dentally user's permissions; we check allowed operations, minimum patient data and lawful processing with the practice before a read. Published documentation does not prove access to your practice or a working EBROTECH connector.
If access is unavailable or the task does not need it, reception can test a call-back workflow outside Dentally, with a manual check against the appointment book. Any email stays as a draft until a person reviews it and presses Send. Clinical and urgent questions go to a qualified person.
For broader administrative processes, see AI for dental practices. The right scope depends on the practice's own reception process and permissions.
A pilot your practice can review
- 1. Baseline. Count the calls or enquiries currently waiting for a response and note how reception handles them.
- 2. Boundaries. Agree the minimum data, permissions, message review, escalation and what remains in Dentally.
- 3. Review. Test one workflow, log exceptions and compare the result with the baseline before discussing expansion.
Dentally and AI: frequently asked questions
Do we have to replace Dentally?
No. Dentally remains your appointment book and clinical record. We start with a reception task such as returning missed calls or preparing a recall list.
Is there a Dentally API?
Dentally documents an API, including GET /v1/recalls and patient and appointment resources. API access must be enabled for your practice, and the key's scope cannot exceed the user's own permissions. Documentation does not mean EBROTECH has a working connector or access to your account.
Do we need another recall reminder system?
Not by default. Dentally's recall records already include a due date, status, whether an appointment is prebooked and how many times the patient has been contacted. We review the practice's existing recall workflow first, then consider a separate staff-reviewed follow-up only for an agreed gap so a patient is not contacted twice.
Are you a Dentally or Henry Schein One partner?
We do not claim an official partnership or a listing in a Dentally partner directory. If the pilot needs vendor approval, we confirm the route with the vendor and your practice.
Can AI book appointments or update patient records?
Reception confirms appointments in Dentally. Any write-back would be a separate, authorised and tested part of the scope. AI does not triage, diagnose or recommend treatment.
How do you handle patient data?
We agree the minimum data, lawful processing arrangements, access controls and a human review step before a pilot. A clinical question or urgent concern goes to a qualified person.
How long does setup take?
We set a delivery schedule after reviewing your Dentally edition, access, reception process and the tests needed. We do not assume a working connector from public API documentation alone.
Can we start with one workflow?
Yes. A small reception workflow makes it possible to compare missed calls or pending follow-ups with your current baseline before expanding.
Tell us where reception loses the thread
We will look at your current Dentally setup, pick one administrative task and set out the access and review needed for a safe pilot. Scope, price and schedule follow that assessment.
Tell us about your practice