RepairLink 4 — Follow-Up

No-Response Recovery Sequence

Recover prospects who PREVIOUSLY engaged — replied, expressed interest, requested information, began qualification, or showed intent — and then stopped responding. This is distinct from initial cold/non-contact…

Link

Link Name

Follow-Up

Playbook

Follow-Up Playbook

Role

workflow

Loop Step

Repair

Review State

in_review

Delivery Status

content_ready_delivery_pending

Purpose

Distinction From RLR23

RLR-23 persists on opportunities that have not yet had a conversation. RLR-24 re-engages opportunities that DID engage and then went quiet. Messages here must use prior context and must never pretend no prior conversation occurred.

Prior Engagement Contexts

prospect replied previously
qualification started but did not complete
prospect requested a callback
prospect asked for information
appointment was discussed but not booked
prospect indicated intent but disappeared
prospect asked to reconnect later
conversation stopped mid-process

Configurable Variables

[First Name]
[Prior Request]
[Service]
[Last Conversation]
[Requested Time]
[Responder]
[Appointment Link]
[Callback Number]

Touch Schema

Fields: attempt_number; elapsed_time; channel; objective; message_or_script; owner; next_action; stop_condition; escalation_condition; disposition_update

Sequence

reconnect SMS

Attempt number: 1
Channel: sms
Objective: reconnect
Message or script: 'Hi [First Name], it's [Responder]. When we last talked about [Prior Request] you were interested — I don't want to let it slip. Want me to pick up where we left off?'
Owner: [Responder]
Next action: Await reply; if none → attempt 2
Stop condition: Reply received
Escalation condition: Explicit high intent → escalate to human review (see escalationRules)
Disposition update: recovery_attempted

reconnect call opener

Attempt number: 2
Channel: phone
Objective: reconnect
Message or script: 'Hi [First Name], [Responder] again — following up on [Prior Request] from [Last Conversation]. Nothing urgent on my end, I just didn't want to leave you hanging. Is now okay for two minutes?'
Owner: [Responder]
Next action: If no answer → voicemail attempt 3
Stop condition: Two-way contact
Disposition update: recovery_attempted

voicemail

Attempt number: 3
Channel: voicemail
Objective: reconnect
Message or script: Brief, context-aware voicemail referencing [Prior Request] and one concrete next step; leave [Callback Number].
Owner: [Responder]
Next action: Email attempt 4
Stop condition: Callback received
Disposition update: recovery_attempted

reconnect email

Attempt number: 4
Channel: email
Objective: clarify_need
Message or script: 'Hi [First Name] — circling back on [Prior Request] for [Service]. Did your plans change, or should we get you [Desired Outcome]? Reply here or grab a time: [Appointment Link].'
Owner: [Responder]
Next action: Await reply; if none → attempt 5
Stop condition: Reply received
Disposition update: recovery_attempted

value / reminder message

Attempt number: 5
Channel: sms_or_email
Objective: offer_useful_next_step
Message or script: Share one genuinely useful item tied to [Service] (answer to their earlier question, relevant option, availability) — not generic marketing.
Owner: [Responder]
Next action: Await reply; if none → attempt 6
Stop condition: Reply received
Disposition update: recovery_attempted

friction-reduction message

Attempt number: 6
Channel: sms
Objective: reduce_booking_friction
Message or script: 'Hi [First Name] — want me to just handle the scheduling for [Prior Request]? I can hold [Requested Time] and you only confirm. Yes/No works.'
Owner: [Responder]
Next action: Await reply; if none → attempt 7
Stop condition: Booking or reply
Disposition update: recovery_attempted

timing-reset message

Attempt number: 7
Channel: email
Objective: confirm_whether_timing_changed
Message or script: 'Hi [First Name] — is [Prior Request] still on your radar, just later? Tell me roughly when and I'll reach out then instead of now.'
Owner: [Responder]
Next action: If timing-later reply → nurture (RLR-25); if none → attempt 8
Stop condition: Reply received
Disposition update: recovery_attempted

final active-recovery message

Attempt number: 8
Channel: phone_or_sms
Objective: reconnect
Message or script: Final active attempt, honest and low-pressure: 'Last note from me for now on [Prior Request], [First Name] — if it's still useful I'm here at [Callback Number]. Otherwise I'll assume timing isn't right and check back later.'
Owner: [Responder]
Next action: If no reply → transition to nurture
Stop condition: Reply received
Disposition update: recovery_attempted

transition-to-nurture message

Attempt number: 9
Channel: email
Objective: transition_to_nurture
Message or script: Clean handoff to nurture referencing prior context: 'I'll stop the active follow-up on [Prior Request] so I'm not crowding you. I'll check back later unless you tell me to hold off — reach me anytime at [Callback Number].'
Owner: [Responder]
Next action: Enter RLR-25 nurture with reason = timing_delay or requested_future_contact
Stop condition: Sequence complete → nurture
Disposition update: nurture

Escalation Rules

Principle: A previously engaged prospect who signals renewed high intent (e.g. asks to book, replies with urgency, requests a call now) must be escalated to human review rather than continuing through automated steps.
Triggers: explicit booking request; urgent reply; callback request with time; complex/high-value opportunity re-surfacing
Action: Route to a named human owner (per RLR-20) immediately, pause automated touches, and hand off with full prior context. Defined in detail in RLR-26.

Compliance Guardrail

Honor opt-outs, channel permissions, business-implemented suppression, do-not-contact requests, and approved communication policy. Do not bypass provider restrictions, opt-outs, or consent controls. Recovery messaging must reference real prior context truthfully.

Handoff To Link5

On re-engagement to booking readiness, hand off to Link 5 with readiness, booking intent, preferred timing, qualification summary, and the recovery/prior-conversation context.

What To Measure

Recovery-attempt reach, re-engagement (recontact) rate, appointment rate from recovery, escalation rate, and nurture-transition rate.

Data Required

Prior-engagement context per lead plus per-touch execution logs and disposition updates.

How To Interpret

Low recovery response with full coverage indicates the prior context isn't being used well or timing has genuinely shifted (→ nurture); high escalation with poor human follow-through points to a Link 5/ownership gap.

Action That Follows

Deploy per prior-engagement context, wire escalation to human review (RLR-26), and route timing-delay outcomes to nurture (RLR-25).

Owner

Follow-up owner from RLR-20; escalations to the named human owner.

How To Implement

Populate context variables from Link 3 outputs and prior conversation records, configure timing/channels, and connect escalation and nurture branches.

How To Test

Run on quiet previously-engaged leads with QA; confirm messages reference prior context, escalation fires on high-intent replies, and dispositions/nurture transitions write correctly.

When To Remeasure

At 14 and 30 days via RLR-22 re-audit.

How To Know It Improved

Re-measured recontact and appointment-from-recovery rates rise and quiet previously-engaged leads are no longer marked lost without recovery — evidenced by data, not by installation.

How to implement

Install the change exactly as the playbook describes; log it on the Repair Plan.

How to verify

Installing a workflow is implementation, not closure. QA the repair before you trust it.

Rather not do this part yourself?

You can repair your Revenue Chain yourself with this Kit — or bring in ShiFt at any point. You do not need to finish the DIY path first.

Done with you

Revenue Leak Scan

A ShiFt specialist runs the diagnosis with you and hands you a prioritized repair plan.

Get My Revenue Leak Scan

Done for you

ShiFt RevenueOS

ShiFt installs and operates the full Revenue Chain system for you — ConvertOS included.

See RevenueOS