Store each member's last visit date in a field, flag anyone who has not visited for 10 days, and send a short personal text from a coach with a task to follow up if there is no reply. GoHighLevel can run the flag, the text, and the task, but it cannot see door scans by itself, so your check in system has to send the visit date into it. The bottom line: members rarely cancel the week they stop coming, so the quiet gap is the window where a message still works.
What the numbers say about attendance
The Health & Fitness Association reports that the average member visited 1.5 times per week in 2024, down from 2.1 in 2019, according to its 2025 U.S. consumer report as cited by Glofox. The same source cites an HFA finding that two staff interactions per month produced one extra visit the following month and cut cancellation risk by 33 percent. That page does not give a year for the staff finding, so use it as direction. The takeaway is that a human touch between visits changes behavior, and a quiet member is a member who has not had one.
What HighLevel can see and what it cannot
| Data | Can HighLevel see it | How to get it in |
|---|---|---|
| Form submissions and bookings made in HighLevel | Yes | Native |
| Door scans or app check ins from your gym software | No, not by itself | Send a webhook, or use Zapier, Make, or n8n to update a Last Visit Date field |
| Replies to texts | Yes | Conversations and the Customer Replied trigger |
| Payment status | Yes, if billing runs through HighLevel | Subscription and Payment Received triggers |
Be plain about this limit when you plan the build. If your gym software cannot send visit data out, the workflow can still use class bookings made through a HighLevel calendar, but it will miss members who walk in without booking.
The month 2 workflow
- Create a date field called Last Visit Date and a tag called quiet 10 days.
- Feed the field from your check in system through a webhook or an automation tool.
- Build a Smart List of active members whose Last Visit Date is more than 10 days ago and who do not have the tag frozen.
- Start a workflow for each match. Send a text from the coach's name, such as a short message that asks if they want to book a session this week, and include one booking link.
- Create a task for the coach if there is no reply after two days, so a person makes a call.
- If the member replies, move them back to the active group and clear the quiet tag. If they ask to cancel, route them to the cancellation article's process, not to another sales text.
Use the Drip Mode option for bulk actions when a Smart List returns many members at once, so a whole list does not get texted in the same minute.
Keep it from feeling like a collection notice
- Write from a named coach, not from the club account.
- Offer something useful, such as a time with open seats or a short session, rather than asking about the bill.
- Send at most one message per 10 day gap, and stop when the member replies.
Sample messages and the follow up task
- Text from the coach: Hi {{contact.first_name}}, it is Coach Marcus. I noticed we have not seen you this week. Want me to hold a spot in Thursday's 6 p.m. class? Reply YES and I will book it. Reply STOP to opt out.
- If there is no reply after 2 days, the task reads: Call {{contact.first_name}}, last visit {{contact.last_visit_date}}, ask what is getting in the way, offer a different class time.
- If the member says work got busy, offer a freeze or a shorter weekly goal, and record the choice in a note on the contact.
The goal is to make returning easy. A member who is asked to hold one specific class has a simple next step, while a general note that says we miss you gives them nothing to do.
Choosing the right gap
| Member pattern | Gap that triggers a message | Reason |
|---|---|---|
| Visits 3 or more times per week | 5 to 7 days | A gap is unusual and a sign of trouble |
| Visits about once per week | 10 days | One missed week is normal, two is not |
| Visits every 2 weeks | 21 days | Their normal rhythm is slow, so wait longer |
| New member in first 60 days | 7 days | The habit is not yet formed |
The Health & Fitness Association figure of 1.5 visits per week in 2024, cited by Glofox, is an average, so use each member's own history when you can. If you can only store the last visit date, a single rule of 10 days is a fair starting point, and you can refine it once you have a few months of data.
What to measure
- Reply rate to the coach text.
- Visits in the 14 days after a message, compared with members who were not contacted.
- Cancellations in the 60 days after contact, compared with the prior 60 days.
- Tasks completed within 2 days, so you know the human step is happening.
Common mistakes
- Texting members who froze their membership. Exclude the frozen tag.
- Sending the same message every week. Limit it to one per gap and stop when the member returns.
- Making the message about the bill. This is a visit prompt, not a payment reminder.
Questions people ask
How long should a gym wait before contacting a member who stopped coming?
Ten days is a common starting point for a member who normally attends weekly. Adjust it to each member's usual pattern.
Can HighLevel track gym check ins?
Not by itself. Your check in system must send the visit date in through a webhook or an automation tool.
Who should send the message?
A named coach or staff member, so it reads as a personal check in rather than an automated notice.
To build the month 2 check in workflow, start a GoHighLevel account here. The workflows are shown in our capabilities demo.
