Mindbody SMS marketing for studios: reminders and consent

Which texts are worth automating for a studio or salon?

Five messages cover most of the value: a booking confirmation, a reminder before the class or appointment, a follow-up after a no-show or late cancel, a notice when a waitlist spot opens, and a birthday or win-back offer.

The kind of message decides the consent check. Confirmations, reminders and waitlist notices are service messages about something the client already booked. Birthday and win-back texts are marketing, even when they are friendly.

Message	Mindbody/Booker event	Consent type	Timing note
Booking confirmation	New class or appointment booking	Schedule/service texts	Send within minutes of booking
Reminder	Upcoming class or appointment	Schedule/service texts	Land before your late-cancel cutoff; evening before for early classes
Waitlist spot opened	Client moved from waitlist to booked	Schedule/service texts	Immediately; include how to cancel
No-show or late-cancel follow-up	Visit marked no-show or late-cancelled	Schedule/service texts; promotional if it contains an offer	Same day, not in the middle of the night; depends on attendance being marked
Birthday offer	Client’s birth date field	Promotional texts	Morning of, or a few days earlier; only clients with a birth date on file

Some texts are better left to a person: long promotional blasts, and anything that needs a reply, such as an injury or treatment question at a med-spa.

How do you send texts from Mindbody or Booker by hand today?

In Mindbody, start with the built-in text tools. The help articles ‘How do I send text messages to clients’ and ‘Enabling text message opt-ins’ describe how to send texts and how opt-ins work. Follow the current steps in those articles, because menus change, and check the text permission options on the client profile so you know who has agreed to receive texts.

In Booker, check the reminder and messaging options in your Booker admin or Booker’s support documentation. Confirm what is available on your plan at the time you read it.

For a one-off message to a group, the manual route is to export a client list, filter it by consent, and paste the numbers into a texting tool. That list is out of date the next day: new bookings, cancellations and opt-outs keep happening.

Where does the manual approach break?

The built-in options are built around general messages. A text triggered by a visit status, such as a no-show or late cancel, or by a waitlist move, is the kind of message that usually needs a connected service.

The common breaks look like this:

• Two places hold opt-outs. A client who replies STOP to a separate texting number stops getting texts from that number, but the Mindbody profile still shows them as opted in. Any other tool or manual send ignores the STOP unless it is written back to the profile.
• Reminder timing does not match the cancel window. If you charge for a late cancel inside 12 hours and the reminder goes out 2 hours before class, the text sets the client up for a fee instead of preventing a no-show. Set the reminder as ‘cutoff plus a buffer’, not a fixed number of hours before.
• Clients get two reminders. If Mindbody’s own reminders stay on and a second system also texts, clients get two. Decide which system owns reminders before launch and turn the other one off.
• Consent exists on paper but not in the data. A client ticks a box on a front-desk tablet, but the box never reaches the profile, so the text tool has no record of it.
• Birthdays are missing. Clients who joined through a booking widget may have no birth date, so the birthday list is smaller than the client list.
• Time zones. Multi-location studios need texts sent by the client’s local time, not the server’s. A 6am class reminder belongs the evening before, not at 5am.

Do you need consent to text clients, and how do you handle opt-out?

Short answer: yes. In the US, the TCPA requires prior express consent for automated texts and prior express written consent for marketing texts sent with automated technology. Canada (CASL) and the UK (PECR) follow similar logic. This is general information, not legal advice, so check with counsel for your state and country.

A practical consent setup:

1. Add a separate texts checkbox on the intake form and the booking flow. Use plain language: what messages they will get, how often, that message and data rates may apply, and how to stop.
2. Keep the wording and a timestamp for each consent, so you can show what the client agreed to and when.
3. Map consent to the right permission. Mindbody’s Public API client record separates account, schedule and promotional text permissions (SendAccountTexts, SendScheduleTexts, SendPromotionalTexts). A reminder should check the schedule permission. A birthday offer is marketing and should check the promotional one. Many studios only ever look at one checkbox.
4. Honor opt-outs right away. Treat STOP, HELP and similar keywords as final, and write each opt-out back to the client record. Honor an opt-out given in person or by email too.
5. Respect quiet hours by the recipient’s local time. Roughly 8am to 9pm is commonly treated as a safe window in the US, and some states are stricter.
6. Register before you send. US business texting over standard local numbers requires brand and campaign registration (A2P 10DLC). Carriers can filter or block unregistered traffic, and approval is not instant, so start early.
7. Test with two staff phones: one that has opted in and one that has opted out. Check that only the first receives each message type.

How do you automate it with Pandaflow?

Pandaflow connects Mindbody (or Booker) to Twilio for texts, and to HubSpot, Klaviyo, Mailchimp or ActiveCampaign for email follow-up. See everything Pandaflow connects.

The setup has four steps:

1. Start free and connect Mindbody or Booker, then Twilio.
2. Describe what you want in plain English. For example: ‘text clients 3 hours before class unless they have opted out of schedule texts, and send a friendly note to anyone marked no-show that evening.’ There are no workflows, templates or settings to build.
3. Review a few records. Check that a client with schedule consent gets the reminder, that a client without it does not, and that the timing sits inside your cancel window. Send test texts to staff phones.
4. Go live.

Once it runs, the owner sees texts going out against real bookings, opt-outs reflected on the client record, and Pandaflow repairing the sync when something changes on either side. Optional Slack alerts tell you when a send fails.

Clients without text consent can still get the reminder by email through HubSpot or one of the email tools. Check pricing for plans: Lite $79, Silver $299 and Gold $499 a month. You can deploy in our cloud or yours.

This is an illustrative setup, not a customer story. A two-location pilates studio sends a reminder the evening before early classes, a no-show note the same evening, a waitlist text when a spot opens, and a birthday text only to clients with promotional consent. Each location’s messages follow that location’s local time.

What can go wrong?

• Texts before consent is recorded, or before 10DLC approval. Confirm both before the first live send.
• Duplicate reminders. Pick one system to own reminders and turn the other off.
• A late no-show text. The text can only fire once attendance is marked. If front-desk staff close out rosters late, the text will be late too.
• Shared family numbers. One STOP covers the number, not the person. A household phone may need a conversation, not just an opt-out.
• Old lists. Exports go stale. Use live records wherever you can.

More how-tos for studios are in the guides.