Skip to content
Emmanuel NanadoumRésumé(PDF, opens in a new tab)

Cactus Chiropractic

From the first ring to a booked visit, on the practice's own brand.

Open revenue system Patient website Talk to the AI receptionist
Built for
Cactus Chiropractic, Peoria, AZ (prospect demo)
Engagement
AI patient acquisition system (sales demo)
My role
Discovery, solution mapping, workflow architecture, live demo build
Source
blair-demo-cactus.vercel.app
Cactus Chiropractic revenue system page: The Chiropractor Revenue System with a talk-to-the-AI-receptionist panel.
blair-demo-cactus.vercel.app

Status at time of writing

Stamped from the live build, not from the plan.

Status of each component
ComponentStatus
Patient websiteLive

Published demo in the practice's brand.

AI receptionistLive

Two-way voice conversation in the browser at /receptionist; the original phone demo line has been retired.

Pipeline, counts and reportingDemo data

Illustrative sample data, labeled on the page. No patient information.

1Business problem

Small practices run the phones, the front desk and follow-up with the same two or three people. The moments that break are predictable: a call rings out during an adjustment, a web form waits until tomorrow, a no-show never hears back.

The owner rarely sees where inquiries stall, because nothing connects the phone, the website, the calendar and follow-up into one record.

2Discovery

  1. 2.1Start from the practice's positioning (gentle, unhurried care) so automation reads as attentiveness, not a call center.
  2. 2.2Map every way a new patient arrives (phone, web form) and every hand-off after it.
  3. 2.3Hard constraint: the demo must never touch the practice's public line or any real patient data.

3Requirements

Requirements
R-01Answer new-patient calls in real time with a two-way AI voice agent.
R-02Turn every call and form into a tracked contact with its source.
R-03Move each opportunity through a pipeline to a booked appointment.
R-04Automatic SMS + email confirmations and two-way SMS reminders.
R-05Log show / no-show and trigger follow-up, review requests and reactivation.
R-06Report every step, with sample data clearly labeled as sample data.

4Solution architecture

One connected patient journey. A single prospect flows through every module without manual re-entry.

Patient journey in 13 steps

  1. 01Call / web inquiry
  2. 02AI or instant SMS response
  3. 03Contact created
  4. 04CRM record
  5. 05Pipeline
  6. 06Appointment
  7. 07SMS + email confirmation
  8. 08Reminders
  9. 09Show / no-show
  10. 10Follow-up
  11. 11Review request
  12. 12Reactivation
  13. 13Reporting
Figure 4.1 — Patient journey in 13 steps

5Demo / POC

The prospect talks to the AI receptionist, pretends to be a new patient, then watches the journey that conversation would start.

Cactus Chiropractic patient website hero: Gentle care. Time to listen.
Figure 5.1 — Patient-facing site in Cactus's own identity.
Cactus revenue system: One connected patient journey, a grid of 13 journey steps.
Figure 5.2 — Every step is visible, so the demo sells the whole path.
Open revenue system Patient website

6Technologies

  • AI voice agent
  • GoHighLevel CRM
  • CRM pipeline
  • Two-way SMS
  • Email automation
  • Web forms
  • Reporting

7Integration points

Integration points
FromTo
Demo phone lineAI voice agentSeparate from the public practice line
Website formCRM contact + opportunitySource recorded on creation
CalendarConfirmations + remindersSMS and email on booking
Appointment statusFollow-up, review, reactivationOutcome drives the next workflow

8Tradeoffs

Design decisions and tradeoffs
A separate demo channelInstead of: Forwarding the practice's real lineThe public line and real patients stay untouched; the owner still hears the real agent. It now runs in the browser, so no phone number is needed.
Live voice agentInstead of: A recorded sample callHarder to build, but it proves the product instead of describing it.
Labeled sample dataInstead of: Plausible-looking resultsA fabricated number would be the first thing a sharp owner questions.
One connected journeyInstead of: Separate point toolsThe value is in the hand-offs, so the demo shows the hand-offs.

9Implementation & handoff

  • Go-live scope if the practice moves forward: decide on number forwarding, connect the calendar, approve every message in the practice's voice, and set staff notifications.
  • Train the front desk on the pipeline, then review reporting after the first weeks and tune follow-up timing.

10What this demonstrates

  1. 1.Runs a sales demo on the prospect's own business instead of a generic slide.
  2. 2.Designs an end-to-end workflow and makes each integration point visible.
  3. 3.Builds trust by labeling exactly what is live and what is sample data.