Acuity Scheduling SMS Integration: Twilio, Webhooks, and Automated Texts

Acuity Scheduling SMS integration connects booking events to text messages through native Acuity SMS, Zapier, Twilio, or a dedicated automation layer. Native Acuity is the simplest option for one-way reminders, while Aculio adds reply-aware workflows, class waitlist alerts, and operational logs for teams that need more than a scheduled nudge. The right setup depends on the message you need to send. A reminder before an appointment can stay inside Acuity. A confirmation immediately after booking, a text triggered by a cancellation, or a message that reacts to a client reply usually needs an integration that can listen for Acuity events and route them to SMS. ## What does an Acuity Scheduling SMS integration do? An Acuity Scheduling SMS integration passes scheduling information into a text-message workflow. A new booking, reschedule, cancellation, appointment start, or completed order can become the trigger for a message to a client, staff member, or waitlist. There are three common ways to build that connection: - **Native Acuity SMS:** Acuity sends one text reminder per appointment on eligible plans. It is the shortest path for standard reminders. - **No-code connector:** Zapier or a similar platform listens for an Acuity trigger and sends an SMS action. This is useful for simple, low-volume workflows. - **Acuity plus an automation platform:** Aculio receives booking signals, runs reminder and no-show sequences, sends class waitlist alerts, and tracks replies in the operational workflow. The key distinction is whether the integration only sends a message or also understands what happens next. A one-way text can remind someone about an appointment. A reply-aware workflow can record YES, CANCEL, or RUNNING LATE, suppress a message that is no longer relevant, and alert the team when human help is needed. ## Native Acuity SMS vs. Twilio vs. Aculio The best option depends on how much control your business needs over triggers, timing, replies, and records. Native Acuity remains a good fit if your only requirement is a scheduled reminder. According to Acuity's current documentation, text reminders are available on Standard and higher plans, clients must opt in, and native reminders are limited to one message per appointment. [Read Acuity's text reminder documentation](https://help.acuityscheduling.com/hc/en-us/articles/16676915777293-Sending-appointment-reminders-via-text) before enabling the feature. ## How do Acuity webhooks power SMS automation? Webhooks are the event layer behind a responsive Acuity Scheduling SMS integration. Acuity sends a notification to your endpoint when a supported scheduling event occurs. Your integration then retrieves the appointment details, checks the relevant rules, and sends the correct message. Acuity's developer documentation lists these dynamic webhook events: - `appointment.scheduled` - `appointment.rescheduled` - `appointment.canceled` - `appointment.changed` - `order.completed` The developer API currently allows a maximum of 25 webhooks per Acuity account, and the endpoint must use port 443 or 80. [See the official Dynamic Webhooks reference](https://developers.acuityscheduling.com/page/webhooks-webhooks-webhooks). Acuity also states that webhooks are a one-way stream of information, while its API is used for a back-and-forth connection with custom software. [Review Acuity's webhooks and API guidance](https://help.acuityscheduling.com/hc/en-us/articles/16676949253389-Using-custom-CSS-webhooks-and-APIs). That limit matters when a studio creates separate subscriptions for every appointment type and downstream tool. A centralized integration can receive the supported events once, identify the calendar or appointment type, and apply the correct SMS rule without asking the account owner to maintain a growing list of webhook targets. Aculio uses this event-driven approach for appointment reminders, waitlist activity, and reply-aware follow-ups. ## How to set up an Acuity Scheduling SMS integration Use this sequence to choose the lightest setup that meets your communication needs. ### 1. Define the message and trigger Write down what should happen and when. Examples include a reminder 24 hours before an appointment, a final reminder two hours before class, a message after a cancellation, or an alert when a group-class seat opens. ### 2. Confirm consent and eligibility Only send SMS to clients who have opted in for the appointment or workflow. Keep opt-out handling visible and honor STOP requests immediately. Aculio's [SMS opt-in guide](https://www.aculio.com/blog/acuity-sms-opt-in-compliance) covers consent language, suppression, and operational records. ### 3. Choose native SMS, a connector, or a dedicated layer Enable native Acuity text reminders when one scheduled, one-way reminder is enough. Choose Zapier or a Twilio workflow when you need a small number of event-to-message automations and can maintain them. Choose Aculio when your team needs multiple reminder stages, two-way reply handling, class waitlist alerts, or a single operational view. ### 4. Map appointment data into the message At minimum, include the client's name, business name, appointment type, local date and time, and a clear next step. Add a rescheduling link when appropriate. Keep the copy short enough to scan quickly, and avoid sending a link without explaining where it leads. ### 5. Test every lifecycle event Create a test appointment and verify the full path: booking, reminder scheduling, rescheduling, cancellation, reply handling, and delivery logging. Test an opted-out number separately to confirm it is suppressed. For a group class, fill the class, join the waitlist, cancel the booking, and verify that the seat-open alert reaches the intended clients. ## Common Acuity SMS integration mistakes ### Treating a webhook as a delivered message A webhook only tells your system that an event occurred. It does not prove that the client received an SMS. Keep event logs and message delivery status separate so the team can distinguish an Acuity event, a queued message, and a delivered message. ### Using separate webhooks for every small variation Creating one subscription per appointment type can consume the account's webhook allowance quickly. A central event router can receive supported events and branch on the appointment type, calendar, or status. ### Assuming native SMS is two-way Native Acuity text reminders are designed as notifications. If clients need to confirm, cancel, or report that they are running late by text, use a workflow that receives and interprets replies. [Aculio's SMS automation page](https://www.aculio.com/acuity-sms-automation) explains the reply-aware approach. ### Forgetting group classes Native Acuity waitlists are built for one-on-one appointment availability, not true group-class seat backfill. If your studio runs yoga, fitness, workshops, or other capacity-based sessions, connect the waitlist flow to a system that can alert clients as soon as a seat reopens. See the [Acuity group class waitlist guide](https://www.aculio.com/blog/does-acuity-scheduling-have-a-waitlist). ## When should you use Aculio with Acuity? Use Aculio when SMS is part of an operating process rather than a single reminder. Aculio connects Acuity booking events to confirmation messages, day-before and two-hour reminders, cancellation handling, group-class waitlist alerts, and feedback requests. Replies can be captured and used to suppress irrelevant follow-ups or surface a task for the operator. This is especially useful for studios and appointment businesses that have several calendars, recurring classes, frequent late cancellations, or staff who need one place to see what happened. Acuity remains the booking system. Aculio adds the event routing, messaging logic, and workflow visibility around it. Ready to connect your calendar? Start the [Aculio onboarding flow](https://www.aculio.com/onboarding) and review [Aculio pricing](https://www.aculio.com/pricing) for a plan that fits your message volume. ## Frequently asked questions ### Does Acuity Scheduling integrate with SMS? Yes. Acuity offers native text reminders on eligible plans, and external tools can connect Acuity events to SMS actions. Aculio adds multi-step reminders, reply-aware handling, and class waitlist alerts. ### Can I connect Acuity Scheduling to Twilio? Yes. A Twilio workflow can receive Acuity events through webhooks or a connector and send messages based on those events. You need to manage authentication, message templates, consent, replies, retries, and delivery records yourself unless your integration layer handles them. ### Does Acuity send an SMS immediately after a client books? Native Acuity sends booking confirmations by email by default. An external SMS integration can send a booking confirmation after receiving an appointment-scheduled event. ### How many Acuity webhooks can I create? Acuity's developer documentation currently states that a maximum of 25 webhooks can be created per account. A centralized event router helps avoid using one webhook subscription for every small workflow variation. ### Can Acuity SMS replies trigger automations? Native Acuity reminders are one-way notifications. To act on replies such as YES, CANCEL, or RUNNING LATE, use a two-way SMS workflow that receives replies and connects them to the appointment record. ## Conclusion An Acuity Scheduling SMS integration can be as simple as native reminders or as flexible as a webhook-driven messaging system. Start with the trigger, confirm consent, and choose the smallest tool that supports the workflow you actually need. If your business depends on reply handling, group-class waitlists, multi-stage reminders, or clear operator logs, Aculio adds those layers around your existing Acuity calendar.