Drift Radar
Scores each client against their own rebooking rhythm, with a plain-English reason.
Feature guide · three engines
Three engines. One practice.
Retention IQ brings back clients who stopped booking. Revenue IQ identifies hours going unused. Margin IQ tells you what to change about pricing, packages, service lines, and provider balance so both problems get smaller over time. Underneath all three sits a platform layer of operations, evidence, and trust controls.
Four-minute product walkthrough
See the workflow before you share data.
Insight Over Data walks through Book Value, Drift Radar, Voice Training, and how Retention IQ turns a past-client book into a reviewable action list. The dashboard shown uses illustrative sample data.
Open the video page and transcript contextEngine 01
Retention IQ — bring back dormant clients.
Identifies clients who have drifted past their personal rebooking window, scores the strength of that drift, and prepares personalized outreach for review.
Explore Retention IQ →Voice Training
Uses examples of your writing to prepare drafts in your tone, plus warmer and more-direct variants.
Warm / cool / cold / dormant
Groups clients by how far they have moved from expected cadence.
Draft-for-review outreach
Owner and staff approval remains part of the workflow.
Attributed booking paths
Connects outreach, booking activity, and verified completion evidence.
Industry-calibrated cadence
Different services use different expected return patterns.
Engine 02
Revenue IQ — fill the dead hours.
Finds the specific hours, days, and providers running below expected capacity and surfaces where filling them would matter most.
Explore Revenue IQ →Schedule Value
A rolling forward view of the calendar's booked, expected, and recoverable value.
Demand heatmap
A day-and-hour view that makes recurring low-fill periods visible.
Dead-time detection
Flags repeat capacity gaps before they are lost.
Provider scorecards
Utilization, average ticket, and rebook measures by provider.
Offer guardrails
Keeps discounts away from naturally strong demand windows.
Source-system fit
Adds intelligence without replacing the booking calendar.
Engine 03
Margin IQ — know what to change.
Analyzes booking history, pricing, packages, service lines, capacity, and provider performance, then delivers a ranked set of recommendations.
Explore Margin IQ →Market Index
Compares service prices with eligible local and category reference points.
Package Score
Finds recurring co-purchase patterns that may support a bundle or membership.
Load Balance
Reads provider utilization alongside changes in client rebooking behavior.
Service-line performance
Separates volume leaders from margin leaders.
Capacity & demand
Tests staffing and resource use against the actual demand curve.
Written ranked report
Turns findings into prioritized actions and walks through them in a working session.
Platform layer
Operations, evidence & trust controls.
The three engines decide who to reach and what to say. The platform layer decides how safely it happens: who can see your account, what is never sent, how a recovered visit is proven, and how that proof becomes an invoice.
A return is billed only when it carries a Confirmed evidence grade. Every support session is logged and expires. Every reply is answered by a person. Every do-not-contact request is enforced before a message is built.
Explore the platform layer →Audited support access
Purpose-bound, expiring, read-only support sessions with a persistent banner and audit-trail start/end events.
Platform Operations Center
Attention queue, campaign calendar, message-lifecycle evidence, coverage funnel, and connector health checks every 15 minutes.
Reply triage & human call queue
Inbound replies labeled by intent (clinical, complaint, opt-out) with suggested replies a person sends — never an auto-response.
Permanent contact exceptions
Do-not-contact, -text, -email, and -call rules enforced before every outreach, reply, booking action, and call.
Evidence grades & four-gate evaluator
Confirmed · Attributed · Inferred · Estimated · Unavailable, with known-pass/known-fail self-tests and immutable enrollment snapshots. Only Confirmed is billable.
Import wrangler
Staged batches, row-level validation, reusable column-mapping profiles, provider mappings, and identity backfill with rollback.
Invoice generation
Billing profiles, draft → issue → reconcile, and per-line include/exclude with a recorded reason.
GoHighLevel Marketplace connector
Official OAuth with vault-stored tokens, uninstall handling, dry-run contact identity sync, and a historical message evidence probe.
Medspa offer-ladder margin rules
No paid incentive before Cooling, fixed-dollar credits instead of %-off, and a personal call for high-book-value clients.
Sending infrastructure & incident IDs
Per-practice sending subdomains with DNS verification and warm-up caps, a fallback provider, and every app error tagged with an incident ID.
What every engine shares
One source-of-truth approach.
Existing-system fit
Approved integrations or usable structured exports. No booking-system replacement.
Controlled recommendations
Drafts and operating recommendations remain subject to owner review.
Data ownership
Customer data remains customer-controlled and exportable.
Healthcare readiness
Covered workflows are gated behind data-flow, vendor, access-control, and agreement review.
Choose the engine that answers today's question.
Start with client drift, unused capacity, or margin intelligence. The three engines share a platform, but each solves a distinct operating problem.
15 minutes · no sales pitch
Works with your booking platform