A fitness studio reactivated 118 lapsed members with a rebooking funnel

Representative examplesEvery case study in this library is an illustrative composite of the kind of engagement we deliver — written to show our method and standards, not to name clients.

Where they started

Three neighborhood locations, coaches who know members by name, and a monthly membership — this boutique fitness studio group runs on personal relationships, and it loses members the way every studio does: people move, get injured, change jobs. Member records lived in a booking system the front desk used for schedules, with cancellations marked by date and little else. The owner knew lapsed members personally and win-back happened when he happened to see someone around the neighborhood. A monthly newsletter went to everyone, including people two years gone.

What it was costing

Lapsed members — people who had already loved the studio — received nothing after cancelling except a newsletter. Win-back relied on the owner remembering faces, and no record existed of who had lapsed and why.

What they could see

• Cancellations were recorded as a date and a checkbox — no reason, no note, no follow-up owner.
• The owner could name perhaps a dozen lapsed members from memory; the actual list held hundreds.
• Lapsed members kept receiving the monthly newsletter as if nothing about their situation had changed.
• Front-desk staff had no way to see who was worth a personal message this week.
• Win-back attempts, when they happened, started from zero — nobody could recall what the member's last classes were.

The constraints we worked inside

• Members left for real reasons (injury, move, price) — messaging had to respect the reason, not blast uniformly.
• Front-desk staff run the follow-up between classes; automation does the tracking.
• The studio's voice is personal — sequences had to sound like the owner, not a machine.

What had been tried before

The group ran a 'come back' discount blast to its full list twice a year.

A uniform offer hit the member out with a knee injury and the member who moved towns with the same message, and the few who returned rarely stayed past the discount.

The owner asked coaches to text members they personally missed.

Coaches meant well but had no list, no timing, and no backup when classes got busy; effort depended on who remembered whom, and the results showed exactly that.

What we proposed

Segment lapses by reason, not by date: the pipeline tags each lapsed member by departure reason drawn from exit notes, so every sequence speaks to the actual gap — schedule, injury, or price — instead of a generic 'we miss you'. A lapsed-member page with a two-week reactivation offer routes bookings straight into each location's real class calendar, with the front desk watching every step. Sequences are drafted from the owner's actual messages, so automation handles when a message goes, never what it says.

Just as important is what we ruled out, and why:

• A better-targeted blanket win-back discount — Even aimed well, a discount tells the injured member to push through pain and tells the price-sensitive member the money was the only barrier worth a coupon; the reason is the message.
• A loyalty app with automated win-back features — A new app for a member base that already ignores one newsletter adds a login between the studio and its people; the owner's voice is the asset, and it cannot live in an app.
• Hiring a part-time retention coordinator — The front desk was under-used between classes, not understaffed; the gap was memory and tracking, which automation covers, rather than hours nobody has.

How the work ran

Delivered by the growth pod — strategist + automation specialist over 4 weeks, with working increments reviewed with the client every week.

The stack, and the reasoning

GoHighLevel funnels

The reactivation page had to feel like the studio — plain, warm, one clear offer — and the funnel builder delivered it without asking the group to run yet another web platform.

Calendars

Rebooking is the entire conversion; slots connect to each location's real class schedule so a returning member picks a class that exists, at a time the desk can actually staff.

Opportunities & Pipelines

Every lapsed member becomes a card with a reason and a stage — the desk sees a Tuesday list of ten names worth a message instead of an unfiltered export of hundreds.

SMS/email sequences

Sequences carry the owner's phrasing and pause on replies, so a member who texts back about a knee gets a human answer, not the next scheduled message.

What went wrong

How we worked together

Cadence

Tuesday morning coffee with the owner and one front-desk lead — 25 minutes, one weekly reactivation number read out, one decision made.

Client side

The owner owned voice and offer; two front-desk leads owned pipeline hygiene and the weekly call list; coaches fed back what returning members actually said.

Decisions

Decisions were logged on the member's card the day they came up, with the desk lead noting the offer and the reason; anything touching money waited for the owner's call at the Tuesday coffee.

They provided

Cancellation records and exit notes from the booking system, class schedules for all three locations, two hours of the owner talking through old win-back texts, and desk time for the tagging sprint.

What changed

The headline: lapsed members rebooked within the first 60 days of the funnel — 118, read from Pipeline reactivation stage. A second check: reactivation rate across the full lapsed list at 9.1%.

The studio got some of its people back — not as a campaign, but as conversations the desk was finally equipped to have. Coaches noticed returning faces they had wondered about for months. The owner stopped carrying the win-back problem in his head; the list remembers now, and it remembers why each person left. The newsletter went back to being news for current members, and the front desk describes the Tuesday list as the easiest part of their week — ten names, one message each, done before the first class.

The result was read from Pipeline reactivation stage against the pre-engagement baseline over the stated window, with a guardrail check on reactivation rate across the full lapsed list. Where platform-reported numbers and business outcomes differ, this record says which layer it is quoting.

What they own now

• The lapsed-member pipeline with reason tags and documented stage definitions.
• The reactivation funnel and offer-calendar template for future pushes.
• Sequences in the owner's voice with a guide for refreshing them each quarter.
• A front-desk one-pager for handling replies, covering injury and move cases.
• The closure-date block list procedure for the booking calendar.