Acuity SMS Reminders: How to Send Texts Clients Can Reply To
Short answer: Acuity Scheduling can send one SMS reminder per appointment on eligible paid plans, but a client reply receives an automated response instead of reaching your team. To handle confirmations, reschedules, cancellations, and late-arrival messages by text, connect Acuity to a two-way SMS workflow such as Aculio.
How do Acuity SMS reminders work?
Acuity Scheduling sends a scheduled text reminder to the phone number stored in an appointment. According to Acuity's current documentation, text reminders are available on Standard or Growing and Premium or Powerhouse plans, are not available during free trials, and require the client to opt in for that appointment.
You can choose the reminder timing from 15 minutes to 14 days before the appointment. Acuity sends one text reminder per appointment, and the default sender number is automatically assigned. Confirmation messages sent immediately after booking are emails, not text messages.
That setup is useful when your business only needs a scheduled nudge. It becomes limiting when the message needs to start a conversation or when one reminder is not enough to protect a busy class or appointment calendar.
What are the limits of native Acuity SMS reminders?
Native Acuity SMS covers the basic reminder use case, but it does not provide a complete two-way messaging workflow.
| Capability | Native Acuity SMS | Acuity plus Aculio |
|---|---|---|
| Reminders per appointment | One scheduled text | Configurable reminder sequence |
| Message length | Up to 300 plain-text characters | Short, multi-step messages with workflow context |
| Client replies | Automated response directs clients elsewhere | Replies can route to automation or an inbox |
| Booking confirmation SMS | Not native; confirmation is sent by email | Can trigger after a new booking |
| Class waitlist alerts | Not supported for group classes | Seat-open alerts can trigger a waitlist flow |
| Consent and opt-out handling | Native Acuity opt-in and STOP handling | Workflow-level consent, suppression, and delivery records |
Acuity also limits a plain-text reminder to 300 characters. The limit includes inserted fields such as the business name and appointment type, and special characters or emojis may count as more than one character. If the message exceeds the limit, it may be cut off.
Most importantly, replies are not a live conversation. Acuity says a client who responds receives an automated message suggesting they contact the business by another method. If a client texts that they are running late or need to move an appointment, your team will not receive that reply in Acuity as an actionable conversation.
Why two-way SMS matters for appointment and class businesses
Two-way SMS turns a reminder into an operational workflow. A client can take the next step from the same message, while your scheduling system remains the source of truth.
- Confirmations: a client can reply YES and the workflow can record the response.
- Rescheduling: a client can ask to move the appointment and receive the correct booking path.
- Cancellations: a cancellation can suppress pending reminders and open the slot for another client.
- Late arrivals: a RUNNING LATE reply can notify staff without requiring a phone call.
- Waitlist backfill: a freed class seat can trigger an SMS alert to eligible waitlisted clients.
For studios, workshops, and instructors, the last point is especially important. A cancellation shortly before class can leave an empty seat even though other clients wanted to attend. Aculio connects the Acuity group class waitlist flow to SMS so the opening can be offered quickly.
How to set up two-way SMS with Acuity
A reliable setup separates the booking event, the messaging rules, and the reply handling. Use this sequence when adding SMS automation around an existing Acuity calendar.
- Connect your Acuity account. Authorize Aculio through the onboarding flow and select the calendars or appointment types that need automation.
- Confirm phone and consent fields. Capture a valid mobile number and obtain the required permission before sending appointment or waitlist texts. A phone number alone is not consent.
- Define the event triggers. Choose whether a new booking, reschedule, cancellation, reminder window, or open class seat should create a message.
- Write one clear action per message. Include the business name, appointment or class, local date and time, and one next step such as replying YES or using a reschedule link.
- Map reply handling. Decide what YES, CANCEL, HELP, and RUNNING LATE should do. Route exceptions to a person instead of promising an automated action the system cannot complete.
- Suppress stale messages. When an appointment is moved or canceled, cancel reminders based on the old time and rebuild the schedule from the current appointment record.
- Test the full lifecycle. Test booking, reminder delivery, replies, rescheduling, cancellation, opt-out, and class waitlist backfill with a test client before enabling the workflow for everyone.
For a broader comparison of native SMS, Twilio-style connectors, and a dedicated automation layer, read the Acuity Scheduling SMS integration guide.
How to write an Acuity SMS reminder clients can act on
The best reminder is specific, short, and easy to answer. Use the 300-character native limit as a useful constraint even when an external workflow gives you more room.
- Lead with the appointment or class name and the local date and time.
- Identify the business so an automatically assigned sender number is recognizable.
- Give one primary action, not a list of competing instructions.
- Add the address, access note, or meeting link when it is necessary to attend.
- Include a reschedule path so clients do not ignore a conflict.
- Keep private, medical, and payment details out of routine SMS.
Example: Hi Maya, your Aculio Yoga class is tomorrow at 6:00 PM. Reply YES to confirm, CANCEL to release your spot, or use this link to reschedule: [booking link]
Do not tell clients to reply if nobody is monitoring the sender. Two-way messaging only helps when inbound replies are received, stored, and connected to an action or a person.
Keep Acuity SMS compliant
Before enabling any external SMS workflow, document the consent source, message purpose, opt-out behavior, and retention of delivery records. Honor STOP requests promptly and suppress later messages for an opted-out client.
Acuity's documentation says clients can book without opting in, and the opt-in applies separately to each appointment. Your integration should preserve that distinction rather than treating a phone number or an earlier booking as blanket permission. Review the official Acuity text reminder documentation and the Twilio Messaging Policy before launch.
Reduce no-shows with reminders that can respond
Native Acuity SMS reminders are a solid baseline: one scheduled text, a clear timing control, and built-in opt-in handling. They are not a two-way client communication system. If your team needs confirmations, reschedule requests, cancellation-driven waitlist alerts, or multiple reminder stages, add a workflow that can receive replies and keep every message tied to the current Acuity appointment.
Aculio adds reply-aware SMS automation around Acuity Scheduling, including appointment confirmations, reminders, no-show prevention, and group-class waitlist alerts. Start with the Acuity SMS automation guide or connect your account through Aculio onboarding.
