When a contact converts from an intro offer to a full membership, a new set of workflows takes over. These handle the long-term relationship: welcoming them as a member, building connection through a 60-day email nurture, celebrating attendance milestones, notifying the studio on birthdays, and managing lifecycle changes like suspensions and inactivity.
The 60-day member nurture
The centrepiece of the membership journey is a 60-day email sequence that runs automatically after someone becomes a member. It builds the relationship gradually: welcome, then tips on getting the most from their membership, then community (bring a friend), then brand depth, then feedback, and finally milestone and longevity content.
01. 60 Day Member Journey
A multi-week email and SMS nurture sequence for new members. Sends 8 emails and 2 SMS messages over approximately 60 days, spaced out with wait periods. Each message checks for DND status before sending.
DND checks before every message
The 60 Day Member Journey checks DND status before each email. If a member has Do Not Disturb enabled (because they replied STOP, for example), the email is skipped but the sequence continues. This means they may receive later emails if DND is later removed, but no messages are sent while DND is active.
Two supporting workflows keep the 60-day nurture clean:
00. 60 Day Journey | Tagging Current Members so they don't pass through the new 60 Day Journey
A one-time utility workflow that tags existing members with the '60 day member nurture' tag. This prevents current members from receiving the nurture sequence, which is designed only for new members.
02. 60 Day Member Journey | Remove from workflow when Location Status = inactive
If a member's location status changes to inactive during the 60-day nurture (they cancelled or their membership lapsed), this workflow removes them from the nurture sequence.
Attendance milestones
STRONG celebrates attendance milestones at 50, 100, 200, 500, and 1,000 classes. Rather than detecting the exact milestone number, the workflow fires 3 classes early (at 47, 97, 197, 497, and 997) to give the studio team time to prepare a celebration.
02. Attendance Milestones Notification
When a member reaches 3 classes before a milestone (47, 97, 197, 497, 997), creates a task for the studio to prepare the celebration and sends an internal notification to the assigned user.
3 classes early, not at the milestone
The workflow fires at 47, 97, 197, 497, and 997 attendance, not at the milestone number itself. This gives the studio 2 to 3 classes to prepare. By the time the member hits 50 (or 100, 200, etc.), the team is ready with whatever celebration they have planned.
Birthdays
The birthday workflow sends an internal notification to the studio on a contact's birthday so the team can prepare a personal touch. It handles both members and leads differently.
03. Birthday Studio Notification
On a contact's birthday, notifies the studio with an internal email. Creates a preparation task for active members and package holders. Sends a different notification for leads (contacts with no active package).
Suspension handling
When a member suspends their membership in Core, the sync updates their Location Status to “suspendedMembership” in Grow. Two workflows handle this:
05. Membership | Suspensions
Detects when a member's Location Status changes to 'suspendedMembership'. Tags them as suspended, stamps the suspension date, then watches for when they return to active or go inactive.
99. Current Member Suspensions (batch tagging)
A utility workflow for batch-tagging currently suspended members. Used when setting up a new location or after a data cleanup to ensure all suspended contacts have the correct tag.
Why 'recently suspended' matters
When a member comes back from suspension, their Active Package updates. This would normally trigger the “Update Date Membership Purchased” workflow and re-stamp their purchase date as today. The “recently suspended” tag prevents this: the purchase date workflow checks for this tag and skips the update if it is present.
Inactivity detection
06. Location Status = inactive
When a contact's Location Status changes to 'inactive' (cancelled membership, expired package, or account deactivated), removes all active status tags to keep the data clean.
Days absent (draft)
A Days Absent workflow exists as a draft but is not currently published. When enabled, it would send SMS reminders and create studio tasks at 7, 14, and 21 days of no attendance for members.
01. Days Absent SMS | 7, 14 and 21 Days | Memberships Only
When a member has not attended for 7, 14, or 21 days, creates a task for the studio and sends an internal notification. Checks that they are still an active member and not recently suspended before acting.
Attendance tracking utilities
Two published workflows maintain weekly and monthly attendance counters. These are simple math operations that increment a counter field each time a contact's attendance total changes. Studios use these for check-in dashboards and reporting.
07. Weekly Check-ins | When Attendance Total changes, add 1 to weekly check-in field
Increments the weekly check-in counter by 1 each time a contact attends a class. The counter resets on a schedule (managed outside of workflows).
10. Monthly Check-ins | When Attendance Total changes, add 1 to monthly check-in field
Same as the weekly check-in but for the monthly counter. Used for monthly attendance reporting.
What the member experiences
From a member's perspective, the membership journey feels personal and well-timed:
- Week 1: they receive a welcome email celebrating their membership.
- Weeks 2 to 8: they receive emails about getting the most from their membership, bringing a friend, the science behind STRONG, and a feedback request. Spaced out so it feels natural, not like a blast.
- Around their birthday: the studio acknowledges it personally (how depends on the location).
- Approaching 50, 100, 200, 500, or 1,000 classes: the studio prepares a celebration 3 classes in advance.
- If they suspend: the system tracks the suspension and handles their return cleanly.
- If they go inactive: all active tags are removed and they exit the automated messaging.