Building a funnel with Heyflow

How to Build a Multi-Location Booking Funnel for DSOs

16 min read
Learn how to build a multi-location booking funnel for DSOs using conditional logic, insurance qualifiers, and partial submit capture to route leads and boost bookings.
Get started Pricing
G2 ratings 4.4 / 5.G2 ratings 4.4 / 5.OMR ratings 4.5 / 5.OMR ratings 4.5 / 5.Capterra ratings 4.7 / 5.Capterra ratings 4.7 / 5.

Trusted by 3,000+ marketers

AxaBCG Digital VenturesForbesSaas GroupRocket MortgageAllianzCiscoPernod Ricard

A patient clicks a Meta ad for dental implants, lands on a generic contact form, and waits half a day for a callback from the wrong office. Multiply that across 30 or 100 locations and a DSO's ad spend is quietly funding competitors instead of booked chairs. Building a multi-location booking funnel fixes the routing, qualification, and follow-up gaps that a static form was never designed to handle.

Key takeaways

  • One conditional-logic funnel can serve an entire DSO network, routing patients by ZIP code without separate builds per office.

  • Asking about insurance mid-funnel, before contact info, prevents wasted appointment slots and improves booking rates.

  • Capturing partial submissions from abandoned sessions turns unfinished forms into retargetable leads instead of lost revenue.

  • Heyflow provides the branching logic, HIPAA-ready compliance tools, and CRM routing needed to template this funnel across every location.

Why DSOs Need a Dedicated Booking Funnel

A static contact form on a dental website does one thing: it collects a name and phone number and hopes someone calls back. For a single-location practice, that may be enough. For a DSO operating across 10, 30, or 100+ offices, it is a revenue leak. A prospective implant patient who clicks a Meta ad, lands on a generic form, and waits 8 hours for a callback has already booked elsewhere. Research cited by Group Dentistry Now found exactly this at a 40-location dental group spending over $1 million annually on Google PPC — form fills sat unanswered for hours while patients moved on.

A multi-location booking funnel solves three problems simultaneously: it qualifies the patient by service need, insurance status, and location before they ever speak to a front desk team; it routes the lead to the correct office automatically; and it captures data from every session — including the ones that don't complete. When dental CPCs range from $5 to $50+ and implant CPLs run to $107 or higher, recovering even a fraction of abandoned sessions changes the economics materially.

The business case is straightforward. A static contact form converting at 5% on $10,000 in monthly ad spend produces 200 leads at $50 CPL. A multi-step qualification funnel converting at 10% on the same spend produces 400 leads at $25 CPL — or the same 200 leads at half the cost. Beyond CPL, lead quality changes the downstream math: pre-qualified leads with matched insurance and confirmed location convert to booked appointments at roughly double the rate of unqualified form fills, because the front desk is calling someone who already knows which office they're going to and has already confirmed their insurance is accepted.

The 7-Screen Funnel Architecture

The sequence below balances qualification depth with completion rate. Five to seven screens is the practical range for this funnel type — fewer than five doesn't capture enough data for multi-location routing; more than seven risks drop-off before contact information is collected.

Screen 1: Service Selection

Open with visual tile selectors, not a text field. Six tiles covering General Dentistry / Cleaning, Cosmetic Dentistry, Dental Implants, Orthodontics / Invisalign, Emergency Care, and Pediatric Dentistry. This screen sets the tone: it signals a personalized experience rather than a generic form. The service selected here drives every downstream branch and becomes the primary CRM tag for lead scoring and ad attribution. In Heyflow, image choice blocks handle this natively — no custom code required.

Emergency Care is the critical branch point. A patient in pain will not complete a 7-step funnel. Selecting Emergency triggers an immediate fast-track: ZIP code input, nearest location with phone number, click-to-call. Three screens maximum. Every second of additional friction here is a patient lost.

Screen 2: Service-Specific Qualifier

This screen branches based on Screen 1. Implant inquiries see: "How many teeth need replacement?" (Single / Multiple / Full arch / Not sure). Orthodontic inquiries see: "What's your primary concern?" (Crooked teeth / Spacing / Bite issues / Refinement). General dentistry sees: "When was your last dental visit?" This deepens engagement and captures clinical qualification data before any personal information is requested. It also enables the confirmation screen to display service-relevant content — a cost estimate range for implants, a financing message for full-arch cases.

Screen 3: Insurance Status

Insurance is the most important qualifier in the DSO context and the most commonly omitted. A patient who arrives at a location only to find their plan isn't accepted wastes an appointment slot, risks a negative review, and demoralizes the front desk team. Ask it mid-funnel — after engagement is established but before personal data is requested.

The question: "Do you have dental insurance?" with three paths: Yes (dropdown of major carriers), No, Not sure. The "No insurance" branch is where most funnels drop the ball. Instead of continuing to the location screen, show a brief reassurance: "No insurance? No problem. We offer flexible financing and our membership plan saves you 20–40% on all services." This addresses the objection before it becomes a drop-off reason. Conditional logic in Heyflow handles this branch without additional screens — it surfaces the message inline and continues the flow.

Screen 4: Location Matching

This is the core differentiator of the multi-location funnel. Ask for ZIP code, then display the 2–3 nearest locations with address, distance, and hours. The patient selects their preferred office. This single interaction replaces the need for separate funnels per location: one flow, one build, unlimited locations served through conditional routing.

The selected location determines which office receives the lead notification, which scheduling calendar or CRM queue the submission routes to, and which local phone number appears in follow-up communications. If no location is within a reasonable radius, offer a waitlist or virtual consultation — never a dead end.

Screen 5: Preferred Timing

A single question: "When would you like to come in?" with options — As soon as possible / This week / Next week / Flexible / Just exploring. This captures the urgency signal for lead scoring. "As soon as possible" submissions should trigger immediate speed-to-lead notifications; "Just exploring" leads can enter a longer nurture sequence. The data takes seconds to collect and significantly improves follow-up prioritization.

Screen 6: Contact Information

Name, phone, and email — placed here, not at the start. A user who has answered five questions has invested effort and received value (service matching, insurance handling, location matching). They are far more likely to complete this screen than they would have been on screen one. Include trust signals: a HIPAA compliance badge, the location's Google rating, and a specific commitment ("We'll call you within 2 hours to confirm your appointment").

Enable phone network validation on every submission — it eliminates fake numbers and ensures every lead is reachable. For high-value service lines where CPL exceeds $100 (implants, full-arch, cosmetic), add SMS OTP verification. The marginal friction is worth it: a verified implant lead at $107 CPL that converts to a $5,000+ case is a fundamentally different ROI equation than an unverified form fill.

Screen 7: Confirmation and Next Steps

The confirmation screen has a captive, high-intent audience — use it. Display the selected location's details, a specific next-step commitment, and a click-to-call button. For implant and cosmetic inquiries, add a cost estimate range generated by Heyflow's Calculations feature based on service selection from Screen 2. Link to patient intake forms — completing them before the visit saves chair time and signals commitment. Add a Google review snippet or patient count for social proof. A "Refer a friend" CTA here costs nothing and occasionally generates additional leads from a single submission.

Conditional Logic: One Funnel, Every Location

The most common misconception in DSO marketing is that multi-location funnels require separate builds per location. They don't. Conditional logic handles the branching; one funnel serves the entire network. There are five branching points in this architecture:

Branch 1 (Screen 1 → Screen 2): Service selection determines which qualifier questions appear. An implant inquiry and an orthodontic inquiry see completely different Screen 2 content.

Branch 2 (Screen 1, Emergency): Emergency selection bypasses screens 2–5 entirely and fast-tracks to ZIP code, nearest location, and click-to-call.

Branch 3 (Screen 3, No Insurance): Displays membership plan and financing messaging inline before continuing to location matching.

Branch 4 (Screen 4, Location): ZIP code determines which offices are displayed. Selected office determines lead routing destination, notification recipient, and scheduling calendar shown.

Branch 5 (Screen 7, Confirmation): Content varies by service and location. Implant leads see financing information and cost estimate. General dentistry leads see a new patient special. Each location's specific offer can be surfaced dynamically.

Heyflow's decision tree view renders all of this as a visual map rather than nested logic rules — essential when managing 5+ service categories across 25+ locations. When a new office is acquired, duplicate the template, update location-specific details, and the branch is live.

Recovering Revenue from Abandoned Sessions

With partial submit capture enabled, a user who selects "Dental Implants," enters their ZIP code, and then closes the funnel doesn't disappear. Their partial record — service interest, location signal, and timestamp — is captured and forwarded to your CRM. That data enables two things: location-specific retargeting (serve them an implant ad for the Dallas office they were looking at) and demand intelligence (if 200 users in a ZIP code start the implant branch but don't complete, that location has a demand signal worth acting on).

The math on recovery is meaningful. If 1,000 users start the funnel monthly and 400 abandon, capturing those partial records and recovering 5% through retargeting or follow-up generates 20 additional leads. At a $2,400 average patient lifetime value, those 20 recovered patients represent $48,000 in lifetime revenue from data that a static form would have discarded entirely.

HIPAA, TCPA, and Compliance

Any funnel collecting dental concerns, insurance information, or health-related questions falls under HIPAA. The threshold is lower than most DSO marketers assume: if your practice submits electronic claims or processes digital payments, you are a covered entity, and your marketing infrastructure must comply. In 2022, small medical and dental practices accounted for 55% of OCR fines — the assumption that small practices fly under the radar is demonstrably wrong.

The practical requirements for this funnel build are three:

BAA with your funnel builder. Any vendor that handles PHI on your behalf requires a signed Business Associate Agreement. Heyflow provides a BAA on all plans and holds SOC 2 Type II and ISO 27001 certifications. Confirm this before collecting any patient data.

PII auto-deletion. Heyflow's Sensitive Tag feature auto-deletes specified fields (name, phone, email) from Heyflow's servers after forwarding to your CRM. The data is in your system; it's not sitting on a third-party server indefinitely. This is a meaningful additional layer of protection for healthcare use cases.

TCPA consent capture. If the funnel triggers SMS or phone follow-up — and it should, for speed-to-lead — you need documented prior express written consent. Heyflow's native integrations with TrustedForm and Jornaya capture independent consent verification at the moment of submission, providing defensible proof if a TCPA complaint arises.

One element that does not belong in this funnel: detailed health history. Medical history intake belongs in a post-booking patient intake form, not the acquisition funnel. Including it here adds HIPAA exposure, destroys completion rates, and collects information the front desk will re-collect anyway.

Integrations: Connecting the Funnel to Your Tech Stack

The funnel is the front end. Its value depends entirely on what happens downstream. Three integration layers matter for DSOs:

CRM and PMS routing. Lead submissions should route to the selected location's CRM queue immediately via webhook or native integration. Heyflow connects natively to HubSpot, Salesforce, and 50+ other tools, and supports webhooks for custom PMS integrations. The lead record should arrive tagged with: service type, insurance carrier (or "none"), selected location, urgency level, and validated phone number. A front desk team receiving this record can prioritize and personalize their first call.

Speed-to-lead notifications. The single fastest way to lower patient acquisition cost is faster follow-up. Social leads in particular have a short interest window and require same-day contact for acceptable conversion rates. Configure instant SMS or email notifications to the assigned location the moment a lead submits. Heyflow supports native WhatsApp and SMTP integration for this. Every minute of delay between submission and first contact reduces booking probability.

Ad platform optimization. Sending conversion data back to Google, Meta, and TikTok is what enables campaign optimization. Heyflow sends data server-side to Meta (CAPI), TikTok, and Bing — bypassing iOS tracking restrictions and cookie deprecation — and integrates client-side with Google Ads and LinkedIn. For a DSO spending $50,000+ monthly across platforms, accurate conversion signals are the difference between campaigns that optimize toward booked patients and campaigns that optimize toward clicks.

Measuring and Optimizing Performance

Aggregate funnel metrics hide the performance variation that matters most in a DSO context. A funnel converting at 12% network-wide may be converting at 20% in one market and 4% in another. Per-screen drop-off analytics at the location level reveal these differences and point to specific fixes.

If Screen 3 (insurance) shows a 40% drop-off at one location, the team knows to add reassurance messaging or test a different question framing at that branch. If Screen 4 (location matching) shows high abandonment in a specific ZIP code, it may indicate the nearest office is too far — a signal for expansion planning or a virtual consultation offer. Heyflow's per-screen analytics surface exactly this data.

A/B testing should run at the screen level, not just the landing page. Test different opening questions (service tiles vs. a single "What brings you in?" open question), different insurance question framing, different offers on the confirmation screen (free exam vs. $99 new patient special). Run tests at the location level when traffic volume supports it — what converts in a dense urban market may not convert in a suburban one. Statistical significance matters; don't call a winner on 50 submissions.

The metrics hierarchy for DSO funnel performance: start with cost per booked patient (not CPL), then work backward to show rate, booking rate, and funnel conversion rate. CPL is a useful efficiency metric, but a low CPL with a poor booking rate produces a cost per patient that makes the channel unprofitable. The funnel's job is not to generate leads — it's to generate booked, attended appointments.

Scaling to New Locations

When a DSO acquires a new practice or opens a de novo, the funnel should be live within days, not weeks. With a template-based approach, the marketing team duplicates the proven funnel, updates location-specific details (address, hours, accepted insurance carriers, scheduling calendar link), and deploys. The conditional logic, question sequence, compliance configuration, and ad platform integrations carry over automatically.

Brand consistency across locations is maintained through Heyflow's 2,000+ style variables — every location-specific variant matches the corporate brand without rebuilding from scratch. For PE-backed DSOs demonstrating marketing infrastructure during due diligence, a documented, templatized funnel system is a meaningful asset: it shows that patient acquisition scales with location count, not headcount.

If you're ready to build, start your free Heyflow trial and use the multi-step flow builder to wire the 7-screen architecture described above. The conditional logic, partial submit capture, phone validation, and HIPAA compliance infrastructure are available out of the box.

Frequently Asked Questions

Do we need a separate funnel for each location, or can one funnel serve the whole DSO?

One funnel can serve the entire network through conditional logic and ZIP-code-based location routing. The patient's ZIP code input triggers a display of the nearest offices; their selection determines which location receives the lead, which scheduling calendar is shown, and which office is notified. There is no need to build or maintain separate funnels per location — duplicating a template for a new acquisition takes minutes.

At what point in the funnel should we ask for insurance information?

Mid-funnel, after the service selection and service-specific qualifier screens — typically Screen 3 of 7. Placing it earlier increases drop-off because the user hasn't yet invested enough effort to justify answering a sensitive question. Placing it after the contact screen means uninsured patients may book appointments at locations that don't offer their coverage, wasting both the patient's time and the office's schedule slot.

What happens to users who start the funnel but don't finish?

With partial submit capture enabled, any data entered before abandonment is captured and forwarded to your CRM. A user who selects "Dental Implants" and enters their ZIP code but doesn't complete the form still provides a retargetable lead with service interest and location signal. Given dental CPCs of $5–$50+, partial data recovery meaningfully reduces effective CPL and enables demand intelligence at the location level.

Does collecting insurance and service information in the funnel trigger HIPAA obligations?

Yes. Any form collecting dental concerns, insurance information, or health-related questions falls under HIPAA if your practice is a covered entity — which applies to virtually every DSO that processes electronic claims or digital payments. Your funnel builder must sign a BAA, and any vendor handling that data must meet HIPAA security requirements. Detailed health history intake does not belong in the acquisition funnel; it belongs in a post-booking patient intake form.

How do we make sure the funnel feeds the right data back to Google Ads and Meta for campaign optimization?

Server-side conversion APIs are the right approach post-iOS 14.5. Heyflow sends conversion data server-side to Meta (CAPI), TikTok, and Bing, and integrates client-side with Google Ads. This means booked appointment data reaches the ad platforms reliably, enabling campaign optimization toward actual patients rather than clicks or raw form fills. Without this, your campaigns optimize on incomplete signals and CPL rises over time.

What's the right way to handle emergency dental patients in this funnel?

Emergency patients need a fast-track branch, not the full 7-screen flow. When a user selects "Emergency Care" on Screen 1, conditional logic should immediately route them to a 3-screen variant: ZIP code input, nearest location with address and phone number, click-to-call. Any additional qualification steps at this point will cause the patient to abandon and call a competitor. The fast-track is a conditional branch within the same funnel — no separate build required.

Back to top