Operator guide
Review visit gaps and known pauses, ask what changed, and measure replies, return visits and payments separately.
Short answer
Use visit history to find members whose gap is unusually long for them, then ask whether they want to return. A gap longer than twice their usual interval is an example review rule, not proof they have left. Check pauses and contact permissions, send one short personal message naming a specific time, and measure replies, return visits and payments separately.
A drop in attendance may not create a cancellation record. Reviewing visit dates can help staff identify customers whose plans may have changed. This guide is the method you can run yourself; how Fynso prepares win-back outreach describes the product side.
Compare each person with their own visit pattern. Eighteen days may be unusual for a twice-weekly visitor and ordinary for someone who attends monthly. Neither proves their reason for being absent.
The workable version is simple arithmetic on records you already have.
Review the flagged list for known pauses, seasonal patterns and record errors before choosing who to contact.
Choose a review frequency based on the service and normal visit pattern. The table offers example outreach options; elapsed time does not reveal a customer's intentions.
| Time since last visit | What to check | What to send |
|---|---|---|
| 2 to 4 weeks | Check for a planned pause or scheduling issue | One short personal message naming a specific time |
| 1 to 3 months | Ask whether their needs or availability changed | A message with no guilt in it and an easy first step back |
| 3 to 6 months | Review prior contact and permissions | A genuine restart offer, or a question about what changed |
| Over 6 months | This is closer to a new lead than a lapse | Review eligibility before any new outreach |
These are planning examples, not findings about customer motives or guaranteed response rates.
Short, specific, and from a person. Three things to include and one to leave out.
Name what they used to do, so the message is clearly personal. Say something true about why you noticed. Offer one specific time. Leave out the discount until you know what changed.
It sounds like this: "Hi Priya, it is Dana at the studio. Noticed we have not seen you since the start of August, and your Tuesday 6pm slot is still open this week if you want it back."
Ask what changed before deciding whether an offer would help. A scheduling problem may call for a different appointment, while other replies may require staff review.
Record volunteered reasons appropriately and look for patterns. A handful of replies can suggest a question to investigate, not establish the reason every customer left.
A worked example. The numbers are placeholders, not a benchmark. Say a membership is $150 a month. One member who returns and stays 6 more months is worth $900 in billings. If a location has 40 people on the lapsed list and reaching out brings 6 of them back, that is roughly $5,400 over the following months if all six pay for six further months.
Use your own collection, retention and service-cost assumptions. The example describes potential gross billings, not profit or guaranteed recovery from an afternoon of outreach.
Do not book this as recovered revenue. It is a plan, not a result. Count the bookings that actually happened and the visits that actually followed.
Set contact permissions, frequency limits, stop rules and a review owner before starting outreach.
Contact a lapsed customer once, and only once, per attempt window. If they do not reply, the next contact is a month away, not a day.
Stop immediately when someone asks. Record the request where every location can see it, so nobody reaches out from a second list.
Never send the same offer to everyone. A member who came three times a week for a year and a class pack holder who used two of ten sessions are different conversations.
Say true things. "We miss you" from a business that has not been in touch for four months may not ring true. "Your Tuesday slot is open" is true and specific.
Look for clusters in the dates customers stopped attending, then compare them with known schedule, staffing and price changes. A cluster is not proof of a cause.
Check the suspected cause with records and customer feedback before changing the service.
Track customers flagged, eligible customers contacted, replies, rebookings and completed visits. Keep opt-outs visible too. Each measures a different part of the process.
Compare the flagged list with the size and mix of your customer base. Growth in the list can reflect seasonality, a changed rule, new customers or a retention problem; investigate before choosing an explanation. The field note on revenue leakage across locations puts drifted customers alongside the other places revenue slips.
The judgment stays with you. Which lapse is worth a message, and what a returning customer is offered, is a decision about your business, not a setting.
Bringing customers back is the newest part of Fynso, and it is rolling out, starting with one campaign type. Ask the team what that campaign covers, how outreach is reviewed before it is sent, and whether it fits your systems before you plan around it. Lead follow-up is further along: in supported configurations it is live, with a text or call when a new lead arrives within the contact hours and cadence your location approves, booking against real availability, handoff to a named person, and a record of each action.
Every active member or package holder, with their visit dates, from one location.
Calculate the gaps between consecutive visits to estimate usual spacing, then count the days since their last visit.
Anyone whose gap is more than twice their own spacing goes on the list, sorted by gap.
Name what they used to do, say what you noticed, and offer one specific time. No discount in the first message.
Sort the list by the date people stopped. A cluster suggests questions to investigate, not a proven cause.
We will walk through your follow-up, your systems and what Fynso would do, on a discovery call.
A gap more than twice a person's usual visit interval can be a review flag, not proof they have left. Check pauses, seasonality and record completeness before outreach, and compare each person with their own visit pattern rather than one cutoff for everyone.
Name what they used to do, say what you noticed, and offer one specific time. Keep it short and send it from a person. Something like: noticed we have not seen you since August, and your Tuesday 6pm is open this week.
Not as a default. Ask what changed first; a schedule problem may need a different time, not a discount. If you test an offer, compare return visits and margin with the cost of the discount, and keep any genuine restart offer for longer lapses.
Contact once per attempt window and wait a month before the next, stop immediately when asked and record it where every location can see it, never send the same offer to everyone, and only say things that are true.
The first visit proves interest. The second starts a routine. What habit research, gym attendance studies and physical therapy records say about the weeks after a first appointment.
This scenario shows a follow-up need your team can review. Fynso can discuss the workflow, available data and connections for your business before agreeing on scope.
This scenario shows a follow-up need your team can review. Fynso can discuss the workflow, available data and connections for your business before agreeing on scope.
Try it
Enter your website. Fynso learns your business and talks with you in your browser, the way it would with a new customer at any of your locations.