Pricing

Pricing that matches how clinics actually break.

Booking Starter starts at $997/mo for clinics with one clear consult path. Flagship, Autopilot Recovery, and Clinic OS are scoped after we understand your inquiry sources, response depth, calendar model, handoff process, and existing CRM setup.

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

Packages

Start with one clear consult path. Add depth when needed.

Booking Starter gives clinics a clear entry package without pretending every clinic needs the same build. Flagship and Autopilot Recovery add depth only when source count, recovery needs, CRM state, calendar rules, and handoff requirements justify the build.

Booking Starter

One source. One consult path. One primary calendar.

$997/mo Lean monthly starting point

For clinics with one live lead source, one consult path, and one primary calendar. It fixes the response gap without forcing a custom automation build.

One connected inquiry source
Baseline clinic knowledge setup
One response agent
Human-like AI response flow
Name, contact, service interest, timing, and booking intent captured
Fixed 4 to 5 message initial cadence
One primary consultation calendar
Staff summary before handoff

Best fit

Clinics that want a real first response and booking layer without buying custom clinic automation on day one.

Flagship

The complete patient response layer for serious inbound consult flow.

Priced after workflow review Most clinics start here

For clinics that need every serious inquiry answered, qualified, booked, and handed off cleanly around one primary consult motion.

Everything in Booking Starter
Expanded clinic response map
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
CRM source, status, and handoff visibility
Booked consult reminders, sync, and staff handoff

Best fit

Clinics running real paid traffic that need conversations, booking state, source context, and staff handoff to behave like one operational layer.

Autopilot Recovery

Follow-up and recovery for stalled and consult-not-booked opportunities.

Priced after growth plan review For active growth teams

Not every lead is lost. Many are waiting for a follow-up that never comes. Autopilot Recovery picks up stalled threads and re-engages consult-not-booked leads before the window closes. No-show recovery is included when PatientResponse controls the booking and reminder sequence.

Everything in Flagship
Stalled inquiry recovery
Consult-not-booked follow-up
30-day recovery follow-up for stalled and consult-not-booked leads
Reply-based follow-up paths with stop rules, CRM status updates, and staff escalation
No-show recovery when booking sequence is controlled
One primary consultation calendar

Best fit

Clinics that already generate enough demand that missed replies, quiet threads, unbooked consults, or no-shows from a controlled booking sequence are costing real money.

Clinic OS

Build custom clinic routing when one front door is no longer enough.

Custom implementation pricing Custom architecture

For multi-provider, multi-location, or treatment-specific operations that need the clinic operating system designed around custom routing, dashboards, CRM architecture, scheduling rules, and rescheduling workflows.

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 that need the operating system itself designed around service lines, providers, locations, or complex team workflows.

Simple operating model

More package depth does not mean more calendars.

The first three packages are designed around one clean consult front door. A clinic can market several services, like neuropathy care, pain relief, weight loss, or SoftWave, and still fit before Clinic OS when those inquiries book into the same primary consult calendar. The difference 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 when the clinic uses one primary consult calendar. Agent-led rescheduling, multiple providers, multiple calendars, treatment-specific booking rules, or custom routing move the clinic 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 identify the package, then scope the launch work.

The discovery call is where we map your lead sources, response gaps, 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 inquiry path into PatientResponse. Multiple campaigns or service promotions can still 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 consult booking breaks.

We will map your inquiry sources, calendar model, response gaps, and staff handoff so the first version is simple, useful, and operationally clean.

Book a package fit review Learn the clinic flow