Using Tasks Effectively in Multi-Location Fitness Franchises: Flows, Assignment, and Follow-Through
How franchise and multi-location fitness brands turn their playbook into tasks: which touchpoints need a human instead of a message, how flows create and assign tasks automatically, and how staff complete them as a natural part of the day.
By Joseph Bona, Founder, Helios
Last updated July 18, 2026
7 min read
Tasks are how a franchise playbook survives contact with the front desk. The system is two halves: flows create and assign the right task at the right moment, from the same member events that drive your automated messages, and staff complete them from a push notification on their phone as a natural part of the day.
Why messages alone do not run a franchise playbook
Automated texts and emails carry most of your lifecycle: welcomes, booking nudges, intro offer sequences, win-back campaigns. But the highest-value moments in a fitness business are human ones: a call when a founding member goes quiet, a face-to-face follow-up after a tour, a manager conversation when someone asks to cancel.
At one studio, those moments live in the owner's head and mostly happen. Across ten or fifty locations, they depend on whichever manager built a habit and whichever front desk remembered. That is the gap tasks close: the playbook decides what a human should do and when, the system hands it to a specific person, and corporate can finally see whether the human half of the playbook is actually running.
Which touchpoints should be tasks instead of messages?
The split is judgment versus routine. If the touch is predictable and the words can be written in advance, automate it. If it needs a voice, a decision, or a relationship, make it a task:
| Moment | Automate a message | Create a task |
|---|---|---|
| New lead comes in | First-touch text within the minute | Only if no reply after the sequence runs |
| Intro offer ending, low attendance | Reminder text | Call from the front desk: "what would make this work?" |
| Long-term member misses 3 weeks | Light "we miss you" nudge | Personal call from their usual coach or manager |
| Tour or drop-in visit | Thank-you text same day | Follow-up call within 48 hours |
| Failed payment | Payment link text | Call for high-value or long-tenure members |
| Membership cancellation request | Confirmation email | Manager save conversation before processing |
| Class milestone (100 classes) | Congrats text with a reward | Shout-out or handwritten note for top members |
Notice the pattern: the message and the task usually come from the same trigger. The failed-payment event sends the payment link to everyone and creates a call task only for the members worth a phone call. One event, two branches, and the human effort lands exactly where it pays.
How to systemize task creation from your playbook
In Helios, a task is a step inside a flow, which means task creation runs on the same engine as your automated outreach: booking events from Mariana Tek, Mindbody, and similar systems, segment entry and exit, and form submissions. Building the system takes four decisions per task:
- The trigger. What member event or segment change means a human should act? Be specific: not "member is at risk" but "member with 12+ months tenure enters the no-visit-in-21-days segment."
- The task itself. Write the task title the way you would brief a new hire, with the context in it: "Call Maya Torres. Intro ends Friday, 1 visit this week, loved the 6 AM class per her form." A task that requires research before starting will get skipped.
- The assignee. Route by role at that location: front desk for follow-up calls, the manager for save conversations, a specific coach for milestone touches. One name per task.
- The due date. Tie it to the trigger, not the calendar: tour follow-ups due in 48 hours, save conversations due same day. The due date is what makes the list self-prioritizing.
Because the flow branches, you can be surgical about when a human gets pulled in. A win-back flow might text everyone on day 0 and day 4, then create a call task only for members who did not rebook and have been with you over a year. Staff time goes to the saves that matter, and nobody burns an afternoon calling people a text would have recovered.
How staff complete tasks without a new system to learn
Systemized creation is half the job. The other half is making completion so low-friction that it becomes part of the shift, not a separate chore:
- One owner per task. Every task is assigned to a person, not a location. Shared to-do lists die at the front desk because everything that is everyone's job is no one's job.
- Push notifications, where staff already are. Assignees get a push on web and on the Helios iOS app, the same app they already use to answer member texts. There is no separate tool to remember to open.
- Complete from the phone, between classes. A front desk person can work the list from the floor: make the call, tap complete, move on. The task sits next to the member's conversation and history, so the context for the call is one glance away.
- Snooze instead of ignore. Real studios have rush hours. A task that cannot happen at 5:45 PM gets snoozed to 8 PM or tomorrow morning and comes back with a fresh notification. Snoozing keeps the list honest; a list full of stale items trains everyone to stop looking.
- Reassign cleanly. When the right person for a save conversation is the manager who is off today, the task moves to whoever covers, with its context intact.
The daily rhythm to aim for at each location is simple: open the app at shift start, work the tasks due today between classes, snooze what genuinely has to wait. If the average shift has more than a handful of tasks, your flows are creating too many; tighten the triggers rather than letting the list rot.
How corporate rolls tasks out across locations
For franchise and multi-location brands, the leverage is that task creation is defined once and executed everywhere:
- Corporate builds the task-creating flows centrally. The at-risk call, the tour follow-up, the save conversation: one definition per play, versioned in one place, wired to the same booking events at every location.
- Tasks route locally. Each task lands with the right role at the member's own location. The playbook is identical; the relationships stay local, which is exactly what franchisees want.
- Execution becomes visible. Completion rate, overdue count, and time-to-complete per location tell corporate who is running the playbook, without anyone sitting in on shifts or chasing screenshots. Coach the outlier locations with numbers, not anecdotes.
This is the same one-playbook principle behind speed to lead and win-back, extended to the human touches. Done right, it is also a better deal for franchisees: instead of a binder of "best practices" they are expected to remember, their staff get a short, concrete list of what to do today. See how this fits the broader operating model in Helios for multi-location and franchise brands.
How to measure whether tasks are working
| Metric | What it tells you |
|---|---|
| Completion rate per location | Whether the human half of the playbook runs at all |
| Median time-to-complete | Whether due dates are realistic and lists are being worked daily |
| Overdue and stale task count | Whether flows create more than staff can absorb |
| Outcome per task type | Whether the play is worth the labor (saves per cancellation task, rebooks per at-risk call) |
The last row is the one to review quarterly. If cancellation-save tasks convert well and at-risk calls do not, shift the human effort and let automation cover the rest. Tasks are a budget: spend them where a person changes the outcome.
Want to see a flow create an assigned task from your own booking data, and complete it from the iOS app? Book a demo.
Frequently asked questions
- What should be a task versus an automated message?
- Automate the routine, predictable touches: welcomes, reminders, nudges, and win-back sequences. Create a task when the touchpoint needs judgment, a voice, or a relationship: calling a high-value member who went quiet, following up after a tour, or a personal check-in when someone cancels. A good playbook uses both, triggered from the same member events.
- How do tasks get created automatically in Helios?
- A flow step creates the task. The same triggers that send automated texts and emails (booking events, segment entry or exit, form submissions) can create an assigned task with a due date at exactly the right moment, like "call Maya, her intro offer ends in 3 days and she has not booked this week."
- How do front desk staff actually work their tasks?
- Each task is assigned to one person, who gets a push notification on web and the Helios iOS app. Staff work from their own list, complete tasks from their phone between classes, and snooze anything that should come back later, like "call after the 6 PM rush." One owner per task means nothing is everyone's job, so nothing is no one's job.
- How does corporate keep task execution consistent across franchise locations?
- Corporate defines the task-creating flows once, and every location runs the same ones. Tasks route to that location's team, so the playbook is identical everywhere while the work stays local. Completion rates and overdue counts per location show who is executing without anyone sitting in on shifts.
