Recovery Radar | Private browser-only check

See which clients may be drifting.

Drop or paste a client CSV to identify records whose most recent visit is beyond your chosen window. The file data is processed in your browser and is never uploaded, sent to RelayLaunch, or stored.

Every dollar result is projected from your own average-ticket input. No recovery rate, booking, payment, or recovered-revenue outcome is promised.

Best move now Illustrative sample

Lapsed Win-Back

Rank the first safe win-back opportunity.

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 client-list date and owner-set lapse window
Why now
The relationship is still recent enough for a useful reminder without treating silence as consent.
Audience
One owner-reviewed returning client
Channel
Low-pressure check-in draft
Decision window
Review before the relationship goes colder
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.

Private analysis

Check the list without uploading it.

Use a CSV export with a name column and a last-visit date column. Results show initials only.
Or paste CSV text instead

Does my client list get uploaded anywhere?

No. The file is read and analyzed entirely inside your browser. It is never uploaded, never sent to our servers, and never stored. The page itself loads like any other page on our site, but your client data is never part of any request. Close the tab and your list is gone.

What counts as a lapsed client?

Anyone whose most recent visit date is 30 days or older: about a month or more since you last saw them. That is the same default Relay uses when it builds a win-back list from an imported client file, and you can change it before running the check.

Is the dollar figure real?

It is a projection you can check by hand: the number of lapsed clients you choose to win back, multiplied by your own average ticket. It is labeled (projected) because nothing is real until a client actually rebooks.

How the workflow earns trust

A client-list signal becomes one owner-reviewed next move.

The browser-only check can surface a candidate and simple projected value. Relay still needs owner judgment, an approved message, a configured delivery path, and real outcome evidence.
  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 Radar proof rail

A lapsed record is not a recovered customer.

Candidate found, draft prepared, owner approved, provider accepted, delivered, answered, booked, paid, and verified remain separate.
  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