Dental group software: a group is not one big practice
- Per-branch booking URLs
- One roll-up view
recorded at 09:40
What's shared, and what isn't
You decide the line — per branch, not once for everyone.
| Head office | The branch | |
|---|---|---|
| The treatment menu and prices | Sets it | Uses it |
| Booking rules (slot step, notice, booking window) | Sets the default | May override, if granted |
| Its own diary and clinicians | Sees it | Owns it |
| Its own booking page | Sees it | Owns it |
| Payment account | Sets it | Inherits, unless granted |
| The roll-up across every branch | Yes | No |
Each branch gets its own booking URL — so patients book the practice they actually attend.
Not a central switchboard. Not a location dropdown they'll get wrong. The branch's own page, on the branch's own address.
Growing into it, not re-platforming into it
- The point: One surgery today. Thirty later. Same software.
Most practices don't set out to become a group — they become one. If your software only understands a single site, that growth means a migration project at exactly the moment you have no time for one. DentiPoint treats the second branch as a setting, not a rebuild.
- Add a branch as a setting
It arrives with its own diary, team and booking page.
- Decide what it may change
Per branch, per setting. Tighten or loosen as you learn to trust it.
- Ungranted means inherited
A setting a branch hasn't been granted follows head office. Nothing drifts by accident.
- One view of the group
Every branch's numbers in one place, without logging in six times.
How dental group software keeps a group running
A dental group is not one large practice; it is several practices that need to feel like one business without losing their local identity. The software has to hold both truths at once, and that is exactly what DentiPoint is built around. Every branch keeps its own booking page, diary and team, while head office gets a single view over the whole group.
Local where it should be, shared where it counts
Each practice gets its own online booking page on its own URL, its own clinicians and opening hours, and its own diary that books by treatment. Patients booking at your Riverside branch never see Northgate's availability. But the patient record is shared where a practice chooses to share it, so a patient seen at two sites is one person with one history, not two half-records to reconcile.
Head office keeps control without micromanaging
Head office sees the whole group in one place and decides what each branch may change for itself versus inherit from the centre. Grant a branch its own booking rules, such as notice, slot step and how far ahead patients can book, its own payment account or its waiting-list settings; the treatment menu and prices stay central. Anything a branch has not been granted follows head office, so local flexibility can never quietly undo a group decision. When you add a practice, it is a setting, not a re-platforming project.
Reporting that rolls up the group
Because every branch runs on the same system, head office can compare completed appointments, no-shows, the value of treatment delivered and payments collected across sites from one report, instead of stitching together exports. If you are planning to grow, our guide on scaling a dental group across multiple branches covers the operational side, and the multi-location software page goes deeper on the group model. Pricing is per practice and transparent, so the cost scales with the group in a way you can predict on the pricing page.
More on running a dental group
- Multi-Location Dental Practice Software: What to Check
What to check in multi-location dental practice software: a book per site, per-location roles, consistent records and recalls, and group-wide reporting.
- Scaling a Dental Group Practice: Multi-Branch Guide
Scaling a dental group practice? The systems, standardised protocols and centralised reporting you need in place before opening your second branch.
11
Dental group software FAQs
Can each branch have its own booking page?
Is there one patient record across branches?
How does head office keep control?
Does the price scale with the group?
More on running a dental group
- What Is a DSO? Dental Service Organizations Explained
What a DSO (dental service organization) is, what a DSO dentist does, the main models, how common DSOs are in the US and what software a multi-practice group needs.
- Scaling a Dental Group: From One Practice to Multi-Branch
The infrastructure a UK practice owner needs before opening branch two: centralised scheduling, standardised protocols, consolidated reporting, and the compliance changes that come with a second location.
- Hiring a Dental Associate: Contract & Onboarding Guide (UK)
A practical UK guide to hiring a dental associate: self-employed status, pay splits, UDA targets, lab fees, restrictive covenants, and how to onboard a new associate into your practice and its systems.
Grow the group, not the admin
Tell us how many sites you run and we'll show you how it maps.
