A spin class has twenty bikes. At 6 AM, three of them are empty because three people forgot. Meanwhile, five people sit on a waitlist who would have loved the spots. That gap is the reason studios and gyms ask booking software for text messages, and it's why your roadmap probably has an item called "SMS notifications."
This post is for the product team at a class-booking or membership platform. We'll cover the texts worth sending, how a waitlist text should work, consent at signup, STOP handling, quiet hours and keeping each studio's sender separate. The studios and numbers below are made-up examples.
The texts that earn their place
Booking software sends a lot of email. Most of it can stay email. Reserve text messages for moments where timing changes the outcome.
| Event | Why it works as a text | Notes |
|---|---|---|
| Booking confirmation | Reassurance, with the time and place | Short, one segment if you can |
| Class reminder | Fewer forgotten sessions | Send a few hours ahead, not days |
| Waitlist spot opened | A clock is ticking | Include how long they have to claim it |
| Class canceled or moved | Needs to be seen before they leave home | Highest priority |
| Membership payment failed | Time-sensitive, but keep wording neutral | Link to a page, no balances in the text |
| Membership expiring | Useful nudge | Needs the right consent purpose |
We won't quote a no-show reduction figure here. Reminders generally help, and the real effect depends on the studio, so measure it on your own data after a pilot.
Consent at the booking form
The person has to agree to get texts, and the agreement should be specific, unchecked by default and separate from accepting your general terms. A workable booking-form pattern:
- A phone number field on the booking form, right next to the name and email fields.
- An unchecked box with plain wording: the studio's name, what kinds of texts (booking confirmations, reminders and waitlist alerts), that message and data rates may apply, roughly how often, and that replying STOP ends texts.
- Links to the privacy policy and terms.
- A stored record of the exact wording and the time they agreed.
Point 4 is yours to keep. When you set consent_attested on a send, Ready records your attestation of who sent, to how many and when. It isn't a per-contact consent record and doesn't store the member's opt-in time or wording, so your database has to. Our post on a consent record schema for developers lays out the fields.
Keep the purposes apart. Agreeing to class reminders isn't agreeing to a "20 percent off annual membership" campaign. If a studio wants to run promotions, collect that agreement separately and tag the message with its purpose in your system.
From January 20, 2027 (UTC), an API send without consent_attested is refused with a 403. Until then it still goes out with a warning and leaves no attestation.
A waitlist text that works
The waitlist is where texting pays off most, and where logic bugs hurt most. Think through the flow before you code it.
- A spot opens when someone cancels.
- Your system picks the next person on the waitlist and sends one text: "A spot opened in Saturday 9 AM Yoga at Example Studio. Reply YES within 15 minutes to claim it. Reply STOP to opt out."
- Their reply arrives at your webhook. If it's YES and the spot is still free, book it. If time runs out, move to the next person.
Two cautions. First, make the send idempotent. If your job retries after a timeout, the same person shouldn't get two "a spot opened" texts. Send an Idempotency-Key header, one UUID per message, reused on every retry. See idempotency for duplicate texts. Second, replies are data you receive, not commands you trust blindly. Check the sender's number against the waitlist entry before you book anything, and treat a surprising reply as a message for a human. Our post on receiving inbound texts with webhooks covers the receiving side.
The request itself is plain, with a made-up number:
POST /v1/messages
X-API-Key: <key>
Idempotency-Key: <one UUID per message>
{"to": "+12125550199", "body": "A spot opened in Sat 9 AM Yoga at Example Studio. Reply YES in 15 min to claim it. Reply STOP to opt out.", "consent_attested": true} Reference docs: https://docs.tryready.com/api/messages.
Reminders and scheduling
For a reminder a few hours ahead, you have two options. Run your own scheduler and call the send endpoint at the right moment, or use POST /sms/schedule with message, send_at and a contact_id or to. Nothing is charged until a scheduled text sends. It schedules one text to one contact, and lists have no scheduling endpoint, so a class of twenty means twenty scheduled texts. If a member cancels, your side needs to remove or ignore the reminder. Docs: https://docs.tryready.com/api/scheduled-messages.
Keep reminder copy short. A plain segment is 160 characters, 153 per part when longer, and an emoji drops that to 70. The flexed-bicep emoji that looks fun in a design review can triple your segment count. Our segment counter post has a check you can drop in.
STOP and member experience
When a member replies STOP, UNSUBSCRIBE or something clear like "please stop texting me," Ready honors it and blocks further texts to that number. Your product should reflect it.
- Read opt-outs with
GET /v1/opt-outs, and check one number withGET /v1/opt-outs/:phone. - Show "texts off" on the member profile so front-desk staff don't promise a text that won't arrive.
- Move that member's reminders to email or push automatically.
A STOP always blocks the number in the sub-account that received it. Whether it also blocks the parent and other sub-accounts is decided by Ready, so check the per-number endpoint for the rest. See handling SMS opt-outs.
Quiet hours matter for early classes
Early-morning studios are the odd case. A reminder at 5 AM for a 6 AM class sits right in the hours texting rules protect. Ready enforces quiet hours based on the recipient's area. A campaign or automation waits up to 24 hours for the window. An API text is held only if the window opens within 6 hours, and otherwise isn't sent. Send reminders for early classes the evening before, and have your code handle the refusal gracefully. We explain the response in handling the quiet hours 409.
A reply to a member who texted the studio in the last 24 hours can go out at any hour, so "reply YES to claim" flows work even for a response that lands late.
A sender for every studio
Each studio should text from its own number with its own carrier registration, so one studio's mistakes don't hurt another's deliverability. Ready's sub-accounts do that: a number and a 10DLC registration for each customer, created through the API. Registration needs an EIN, and most approvals take 2 to 7 days. Plan the onboarding step for it, and read SMS API for vertical SaaS onboarding for the order of steps.
FAQ
Should we text from a shared number? Not for studios. Their members expect to recognize the sender, and shared senders mix reputations.
Can reminders include a cancellation link? Yes, keep it to one link.
What about payment text content? Keep amounts and card details out of texts. Send a neutral line and a link to a logged-in page.
The practical takeaway
Start with two texts: the booking confirmation and the waitlist alert. Store consent, retry safely, and give each studio its own sender. When you're ready to test the sends, sign up and try a test key first.