Reference architecture
From Ad Click to Chair: A Lead-to-Booking Engine for High-Ticket Clinics
Nature: reference architecture, fully specified and designed by Pelotis (honest label: this is a system design, not a deployed client — every number below is a design target, not a measured result) · Stack: HubSpot, Make, WhatsApp Business API, Looker Studio
The scenario
A premium dental clinic in Madrid. Average treatment ticket: €3,000. Marketing generates leads from ads, web forms, and WhatsApp — and then the leads die. Not because the clinic is bad at dentistry, but because a receptionist between patients cannot answer a form submission in under a minute, chase a silent lead three times in 48 hours, confirm tomorrow’s appointments, and resurrect last month’s no-shows. At €3,000 a patient, every leaked lead is real money; the leak is structural, and so is the fix.
The system
An 8-stage pipeline where every stage has explicit entry and exit criteria — because a pipeline without criteria is a list with opinions:
| # | Stage | Enters when | Exits when |
|---|---|---|---|
| 1 | New lead | Form / WhatsApp / ad received | Answered in < 1 min |
| 2 | Contacted | First touch made | Shows booking intent |
| 3 | Qualified | Lead score ≥ 70 | Agrees to book |
| 4 | Appointment booked | Calendar slot confirmed | Attends |
| 5 | Appointment held | Patient showed up | Quote sent |
| 6 | Quote sent | Offer presented | Patient decides |
| 7 | Closed won | Accepted / treatment started | — |
| 8 | Closed lost | No response / declined / no-show ×2 | — |
Eleven mapped automation events drive the record through those stages. The load-bearing ones:
- Sub-minute first response. Lead arrives → contact auto-created in HubSpot → automated reply (WhatsApp or email) in under 60 seconds. Speed-to-lead is the single highest-leverage variable in local high-ticket services.
- Scoring gate at 70. Leads above threshold go straight to the booking sequence; the rest enter automated nurture instead of being ignored.
- 3 touches in 48 hours for silent leads — email + WhatsApp + a task for a human, in that order. Persistence is systematic; annoyance is capped.
- Confirmation + 24h reminder on every booking, attacking the no-show rate where it lives.
- No-show reactivation (two structured attempts) and a lost-lead reactivation loop — the cheapest leads a clinic will ever get are the ones it already paid for.
- Post-treatment satisfaction survey, closing the loop and feeding reviews.
A Looker Studio dashboard reports conversion by stage, appointments, and closings — so the owner argues with numbers, not anecdotes.
Design principles
- The first minute is worth more than the next week. Everything is architected around instant response.
- Humans handle judgment, machines handle memory. Staff never has to remember a follow-up again; they only handle conversations.
- WhatsApp-first, because that’s where Spanish patients answer. Email supports; it doesn’t lead.
- Consent and lawful basis are built into intake, not bolted on — GDPR-clean by architecture.
What this template is for
This architecture transfers to any local, high-ticket, appointment-driven business — aesthetic medicine, legal, veterinary, physiotherapy. The tools can swap (Attio instead of HubSpot, n8n instead of Make); the logic — instant response, scored routing, capped persistence, reactivation, measurement — is the product.
Pelotis builds and runs GDPR-clean revenue systems — Attio Certified Expert Partner, Braze certified, ex-Amazon/Audible MarTech. Want this engine pointed at your funnel? First conversation is free and specific.