Client Return
A thoughtful
return.
Find clients who may be ready for another visit. Review the records, prepare a message and hand it over to your team.
Nothing is uploaded or sent. Clear the page when finished; downloaded files stay on your device.
1. Bring in your records.
Use a fresh export from the salon’s records. Permission must apply to the selected channel and this kind of message. Unknown status stays unresolved.
No client data loaded. UTF-8 CSV, up to 5 MB and 10,000 rows.
What the source export needs
A stable client ID, first name, contact for the chosen channel, last completed visit (YYYY-MM-DD), last service, future appointment status, channel permission and opt-out status. A future appointment date is optional.
Use yes / no for appointment and opt-out status, and granted / denied for permission. Other or missing values are held as unknown. A past service date must represent a completed visit, not a cancelled booking.
This tool has one permission field for the channel selected below. If your export mixes email and SMS permission, map the appropriate channel’s column. Correct unresolved records in your original system and reimport a fresh CSV.
3. Review who to contact.
0 selected. Nothing will be sent.
| Select | Client ID / name | Service / last visit | Days | Why eligible |
|---|
Excluded records
| Client ID | Source rows | Reason |
|---|
Unresolved records
Correct these in the source and reimport. The tool never guesses which conflicting row is right.
| Client ID | Source rows | Reason |
|---|
Record what actually happened.
After the team sends manually and checks the inbox or diary, import referenced outcomes for the client IDs in the latest export. Actual sends, responses and appointments are counted separately, with repeated events deduplicated. These counts do not establish attribution.
Columns: client_id, outcome (sent / response / appointment / cancelled), event_id, event_date (YYYY-MM-DD), source_reference. Use an actual sending-log, inbox or booking reference. Reconcile conflicting or cancelled events in the source before importing.