Engine 2 · Long-Arc Trust & Reactivation

Engine 2 — The Trust Phase

The compounding engine. Every patient already in the database — systematically re-engaged.

Engine 1 wins the first six days. Engine 2 wins everything that happens after. Booked patients, "not yet" leads, stalled treatment plans, lapsed alumni — every record in the database has a place in the cadence, and every one is treated with care that matches their stage in the relationship.

The "think about it" case becomes the booked case. The "we'll come back in the autumn" becomes the September consult. The patient who finished treatment two years ago becomes the referral that brings their partner in.

Engine 1 Day 0 → Day 6 · Capture + qualify + first call
Handoff
Engine 2 Day 7 onwards · Trust, reactivation, amplification

What Engine 2 runs

01

Pre-Arrival Nurture

Psychology-backed cadence between booking and attendance. Short (1–3 days), Mid (4–7 days), and Full (8+ days) branches — content matches how long the patient has to wait.

02

Appointment Reminders

Tag-triggered, date-calculated touches at 48h, 24h, and morning-of. Confirmation replies flow back into the record. Reschedule requests route to reception without noise.

03

Attendance Tracking

Checked-In vs Did-Not-Attend handling. Attendance closes the Trust cadence gracefully. DNA routes into the recovery flow immediately.

04

DNA Recovery

Structured rebooking outreach for patients who didn't attend. Staff wait window, then patient-facing SMS, then a reception task if still open. No drop-outs.

05

Post-Treatment Loop

Review request, testimonial capture, referral invitation, upsell flag for high-lifetime-value cases. The "wow" moment turned into a repeatable advocacy loop.

06

Long-Term Nurture

For the leads who said "not yet" at the end of Engine 1 — up to 12 months of monthly educational touches. Purchase Moment triggers watching the whole time.

Why it compounds

Every Engine 1 enquiry that doesn't convert inside six days becomes an Engine 2 asset. Every appointment that books generates an Engine 2 pre-arrival sequence. Every completed treatment feeds into Engine 2 testimonials and referral mechanics. The database turns into a flywheel: every cycle of Engine 1 feeds more patients into Engine 2, and every Engine 2 Purchase Moment re-enters Engine 1 as a booked consultation.

That's the difference between a CRM that stores records and a growth engine that produces them.

How the record travels

The same contact record WF01 creates on Day 0 stays with the patient through Engine 2 — through the booking, the pre-arrival cadence, the appointment, the post-treatment loop, and any subsequent reactivation. Reception sees the whole journey on one screen. Nothing gets re-keyed, nothing gets lost between pipelines, and every touch is informed by every prior touch.