Pricing

Start with the response gap you need closed.

The ad platform counts a conversion when the form is submitted. Your clinic only wins when that patient moves into a real consult path. Booking Starter starts at $997/mo for one lead source and one consult path. Flagship, Autopilot Recovery, and Clinic OS are scoped after we map your actual inquiry sources, calendar setup, handoff process, and response workflow.

Starts at $997/mo One consult front door Launch scope reviewed on discovery

Packages

Start with one visible cooling point. Add depth when the volume proves it.

Booking Starter closes the first gap on one inquiry source. Flagship adds the full response layer. Autopilot Recovery restarts qualified threads before they go cold. Clinic OS handles the complexity that a single front door cannot.

Booking Starter

The response layer that stops the bleed on your single lead source.

$997/mo Focused monthly starting point

One connected inquiry source, such as one website form, chat path, or ad lead. One consult path. One calendar. PatientResponse answers the inquiry, captures intent, and books the consult before the patient moves on.

One connected inquiry source
Your core clinic info: services, location, hours, and booking rules
One response agent that replies, asks fit questions, and opens the consult path
Clinic-bounded AI response flow based on your service and booking rules
Name, contact, service interest, timing, and booking intent captured
Fixed 4 to 5 message initial cadence
One primary consultation calendar
Staff-ready note with contact info, service interest, timing, and booking readiness

Best fit

Clinics that have a lead source going nowhere and a front desk that cannot catch every inquiry in time.

Flagship

Every inquiry answered. Every consult booked. Every handoff clean.

Priced after workflow review Most clinics start here

Paid traffic is expensive. When a patient fills out a form or responds to an ad and gets silence, that money is gone. Flagship puts a complete response layer around your consult motion so every serious inquiry gets answered, qualified, and booked.

Everything in Booking Starter
Expanded clinic response logic for services, offers, FAQs, locations, and patient questions
Multiple inquiry sources connected to one primary consult path, including website forms, landing pages, paid ad leads, and social campaign inquiries
Inquiry-specific qualification based on source, service interest, location, and booking readiness
One primary consultation calendar
Visibility into where each lead came from, current status, and what staff needs to do next
Booked consult reminders, sync, and staff handoff

Best fit

Clinics running paid traffic who are tired of watching inquiries vanish into silence.

Autopilot Recovery

The leads you already have are going cold. Fix that.

Priced after growth plan review For active growth teams

Your staff is busy. Your follow-up system is broken. The inquiry that came in three days ago is still sitting there waiting for a reply that never happened. Autopilot Recovery runs the follow-up sequence your team cannot keep up with and re-engages consult-not-booked leads before the window closes.

Everything in Flagship
Stalled inquiry recovery
Consult-not-booked follow-up
30-day recovery follow-up for stalled and consult-not-booked leads
Follow-up sequences that adapt based on patient replies, with automatic rules to stop, update records, or flag staff
No-show recovery when your booking and reminder sequence is connected
One primary consultation calendar

Best fit

Clinics with enough lead volume that intent decay and missed follow-up are quietly costing consultations every week.

Clinic OS

When one front door cannot handle everything your clinic runs.

Custom implementation pricing Custom architecture

Multiple providers. Multiple calendars. Treatment-specific routing. Rescheduling logic. Custom pipelines. Clinic OS is the full operating system built around your actual clinic workflow, not a generic automation that sort of fits.

Multiple calendars or providers
Treatment-specific routing logic
Custom rescheduling automation
Custom pipelines and dashboards
Advanced staff handoff rules
Deeper CRM architecture
Custom implementation roadmap

Best fit

Clinics where complexity has outgrown what a single consult front door can handle.

Simple operating model

More package depth does not mean more calendars.

The first three packages run through one consult front door. A clinic can market neuropathy care, pain relief, weight loss, or SoftWave and still stay before Clinic OS when those inquiries book into the same primary consult calendar. What changes is response depth: what we capture, how much follow-up runs, and how much visibility your team gets before the consult. Standard booked-consult reminders belong in Flagship. Agent-led rescheduling, multiple providers, multiple calendars, or custom routing push toward Clinic OS.

Pricing posture

$997/mo starting point

Priced after workflow review

Priced after growth plan review

Custom implementation pricing

Calendar model

One primary consult calendar

Custom scheduling architecture

Qualification

Contact info, service interest, timing, and booking intent

Inquiry-specific questions by source, service interest, location, and booking readiness

Recovery state and next-best action

Custom intake and routing logic

Calendar automation

Live booking only

Booked consult reminders and sync

No-show recovery only when booking sequence is controlled

Custom rescheduling and scheduling rules

Operating meaning

Booking Starter

Flagship response layer

Autopilot Recovery

Custom clinic architecture

Response depth

Core intake, live booking, and first cadence

Expanded response map, CRM visibility, reminders, and handoff

30-day recovery follow-up with reply-based paths

Custom scripts, routing, rescheduling, and dashboards

Best fit

One focused launch path

Paid traffic and consult conversion

High lead volume and leakage

Complex clinic operations

What happens on discovery

We find the cooling point, then build the package around it.

The discovery call maps your lead sources, visible cooling points, calendar structure, handoff process, and CRM setup. That is how we keep the public package simple without pretending every clinic launches the same way.

One lead source means one connected inbound path. Multiple campaigns or service promotions can stay before Clinic OS when they share the same primary consult calendar, response handoff, and booking motion.

01 Lead sources

Where patient inquiries currently enter.

02 Consult path

Whether demand can route through one front door.

03 Response depth

Which package matches your actual leakage.

04 Calendar automation

Whether the clinic needs standard reminders or custom rescheduling rules.

05 Launch scope

What implementation needs to be built before go-live.

Scope the right package

Show us where patient intent cools off in your clinic.

We will map your inquiry sources, calendar model, response gaps, and staff handoff so the first version closes the right leak without overbuilding your clinic.

Book a Response Gap Review See how inquiries become booked consults