Three members asked Iris about the new late-cancel rule after her Thursday 6pm class. The letter to members had gone out on Tuesday, and Iris had not heard of the change. It had reached her on Monday night, as message 23 of 41 in the all-staff group text, between a photo of the new mats and a sub request for Wednesday's noon class. She saw the photo. She answered the sub request.
Nobody did anything wrong, exactly. The message was sent, and it arrived. But that week Iris got studio messages in six places, and nothing said which were for her. This piece rebuilds instructor communication around one idea, one home for each kind of message, on an invented studio: Alturra Studios, 240 members at $169 a month across three sites, Downtown, Old Town and Riverside, with 15 instructors and ten more people on the team.
Instructor communication in one minute
- One home for each kind of message. Policies, sub requests, schedule changes, member notes and quick questions each go to one place, and everyone knows which.
- Must-reads are counted, not assumed. Ask each person to confirm, then chase only the ones who haven't.
- A buzz means “this is for you.” Everything else waits, unread and silent, inside each person's own hours.
| The habit | What it fixes | At Alturra |
|---|---|---|
| One home per kind of message | “I never saw it” | five kinds, one home each |
| Channels from sites and roles | messages for the wrong people | eight channels; Iris is in five |
| Must-reads, counted | not knowing who read it | 12 of 15, then three reminders |
| A buzz only for “for you” | phones set to silent | five things buzz; the rest waits |
| Everyone keeps their hours | the 10pm text | Iris: 7am to 8pm, Sundays off |
| The handbook answers | the same question six times | one policy page, linked, not retyped |
Why do instructors miss messages?
Because the messages arrive in too many places, and nothing marks the few that matter. An instructor who teaches a handful of classes a week has no reason to read 41 messages in a group text, so she skims, and a skim catches the photo, not the policy.
Instructors are not at a desk: they teach at 6am and 7pm, some at more than one site, with the phone in a cubby between classes. Every place you add is one more to check, and each mixes the urgent with the social. A group text cannot even show who has read what, so the first sign that a message missed is a member asking about it.
The fix is fewer places, each with one job, and a clear signal on the few messages everyone must read.
Where should each kind of message go?
Give each kind of message one home, and tell the team which is which. Five kinds cover almost everything a studio sends its instructors, and one rule covers anything personal.
A policy change is a post to the people it affects, marked must-read, with the full policy in the handbook the same day. A sub request goes where your schedule lives, in the booking platform or the tool you already use for subs, so the swap shows where members book. A schedule change is made in the schedule first, then posted in that site's channel for the people it moves. A quick question goes in the site or role channel, and the answer is a link to the handbook wherever one exists.
A member note, such as an injury she mentioned or a regular who has stopped coming, goes on the member's record, where her next instructor will see it, not in a group text on twenty personal phones. Instructors often notice a regular starting to fade first, and that note is where a save begins: a call from someone she already knows. Pay, feedback and anything personal go one to one, never in a group.
What to do this week:
- List every place your instructors get studio messages today, and count them.
- Write the five homes and the one-to-one rule on one page, and send it once.
- For two weeks, answer any message that lands in the wrong place in the right one, with a link.
Is a group text enough for instructors?
For four people at one site it can be; past that, one group text mixes every site, role and kind of message, and the important ones scroll away. It also cannot mark a message as must-read or show who has read it.
Its other costs arrive later. Everyone's personal number is shared with everyone. An instructor who moves on keeps months of your studio's conversations on her phone, while a new hire starts with none of them. Member names and the odd complaint sit on personal phones, outside anything the studio keeps.
Good fitness studio staff communication needs three things a group text lacks: separate places for separate audiences, a way to mark and count the messages that must be read, and a record the studio keeps. The setup matters more than the software.
How should you set up channels for a studio team?
From the two things that decide who needs a message: where each person works, and what they do. That gives any studio the same short list: channels for the whole team, one for each site, one for each role, and a private one for managers.
At Alturra that is eight channels. Only managers post in # announcements, so it stays short enough to read, and # everyone takes the rest of the whole-team talk. Each site's channel holds everyone who works there, and # instructors and # front-desk hold that team plus the managers. Each person is in the channels that fit their role and sites, and no others.
The grid also tells a manager where to post: a change for everyone in # announcements, one for a site in its channel, and one for Old Town's instructors in # old-town, addressed to them, so the desk there knows too. Running several locations makes this matter more: one group text mixes more with every site.
Resist a channel per topic, which goes quiet in a month and stays in everyone's list; add one only for a group with ongoing work, such as the teachers of one format.
What to do this week:
- Make the channels, and put each person only in the ones that fit where they work and what they do.
- Close the old group texts with one last message saying where everything lives now.
How do you announce a policy change to your instructors?
Tell the people who have to enforce it before members hear it, post it once where they will see it, and ask each person to confirm they have read it. Then chase only the ones who haven't, one to one, instead of sending it to everyone again.
Alturra's new policy, from November 1, is the one worked out in the late cancellation policy piece: six hours' notice, or 8pm the evening before a class that starts before 9am, and one free pass every 90 days. In the right order:
- Two weeks before: a must-read post to the instructors, and one to the desk with its two sentences for the counter, each titled with what changed and when, with the reason: a fair chance for the waitlist.
- The same day: the full policy goes in the handbook, and both posts link to it.
- Two days later: count who has confirmed, and remind only the rest.
- A week before: the member letter, once every instructor and desk shift can answer questions. The price increase letter shows the shape of a good one.
By Wednesday, 12 of the 15 instructors had confirmed, two had opened it without confirming, and one had not opened it. Three reminders reached those three; a second message to all fifteen would have taught the other twelve that a first message can wait. By Friday it was 15 of 15, before the letter to members had even gone out.
Keep must-read for what truly is: a policy, a safety change, a new routine at the door. If everything is must-read, nothing is. And put waiting must-reads on the front desk's opening checklist, so a change reaches the desk before the first member does.
What should buzz an instructor's phone, and what can wait?
Only what is for her: a message to her, a mention of her or her group, a must-read she has to confirm, and a reply in a thread she is part of. Everything else can wait, visible but silent, until she chooses to look.
If every message buzzes, people mute the whole studio, and then the must-read does not buzz either. So agree as a team that a buzz means “this is for you,” and set phones to match. Chatter, a question for anyone and someone else's thread should only mark a channel unread.
Managers carry most of this: name the person or group a message is for, save a mention of everyone for the rare message that truly is, and answer in threads so the channel stays readable.
Should instructors get work messages outside their hours?
Not as a buzz, unless it is an emergency, and an emergency is a phone call. Let each person choose the hours notifications reach them, and agree that nobody expects an answer outside them.
Instructors do not keep office hours. Iris teaches at 6am on Monday, Wednesday and Friday, at 6pm on Tuesday and Thursday, and at 9am on Saturday. A studio-wide quiet time would miss her mornings and cut into her evenings, so she sets her own: 7am to 8pm, with Sundays off. A message outside them does not buzz; it waits, counted, for the next time she looks.
Two habits make it work. Write late if you must, but send or schedule it for the morning. And give emergencies their own path: if the 6am is canceled at 5am, someone calls, because a message she cannot see until 7 is not a message. Many late messages are really jobs nobody owns, and handing each one out with a name and a day takes them off everyone's evenings.
How do you stop answering the same question six times?
Write the answer down once, in a handbook the team can search, and answer questions with a link to it. When it has no answer, answer the question, then add it, so nobody has to ask again.
Your studio has a handbook already, even if it is a folder of old emails. Make it one place: the member policies people ask about, the opening and closing routine, what to do when something breaks, and who to call for what. What each role should see applies to documents as much as to numbers, so share each role its parts and keep pay and HR files with the people who should read them. Then a question in the channel becomes a link, and the answer is the same whoever is awake.
The next step is a handbook that answers back. Where your studio has switched Chat on in Xyzios, @Xyzi answers in a channel from what everyone there may see, such as the policies shared with them in Knowledge, and never with a member's details; anything meant for a member waits in Approvals for a person to approve.
Cancel up to 6 hours before class, or by 8pm the evening before for classes before 9am. One free pass every 90 days. Details in Member Policies.
Seen by 14 of 15 · 12 got it@Xyzi does the 8pm rule cover my Saturday 9am?
No. The 8pm rule is for classes that start before 9am, so your 9am keeps the six-hour window: members can cancel until 3am. That’s from Member Policies.
Where this lives
These habits work with any tool, or with paper. In Xyzios, the studio operating system, they live in Tasks and Chat, next to your numbers. Tasks is on at every studio, and anyone can give anyone a task, so a message that asks for something gets a name and a day. Chat is switched on studio by studio, when your studio is ready, with channels set up from your locations and roles.
There, a post marked Must read asks each person it is for to tap Got it, its author and the managers see “Seen by 14 of 15 · 12 got it” under it, and Remind reaches only those who haven't. @Xyzi in a channel answers from what everyone there may see, such as a handbook shared in Knowledge, and never gives member details. Each person can pause notifications or set their own notification hours; on iPhone, add Xyzios to the Home Screen first.
Nothing in Tasks or Chat reaches a member, and members never get push notifications or texts; anything a member receives still waits in Approvals until someone approves it. Sub requests and shift schedules stay where your schedule lives, not in Xyzios. It works with Mindbody and is an approved Mariana Tek integration, and the booking platform stays your system of record.
Start by counting every place your instructors look for studio messages today. Then the two-minute studio check shows which part of the studio needs you next, and the churn rate calculator shows what a year at your current churn keeps.