Push Notifications for Studios: What to Send and When

Send three kinds of push notifications, in this order of priority: booking-critical alerts (waitlist spots, cancellations, class changes), habit nudges tied to a member's own schedule, and opt-in offers. We call it the Booked, Nudged, Offered ladder. Cap non-transactional pushes at two per week, and never send an offer to someone who has not explicitly opted in.

What is the Booked, Nudged, Offered ladder?

It is a priority order for every push you send: protect the booking first, prompt the habit second, and pitch an offer last, if ever.

Booked covers anything that changes whether a member ends up in the room: a cancellation, a sub, a room swap, a waitlist spot. Nudged covers messages built on the member's own behavior, such as their usual class, their pack balance or their streak. Offered covers workshops, promos and events.

The rule is that a lower rung never crowds out a higher one. If a member turns off notifications because of a Friday flash sale, your 9:40 p.m. alert that Saturday's 7 a.m. class is canceled never reaches them. A promo push doesn't only risk being ignored. It also puts your operational alerts at risk.

Which booking alerts should go out as push, not email?

Push anything time-bound inside the next 24 hours: class cancellations, instructor substitutions, room changes, and late-cancel window reminders. Everything else can wait for email.

Here are the timings we would set at any front desk:

• Cancellation: push the moment it is confirmed. If the class starts in under 3 hours, send an SMS as well, because some members are already in the car.
• Instructor sub: push to everyone booked, as soon as the sub is confirmed. Members who book for a specific instructor would rather hear now than find out at check-in.
• Late-cancel reminder: send it 1 hour before the window closes. With a 12-hour policy and a 7 a.m. class, the window closes at 7 p.m. the night before, so the push goes out at 6 p.m. That one message heads off many of the late-cancel fee disputes your desk deals with on Monday mornings.
• Booking confirmations: do not push these. The member is looking at the confirmation screen already. Use email and the in-app calendar.

When should a studio ask members to turn on notifications?

Ask after a member's first booking, not at app install. The booking gives the request an obvious reason: you will hear if this class changes.

Since Android 13, posting notifications has needed a runtime permission that the app must request. Google's guidance is to let users get familiar with the app first and to trigger the prompt from a user action. iOS has always required the member to grant permission.

The procedure:

1. Member books their first class.
2. The confirmation screen shows your own soft ask: "Want a heads-up if this class is canceled or a waitlist spot opens?" with Yes and Not now.
3. Only Yes triggers the system dialog.
4. Not now members see the soft ask again after their third booking, and not before.

When new members download the app at the desk, have them book their next class right there. Don't tap Allow on their phone for them. Booking at the counter triggers the ask in context, and the member makes the choice themselves.

What habit nudges actually bring members back?

Nudges that reference the member's own pattern work: their usual Tuesday class, their pack balance, their streak. Generic motivation quotes get ignored or silenced.

Habit nudges with real triggers:

• Usual slot open: a member has booked Tuesday 6:15 p.m. spin in 3 of the last 4 weeks but hasn't booked by Monday noon. Push: "Tuesday 6:15 Ride: 4 bikes left."
• Pack low: fire at 2 credits remaining, not 0. At 0, the member has already left the habit loop.
• Credits expiring: 7 days before expiry, with the exact count: "3 credits expire Nov 3."
• Slipping: a member who averaged two visits a week has gone 14 days without one. Send one push. At 21 days, stop automating and have a staff member text them personally. The signals for spotting at-risk members are worth setting up before you write these messages.
• Milestones: the 50th class, sent the morning after, not mid-class.

How do you handle waitlist pushes without starting a stampede?

Offer the spot to one person at a time with a short claim window, or auto-enroll them. Blasting the whole waitlist leaves most of the list disappointed.

Picture seven people on the Saturday 9 a.m. reformer waitlist. A spot opens at 8:10 and you push to all seven. Six people tap it, one gets the bed, and five open the app to a "class full" screen. You have annoyed six members to fill one spot.

Use two modes:

• More than 2 hours out: auto-enroll the first person and push "You're in: Saturday 9 a.m. Reformer."
• Inside 2 hours: switch to claim mode. The first person gets a 15-minute window, then the spot moves to the next person.

Waive the late-cancel fee for anyone promoted off the waitlist within the late-cancel window. Charging someone a fee for a class they never chose to be in is a front-desk argument you will lose.

Are promotional pushes allowed in a studio app?

Yes, but only with explicit in-app consent and an easy opt-out. Apple's App Store review guidelines require both, and abuse risks revocation.

Guideline 4.5.4 states that push notifications "should not be used for promotions or direct marketing purposes unless customers have explicitly opted in" through consent language in the app's UI, with a way to opt out. Apple adds that abuse "may result in revocation of your privileges."

If you run a branded app, check that it has a separate Offers and events toggle, off by default, with a sentence like "Workshops, challenges and member offers, about twice a month." If the setting doesn't exist, keep promos in email.

For members who opt in, target the offer. Send an inversions workshop to members who attended three or more vinyasa classes last month, not the whole list. A challenge launch such as a 30-day yoga challenge suits push because it has a start date. A 20%-off push sent to every member does not.

How many push notifications per week is too many?

For non-transactional pushes, two per week is a sensible ceiling. Transactional alerts do not count, because members asked for them by booking.

The problem is usually not one bad campaign. It is overlap between campaigns. On a Monday, marketing schedules the workshop promo, the system fires a pack-low nudge, and the slipping-member trigger hits the same person. That's three pushes before lunch.

Set the cap per member, across every campaign:

• At most one Nudged or Offered push per member per day.
• At most two per member per week.
• When two compete, the higher rung of the ladder wins and the other is dropped, not queued.

When should you use SMS or email instead of push?

Use SMS when missing the message costs the member a class or a fee. Use email when the content needs more than two lines.

Push only reaches members who installed your app and allowed notifications. Pew Research Center finds that about nine in ten US adults own a smartphone, but owning a phone is not the same as having your app with alerts switched on. Your real push reach is the share of active members with permission granted. Check that number before you rely on push for anything urgent.

Payment issues need special care. Apple's guideline also says pushes should not carry sensitive personal or confidential information, so "Your card was declined" should never appear on a lock screen. Send "Action needed on your account" and put the details in email. The same reasoning applies to recovering abandoned checkouts: keep the specifics behind a login.

For longer sequences such as onboarding or win-back series, see how studios handle automated email for member communication.

What should a studio push notification actually say?

Lead with the class, time and change in under 60 characters. The member should know what happened without opening the app.

Lock screens cut text short, so the first few words carry the message. Compare:

• Weak: "Hey there, we have an important update about your upcoming class."
• Strong: "Sat 7 a.m. HIIT canceled. Credit returned."

The weak version makes the member open the app to find out what happened. The strong version answers the question and confirms that their credit came back, which heads off the "did I lose my credit?" call to your desk.

Further rules:

• Use the class name members see on the schedule, not your internal code.
• Include the instructor's first name only when the instructor is the news.
• One push, one action. Don't attach a promo to a cancellation.

How do you measure whether pushes are working?

Measure bookings within a set window after the push, not opens. A waitlist push should convert in minutes; a habit nudge within 48 hours.

Open rates mislead for push because a good Booked alert gets read on the lock screen and never opened. Track these instead:

• Waitlist claims within the 15-minute window. If fewer than half of offers get claimed, check your send timing.
• Bookings within 48 hours of a usual-slot nudge, compared with a holdout. Hold back 10% of eligible members for a month and compare their booking rate with the group that got the nudge.
• Permission rate among active members, weekly. If it drops after a campaign, that campaign cost you reach for every alert that follows.

The permission rate is the number most studios forget to track, and it's the one that shows when the Offered rung has started damaging the Booked rung.