Supporting workflow | Owner-approved follow-through

Bring one quiet opportunity back into view.

Relay can surface an open slot or an aging estimate from a configured source. It prepares one low-pressure next move and waits for the owner.

Illustrative workflow. A prepared draft is not a delivered message, booking, payment, or recovered-revenue event.

Best move now Illustrative sample

Lapsed Win-Back

Reconnect before the relationship goes cold.

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
Sample 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 client
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

One source-backed signal becomes one controlled next move.

The workflow can prepare quickly without collapsing owner judgment into delivery or customer response. Verified value remains separate.
  1. Source connected
  2. Draft prepared
  3. Owner decision
  4. Separate receipt
Open workflow and proof details
  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.

Client follow-through proof rail

A prepared follow-up is not a recovered customer.

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

Where it can help

Four supporting workflows. One decision at a time.

These are optional parts of the broader RelayLaunch operating loop. Start only with the record source and follow-through problem that already exist.
Slot Rescue

Make an open slot visible

Use a configured calendar to surface a real opening and prepare one owner-reviewed fill action.

Review Lift

Use one neutral review rule

Apply the same eligibility rule to completed work and prepare a consistent invitation for approval.

Estimate follow-through

Revisit one aging quote

Show the source estimate, explain why it needs attention, and prepare a respectful follow-up.

Lapsed client follow-through

Reconnect without pressure

Use an owner-set rule to surface a prior client and prepare a low-pressure check-in.

Best fit

Useful when the work already exists but the next step is easy to miss.

This is not a phone-answering service, replacement receptionist, or automatic outreach system.
See examples by business type

Spa and wellness

Useful when booking gaps or returning-client follow-through still live in separate tools.

Auto repair

Useful when open estimates and prior-customer records need a clear next owner decision.

Corporate wellness

Useful when proposals or renewal follow-through depend on manual reminders.

What the record proves

Each state stays separate.

  1. 01

    Source synced

    Operational records inform the workflow only after a supported source is configured and successfully synced.

  2. 02

    Draft prepared

    Relay shows the source evidence and prepares one bounded next move.

  3. 03

    Owner decided

    Approve, edit, snooze, or skip. Approval alone does not prove delivery.

  4. 04

    Later evidence recorded

    Delivery and customer outcomes remain separate records. Revenue stays unverified until a source of record supports it.

Common questions

Know the boundaries before setup.

What has to be connected first?

A supported client, booking, estimate, or review source must be configured and successfully synced before its records can inform a workflow.

Does Relay contact a customer without approval?

No. Customer-facing work waits for owner approval and a configured delivery path. Approval does not by itself prove that anything was delivered.

What does it cost?

Starter is $199 per month with 1-on-1 setup help. It is month-to-month, with no required setup fee or per-message charge.

How quickly should I expect results?

Timing depends on source setup, available records, and owner decisions. A draft or delivery receipt is not a booking, payment, or verified revenue result.

Do I keep my records if I leave?

Yes. The configured records, decision history, and follow-through states remain exportable.

One next move

See whether the workflow gap is real first.

The free AI-Readiness Score is self-assessed and advisory. It does not inspect operational records.
Get your free AI-Readiness Score