One standard of care across every location.

What "per location" actually means

A group does not buy one receptionist and point five numbers at it. Each location is a separate practice inside Dentovox, and that is deliberate: a caller who reaches the Riverside office should be offered Riverside's providers, Riverside's hours and Riverside's operatories, and their record should never be visible from another site. Patient data is isolated per practice in the database itself, not by a filter in the application, so a query that forgets which location it belongs to returns nothing rather than someone else's patients.

What each location gets: its own phone number, its own connection to the practice management system, its own greeting, hours and answer mode, its own dashboard with its calls, bookings and no-shows, and its own 900 included minutes. What the group gets: the same behaviour everywhere, one relationship, one invoice, and a named success manager.

Rolling it out across sites

1. Start with one location, not five. Pick the site with the worst phone coverage — usually the busiest or the one with a vacancy at the desk — and run it for two weeks.
2. Fix the script once. The practice questions the AI needs — cancellation policy, new-patient instructions, parking, insurance answers — are mostly identical across the group. Settle them on the first site and reuse them.
3. Roll the rest in pairs. Each new location is a number forward and a PMS connection; the configuration is a copy of the first one with its own providers and hours.
4. Decide the answer mode per site. A location with a strong front desk may only need overflow and after-hours; a location that is short-staffed may go full-time immediately. They do not have to match.

What a group should know before signing

Two limits worth hearing now rather than after the contract. There is no combined cross-location view yet: reporting is per location, and a group roll-up is on the roadmap, not in the product. And two-way SMS — confirmations, reminders, waitlist offers — is built and included in every plan but is not sending yet; it switches on for every location at once when US carrier registration completes. Everything else on the status list is on one page, including what is live today and what is not offered at all.

Frequently asked questions about multi-location and DSO

How does Dentovox work across multiple locations?

Each location is set up as its own practice: its own number, schedule, providers, hours and answering settings, with its own dashboard. Answering behaviour can be standardised across sites by configuring them the same way, or tuned location by location. A single combined group view across locations is not available yet — today you switch between locations.

Is patient data separated between locations?

Yes. Data is isolated per practice at the database level, so one location's records cannot be read from another. Access is controlled by role and every sensitive action is audit-logged.

Can we route calls differently per site?

Yes. Each location can use a different answer mode — full-time, overflow, or after-hours only. A transfer to that location's own front desk line can be configured for its office hours; outside them, an unfinished call becomes a structured callback request for that location rather than a transfer into an empty office.

How is multi-location billed?

$649 per location per month, each with 900 included minutes and $0.39 per extra minute, plus a named success manager. Annual billing saves 10%. For larger groups, terms are agreed on the call rather than published as a discount table.

Whatever the group size, the capability-by-capability status is the one listed on the AI receptionist + patient recovery page.