Glass-box recovery | Owner control

See exactly what happens before and after you approve.

Relay finds a lapsed-customer signal, frames one respectful next move, and holds it for your decision. After approval, provider acceptance, delivery, response, booking, and verified revenue remain separate states.

Illustrative workflow. Nothing shown here represents a live customer contact, booking, payment, or recovered-revenue result.

Best move now Illustrative sample

Lapsed Win-Back

Reconnect before a good customer drifts away.

A returning client has been quiet for 47 days and has no future booking recorded.

Prepared next move
Prepare one low-pressure check-in that references the client-approved service history.
Owner approval
View evidence and controls
Source
Illustrative booking history and owner-set lapsed-client rule
Why now
The relationship is still recent enough for a useful reminder without treating silence as consent.
Audience
One owner-selected returning customer
Channel
Low-pressure check-in draft
Decision window
Review while the prior relationship is still recent
Release rule
Owner approval is required before customer contact.
Current state: prepared

Nothing sends from this preview. Delivery and outcomes remain unknown until evidence exists.

How the workflow earns trust

The buyer-facing loop stays simple. The contract stays exact.

The workflow can prepare quickly without collapsing owner judgment into delivery or customer response. Verified value remains separate.
  1. 01 Find

    Surface one source-backed business signal.

  2. 02 Frame

    Prepare the safest move and explain why now.

  3. 03 Approve

    The owner edits, holds, skips, or releases the prepared action.

  4. 04 Follow through

    Track provider acceptance and delivery without calling them outcomes.

  5. 05 Prove

    Attach the real reply, booking, review, payment, or verified non-result.

  6. 06 Learn

    Propose preference changes for approval instead of silently adding autonomy.

Recovery Loop proof rail

Every post-approval state remains independently provable.

Source, owner decision, provider state and outcome stay separate, so a draft never looks recovered.
  1. 01 Signal found Source attached
  2. 02 Action prepared Sample draft ready
  3. 03 Owner review Current state
  4. 04 Owner approved Unknown
  5. 05 Provider accepted Unknown
  6. 06 Delivered Unknown
  7. 07 Customer outcome Unknown
  8. 08 Revenue proof Unknown

The contract under the loop

Seven explicit checks. Nothing hidden.

The six-stage reliability loop is the buyer-facing model. These seven checks are the more detailed operating contract: detect, prepare, hold, decide, queue delivery, record, and stop.

  1. 1 Detect

    Relay spots a regular who has quietly stopped booking — from your own appointment history, not a guess.

  2. 2 Prepare

    It drafts one warm win-back in your voice. Nothing is sent yet.

  3. 3 Hold

    The message HOLDS. It cannot reach your customer until you approve it — that’s the default, not a setting.

  4. 4 You decide

    You read it and tap Approve — or Skip. One tap. You are always the last word.

  5. 5 Queue delivery

    With a supported source configured and synced, approval may enter a configured delivery queue. Provider acceptance is not delivery.

  6. 6 Record

    Relay records acceptance, delivery, response or rebooking, and attributed revenue separately. A receipt stays pending until the result is verified.

  7. 7 Stop

    When they reply or rebook — or you skip — the loop stops. It never nags.

Why this is different

  • Permission, not blast. Many automation tools can be configured to send without per-message review. Relay holds by default — you are the gate.
  • The evidence is yours. Approval, acceptance, delivery, customer outcome, and attributed revenue stay separate in an exportable record.
  • Your brand, your channel. Approved messages use your configured email/SMS channel — customers never see "RelayLaunch."

The loop, in writing

This is the same contract our software reads — published in plain English so you (and any AI assistant answering for you) can check it. Unlike auto-send review/marketing tools, the default state is HOLD: the owner is the gate, not an opt-out.

Trigger
lapsed regular detected (no recent visit)
Goal
an owner-approved re-book
Sends on
the business's own email / SMS
Default state
HOLD until approved
Stops when
customer replies/rebooks, or owner skips
How it's recorded
provider acceptance, delivery, response or rebooking, and attributed revenue are recorded independently; a proof_event is written only for a real verified outcome

What it will do

  • Detect. Spots a regular who has quietly stopped booking, from the owner's own appointment history.
  • Prepare. Drafts one personalized win-back in the owner's voice. Not sent.
  • Hold. The message holds. It cannot reach the customer until the owner approves. Default, not a setting.
  • Approve or skip. Owner reads it and taps Approve or Skip. The owner is the last word.
  • Queue delivery. With a supported source configured and synced, approval may enter a configured delivery queue. Provider acceptance is not delivery.
  • Record. Records provider acceptance, delivery, customer response or rebooking, and verified revenue as separate evidence states. A recovery receipt remains pending until a real attributed result is verified.
  • Stop. When the customer replies/rebooks, or the owner skips, the loop stops. It never nags.

What it will not do

  • It will not contact a customer before you approve — HOLD until approved.
  • approved messages use the business's own configured email/SMS channel and client brand; customers never see RelayLaunch.
  • email by default; SMS only to opted-in customers; reviews may go broader.
  • It will not show a recovered-dollar figure before one is real — renders pending ($—) until a real attributed recovered dollar exists; never a simulated win.

Machine-readable version: /recovery-loop-contract.json — the exact JSON this page is built from.

The questions owners actually ask

Short, straight answers about safety, control, and cost.

Will it message my clients without me?

No. Nothing reaches a customer until you tap approve. HOLD is the default state of the loop, not an opt-out you have to remember to switch on — Relay drafts the message and then stops and waits for you, every single time.

Can I see every message before it sends?

Yes. You read the exact message before it can enter a configured delivery queue, and you tap Approve or Skip. You are always the last word; the system never releases an action you have not personally seen and approved.

Whose brand do clients see?

Yours. Approved messages use your configured business email or SMS channel, in your brand and your voice. Your customers never see "RelayLaunch" — by default email, and SMS only to customers who have opted in.

Do I own the data, and can I export it?

Yes. The action record is yours to export. Owner approval, provider acceptance, delivery, customer response or rebooking, and attributed revenue remain separate evidence states. A recovered-revenue receipt stays pending until a real attributed result is verified.

What happens when a client replies?

The loop stops. When a customer replies or rebooks — or when you skip — Relay ends that thread and does not keep messaging. It never nags.

What does it cost?

A flat $199 per month: cancel anytime, no usage meter, no annual lock, and no required setup fee. 1-on-1 setup help is included, and there are no per-message or per-booking surprises. We never show a recovered-dollar figure until a real, owner-approved recovery has actually happened.

Recovery receipt $— Shows a real amount only after delivery and a real attributed outcome are verified. We never show a number before it's proven.

Built by a veteran founder, dogfooded on our own business first. Every projected figure elsewhere reads Sample until this loop verifies a real, owner-approved attributed result.