A dental group has four practices. A patient asks one practice whether they take children on the membership plan and is told yes. They ask another practice in the group the same question and are told no. The patient is confused, and so is the group's operations manager when they hear about it.
Dental groups often give inconsistent answers across practices. A redesigned approach fixes most of it.
How the answers drift apart
Most dental groups grow by acquisition, and each practice arrives with its own way of doing things. One receptionist explains the plan one way, another has a printed sheet from years ago. Group-wide changes to plans or registration reach some practices weeks before others. And where fees genuinely differ between practices, nobody has written down why, so patients hear different figures without explanation.
Healthcare groups generally face this, as covered in multi-site healthcare groups and consistent patient answers.
One source for the group, one page per practice
Shared answers first. Plan terms, how registration works and payment options belong on group pages, written once, so every practice points to the same wording.
Local details on local pages. Each practice page carries its own hours, address, parking, dentists and any fee differences, labelled so patients know they are specific to that practice.
3. Make urgent care routes clear for each practice. Urgent care arrangements may differ between sites. Each practice's page should show them clearly, as covered in emergency dental enquiries and what the website should say.
Nearest practice, nearest team. A patient who mentions a town or postcode should reach the reception team at the practice that serves it.
The same promise everywhere. Pick a reply time, such as the same working day, and hold every practice to it.
A monthly look across the group. The operations lead reads a sample of enquiries from each practice to catch answers that have drifted.
Where an assistant helps
SpideyChat for dental practices answers from your website, so group-wide answers stay consistent while practice-specific details come from each practice's pages. It captures enquiries and routes them to the right practice. SpideyChat Pro supports up to 3 companies and Enterprise supports unlimited. Using one assistant across several locations is covered in AI receptionist for multiple locations.
Patient: Do you take children on the membership plan? Assistant: Yes, the group's membership plan includes a children's option, as the plans page explains. Which practice would you like to join? I'll pass your details to their reception team.
Consistency and patient value
A patient who has a confusing experience may not register at all, and the long-term value of each lost patient is significant, as shown in what a missed dental enquiry costs a practice. Across a group, those losses add up.
Clinical boundaries across the group
Every practice should follow the same rule: the website assistant never gives clinical advice. That rule should be set once for the group, not left to each practice.
Comparing practices fairly
Look at new patient enquiries, how quickly each was answered and how many became registrations, practice by practice. When one practice converts far better than the rest, find out what its reception team does differently and share it.
When fees genuinely differ
Sometimes practices in a group have different fees, perhaps because of location or the services offered. That is fine, as long as it is explained. A single line on each practice page, such as "fees at this practice are listed below and may differ from other practices in the group", prevents confusion. Patients accept differences when they are told about them. What they do not accept is being given one figure and charged another.
A single point of truth
Keep one person or team responsible for group-wide content, such as plan terms and registration steps. When something changes, they update it once and every practice benefits. Without that ownership, updates happen piecemeal and inconsistency creeps back within months.
First steps for the group
Start with the ten questions reception teams hear most, write one group answer for each, then check every practice page against them. The features page explains routing, and you can try SpideyChat at a single practice before extending it.