How to Automate Membership Renewals and Win-Back Messages for a Gym or Fitness Studio

A gym rarely loses a member on the day they cancel. It loses them about six weeks earlier, when they stopped coming and nobody noticed, and the cancellation is just the paperwork catching up.

Renewals are the same story told from the other end. A card expires, a payment fails, an annual membership comes up in a month nobody was watching, and somebody who would have stayed drifts off because the only message they received came from a payment provider.

This guide builds two sequences that run off the booking and billing data you already hold: one for the run-up to a renewal, and one that notices a member has stopped attending and says something human about it. Budget about three hours.

What you are building

Two automations sharing one member list. The first watches renewal dates and failed payments and sends a short sequence before anything lapses. The second watches attendance, and when somebody who used to come three times a week has not been in for a fortnight, it puts a message in front of a coach to send.

Tools: your gym or booking software, your payment provider, a spreadsheet if your software will not hand you a list directly, an automation tool such as Zapier, Make or n8n, an AI assistant such as ChatGPT or Claude, and email or SMS.

Step 1: decide what lapsed means before you build anything

Lapsed is not a fact, it is a threshold you choose, and it has to fit how people actually use your place. A gym where the average member comes twice a week can treat fourteen quiet days as a signal. A studio selling ten class packs cannot, because a member with six classes left and a busy month is not lapsing.

• ·Regular attenders: no visit for fourteen days, where the normal pattern is two or more visits a week.
• ·Class pack holders: a pack more than half unused with under three weeks left on it.
• ·New joiners: fewer than three visits in the first three weeks, which is the window where most new memberships quietly die.
• ·Renewals: thirty days out, seven days out, and the day before, for anything annual or fixed term.
• ·Failed payments: the day it fails, three days later, and one final message before access changes.

Write your thresholds down and keep them next to the member list, because everything below is simply a message attached to one of these moments.

Step 2: write the renewal sequence

Renewal messages fail when they read like a payment reminder. The member is not being asked to settle an invoice. They are being asked whether this is still part of their week.

1. 1Thirty days out. No ask at all. A short note with what they have done this year, taken from the attendance record, and the date their membership renews.
2. 2Seven days out. Confirm the date, the amount and what happens automatically, plus one line on anything new starting next term.
3. 3The day before. One line. What will be taken, when, and a direct way to change plan rather than cancel, because a smaller membership is still a member.

The visit count is the part that works, and it is also the part that has to be right. Pull it from the attendance record rather than letting the assistant estimate it, and if the figure is not available, drop the sentence rather than filling it with something vague.

Step 3: the win-back message comes from a person

The renewal sequence can send itself. The win-back should not, at least for the first few months, because the message that works is the one that sounds like the coach who knows them.

Put the drafts in a list a coach reads once a day, with the member name, when they last came and what they usually do. Sending ten of those takes ten minutes, and it is the highest value ten minutes in the building.

Step 4: wire it up

1. 1Once a day, pull the member list with plan, renewal date, payment status and last visit date. If your software will not export on a schedule, a weekly manual export into a sheet still works.
2. 2Compare each member against the thresholds from step one and tag anybody who matches one today.
3. 3Check the stop column and the suppression list before anything else happens.
4. 4For renewal and failed payment moments, fill the saved template and send it.
5. 5For attendance moments, fill the win-back template and put the draft in the coach list rather than sending it.
6. 6Write a timestamp against the member and the moment, so nobody receives the same message twice and a coach can see what has already gone out.
7. 7Once a week, take anybody who has since attended or renewed off the open list automatically.

Test the whole thing against your own membership record first, including a failed payment if your provider offers a test mode. A renewal message with the wrong amount in it is the one mistake in this build that generates a phone call from every member who receives it.

What changes

Nobody drifts out in silence. A member who has stopped coming hears from a coach in the second week rather than reading a cancellation confirmation in the eighth, and a renewal arrives as a conversation that started a month earlier instead of a line on a bank statement.

Keeping people warm, before and after they buy, is the subject of Workflow 04: Get More Customers, the AutomateFirst module about lead generation and follow-up sequences that stop good enquiries going cold. This guide is one complete build from it, free. The playbook has seven workflows for one payment of $297, with a 30 day refund.