A dental booking flow that separates emergency, hygiene and elective before anyone picks up the phone

A cracked tooth at seven in the morning, a six-month hygiene recall, and a Sunday-evening enquiry about whitening are three different businesses sharing one form. They have different urgency, different slot types, different staff, and completely different tolerance for a callback tomorrow. The default website sends all three into the same inbox in the order they arrive, and the front desk performs the sorting by hand every morning, from memory, under time pressure.

The cracked tooth and the whitening enquiry arrived through the same form, into the same queue, and were opened in the order they happened to land.

1. 01

   Appointment type is the only routing key that matters, and it is the field practices leave out

   Forms ask for name, email, phone and a free-text message. The free-text box is where the appointment type is hiding, unstructured, waiting for a person to read it. Asking the question directly costs one field and removes the entire manual sorting step.

2. 02

   The site and the practice management system speak different vocabularies

   Websites say 'emergency', 'check-up' and 'cosmetic consultation'. Practice management systems carry their own appointment type codes, set up years ago, that nobody wants to change. The build needs an explicit mapping table between the two, owned by the practice, or the routing degrades the first time someone adds a type.

3. 03

   An emergency route belongs above the form, not inside it

   Someone in pain is not going to fill in a five-field form and wait. The phone number and the same-day path sit above the form, and the form is what the other two audiences use.

4. 04

   The source tag has to survive the handoff or the whole build is decorative

   If the campaign source is lost when the enquiry crosses into the practice management system, the practice can route perfectly and still not know which channel produced which chair. The tag travels with the record.

Dental is one of the few categories where **Meta costs more per lead ($76.71) than Google search ($72.97)** (WordStream/LocaliQ 2026), and **61% of practices cite cost of care as the top reason patients delay treatment** (Sunbit *2026 State of Dental*) — so routing the right enquiry to the right path, fast, is worth more than buying more of them.

Three routes, one page. The emergency path is a phone number and a same-day slot type, placed above the form. The recall path books directly into hygiene availability. The elective path books a consultation slot with a longer duration and a different confirmation. A mapping table, owned by the practice and version-controlled, translates each site-side type into the practice management system's own appointment code, and the acquisition source tag is written into the record at creation so it survives into the schedule. No clinical detail is collected anywhere in the marketing layer: the form asks what kind of appointment, never what is wrong.

1. 1

   Week 1

   Appointment type inventory

   Every practice management system code listed, with duration and owner

   Owner: OmniFlow + practice

2. 2

   Week 1–2

   Mapping table

   Site-side types mapped to practice codes, signed off by the person who runs the schedule

   Owner: Practice

3. 3

   Weeks 2–4

   Route build

   Three routes live, emergency path above the form, source tag written at creation

   Owner: OmniFlow

4. 4

   Week 4

   Front-desk handover

   Script matched to each route, so the phone and the page give the same answer

   Owner: OmniFlow + practice

This entry makes no performance claim. It documents a booking architecture and the mapping discipline that keeps it working after launch. The artefact that matters most is the least interesting one: a maintained table connecting what the website calls an appointment to what the practice's own software calls it. That table is the part that decays first, because appointment types get added to the practice system by whoever is running the schedule that month and nobody thinks of the website. It has a named owner and a review date for exactly that reason.

These are the surfaces this engagement is run and measured from, shown with representative figures built around the benchmarks cited on this page. Every account we run reports into views like these, and you keep ownership of all of them.

We built the first mapping table outward from the website's vocabulary and then asked the practice to fit its codes to ours. That is backwards. The practice management system is the thing that cannot be changed, so the table has to be built inward from its codes, and the site's language bends to fit. Rebuilding it that way cost a week we did not need to spend.

Real client work that shipped. No performance figures are published, because none have been verified and approved for release. See all our work