Smart Booking & Nurture System for a Physiotherapy Clinic
Here is a real, live system I built and tested end to end for Gul's Rehab, a physiotherapy and aesthetic clinic, not a mockup. Every routing branch below was verified with live form submissions, confirmed in GoHighLevel's own Execution Logs, Contacts and Opportunities views.
routing branches, each tested live end-to-end
fully separated pipelines (Physio + Aesthetic)
gender- and service-aware calendars
manual data-entry steps for the patient
The business
Gul's Rehab runs two doctors on a fixed booking rotation: Dr. Ghulam Shabeer and Dr. Areeba, both seeing physiotherapy and aesthetic patients. The clinic owner, Dr. Sameera Gul, sees patients only occasionally and is intentionally excluded from the automated rotation. The core rule driving everything below: a male patient is routed straight to the male doctor; a female patient gets a choice of either.
System 1
Smart booking routing
The problem: clinics lose leads to slow phone-based booking and to friction from re-entering the same details twice.
One form, live conditional logic
A single lead-capture form collects name, gender, phone, email, doctor preference and service interest. The Doctor Preference field hides itself automatically when the patient is male, since the rule is simple: male patients go to the male doctor, female patients get a choice.
Instant redirect to the right calendar
Six redirect rules cover every combination of service, gender and doctor preference. On submit, the form evaluates which one applies and sends the browser straight to that doctor's live calendar, pre-filled with the patient's name so they never retype it.
Background CRM update, invisible to the patient
A parallel workflow fires on the same submission: it assigns the contact to the correct doctor and creates an Opportunity in the correct pipeline (Physiotherapy or Aesthetic) at the New Lead stage, all before the patient has finished booking.
Two pipelines, six stages each
Physiotherapy and Aesthetic run as separate pipelines: New Lead to Contacted to Assessment Booked to Treatment Active to Completed to No-Show/Lost, each stage weighted for forecasting.
System 2
Branching nurture sequence
The problem: generic nurture sequences keep emailing people who already converted, which looks unprofessional and risks spam complaints.
Welcome email
Sent immediately on form submission, service-agnostic.
Branch by service, 2 days later
The sequence splits by Physiotherapy vs. Aesthetic interest so the next email is topically relevant, not generic.
Educational email, per branch
Service-specific content framed for what that patient actually asked about.
Booking-aware final reminder, 3 days later
Before the last reminder sends, the workflow checks an appointment-booked tag applied the moment a patient books through any of the 4 calendars. Already booked: the sequence ends silently. Not booked: the final reminder goes out.
Tested live: a contact who booked before the wait period elapsed correctly took the booked branch and received no further reminder, confirmed in Execution Logs. A dedicated sending subdomain was configured with SPF/DKIM/DMARC for deliverability, rather than using GoHighLevel's shared sending domain.
System 3
Webinar automation funnel
The problem: running a webinar manually (reminders, SMS, replay) doesn't scale and is easy to forget.
- Branded registration page with form, consent and bot protection
- Confirmation email sent immediately with the Zoom link
- Reminder email 3 days before the event, scheduled against the actual event date
- Reminder email 1 day before the event
- SMS reminder 2 hours before (built, pending a GHL number purchase to go live)
- SMS reminder 15 minutes before (same status)
- Replay follow-up email after the event, with a recording-link placeholder
- Late registrants handled gracefully: past-due reminder steps skip instead of erroring
System 4
Reporting dashboard
A customized GoHighLevel dashboard shows, per pipeline: opportunity status, value and conversion rate, funnel and stage-distribution views, and email open/click counts tied to the nurture and webinar sequences. Irrelevant default widgets (unused ad-platform connections, an email-health widget needing 500+ sends/month, an e-commerce "sales efficiency" widget) were removed to keep it client-presentable.
See it in action
Real screenshots from the live system.
Booking form with conditional doctor-preference logic
The clinic's 4 gender- and service-aware doctor calendars
The Aesthetic pipeline, live opportunities created from real bookings
Published automations: doctor routing, nurture, appointment tags, webinar reminders
Webinar registration & reminder funnel
Custom reporting dashboard
Webinar SMS reminder, built and firing on schedule, pending a purchased SMS number
Webinar funnel management inside GoHighLevel
The clinic's live forms: new patient booking and webinar registration
Built to fail safely
The clinic's existing Next.js site already used plain WhatsApp links for its booking calls-to-action, no embedded scripts or iframes. The GHL integration followed the same pattern instead of introducing tighter coupling: a single config constant holds the GHL form URL, "Book Consultation" buttons link out to it directly, and no GHL JavaScript widget is embedded anywhere on the site. If GHL is ever down, replaced or misconfigured, only the booking link breaks, the rest of the site, hosted independently on its own VPS, is unaffected. Two pages that used WhatsApp's message-prefill feature were deliberately left on WhatsApp rather than migrated, since that specific UX wasn't replaceable by the current GHL form.
The clinic's own site: a plain link, not an embedded widget
Ready to build your growth engine?
Tell us about your business and goals. We'll reply with honest, practical next steps — no pressure, no fluff.