Customer SMS Notifications

Configure SMS notifications for customers to receive appointment reminders and updates via text message.

Environment tip: All examples use v3.onsched.com for production. Replace the host with api-stage.onsched.com when calling the staging environment.

What Are SMS Notifications?

SMS (text message) notifications allow customers to receive appointment alerts on their mobile phones. OnSched supports SMS alongside email notifications, giving customers choice in how they stay informed.

SMS notifications can be sent for:

  • New appointments – Booking confirmations
  • Appointment confirmations – When appointment is confirmed
  • Reminders – Upcoming appointment alerts
  • Rescheduling – When appointment time changes
  • Cancellations – When appointment is cancelled

How SMS Notifications Work

Notification Flow

  1. Appointment event occurs (booking, confirmation, reminder, etc.)
  2. Customer email follows the location customerNotificationType
  3. Customer SMS is sent when smsConsent is true and the customer has a phone number. The location type does not have to include SMS
  4. disableSmsNotifications on the company suppresses SMS. disableEmailNotifications suppresses email only
  5. The SMS provider delivers the message. If a customer text is not sent, one skip reason is recorded and the phone number is not written to that log

Public booking opt-in

The public booking form shows an optional, unchecked checkbox next to the phone field. The label names the location or company, states that consent is not a condition of booking, and includes STOP/HELP plus SMS Terms (https://onsched.com/terms) and Privacy Policy (https://onsched.com/privacy-policy) links. Customers can book without checking it. Email behavior does not change.

Send Customer.smsConsent: true on POST /v3/appointment or PUT /v3/appointment/{id}/book (and on POST / PUT /v3/customer) to persist consent. Omitting the field on create stores false. Omitting it on update leaves the stored value unchanged. false revokes consent.

SMS Provider

OnSched uses Twilio for SMS delivery. Twilio configuration is handled at the platform level (contact support for SMS gateway setup).

Configuring Customer SMS Preferences

Customer texts follow smsConsent plus a phone number. notificationType on the customer does not choose that text. Email still follows the location customerNotificationType.

Opt in

curl -X POST https://v3.onsched.com/v3/customer \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "firstName": "Jamie",
    "lastName": "Chen",
    "email": "[email protected]",
    "phone": "+15550123",
    "smsConsent": true
  }'

The customer receives appointment texts. Email is still sent when the location type includes email.

Opt out

curl -X PUT https://v3.onsched.com/v3/customer/CUSTOMER_ID \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "smsConsent": false
  }'

Further customer texts stop. Email is unchanged.

Phone Number Requirements

Format

Phone numbers must be:

  • E.164 format – International format with country code
  • Examples: +15550123 (US), +442071234567 (UK), +61291234567 (AU)

Validation

OnSched validates phone format but doesn't verify the number is active. Ensure:

  • Country code is included (+1 for US/Canada)
  • No spaces, dashes, or parentheses
  • Number is mobile (landlines can't receive SMS)

Missing Phone Numbers

If the customer opted in (smsConsent: true) but has no phone number:

  • SMS notifications are skipped
  • Email notifications still follow the location customerNotificationType
  • No error is thrown

Best practice: Validate phone number exists before setting SMS preferences.

Notification Cascade

Customer SMS

Customer appointment texts are sent when:

  1. smsConsent is true
  2. A phone number is stored on the customer
  3. The company has not disabled SMS

Location customerNotificationType does not gate that text. An EMAIL location still texts a customer who opted in.

Customer email still follows the location type: EMAIL and ALL send email; SMS and NONE do not.

Company and resource alerts still follow company.notificationType and resource.notificationType.

Example:

  • Location: customerNotificationType: EMAIL
  • Customer: smsConsent: true and a phone number
  • Customer receives the email and the text
  • The same customer with smsConsent: false receives the email only

Resource Notifications

Resources (staff) can also have notificationType for their own appointment alerts. This is separate from customer notifications:

  • Customer notifications: Alerts to customers about their appointments
  • Resource notifications: Alerts to staff about appointments assigned to them

SMS Message Content

Message Format

SMS notifications include:

  • Appointment details – Date, time, service
  • Location information – Where to go
  • Customer name – Confirmation recipient
  • Business name – Who the appointment is with

Example SMS:

OnSched Reminder: Your Haircut appointment with Style Salon is tomorrow at 2:00 PM. Location: 123 Main St. Questions? Call (555) 0100.

Message Customization

SMS content is generated automatically based on:

  • Notification type (booking, reminder, cancellation)
  • Appointment details
  • Location/company information

For custom messaging:

  • Use email templates (customizable via dashboard)
  • SMS templates follow standard format (contact support for custom SMS templates)

Character Limits

SMS messages are limited to 160 characters (standard SMS). Longer messages are split into multiple texts. Keep information concise:

  • Short business name
  • Essential details only
  • Link to confirmation page if more info needed

SMS Costs

Twilio Pricing

SMS delivery incurs per-message costs through Twilio:

  • US/Canada: ~$0.0075 per message
  • International: Varies by country (~$0.01-0.50 per message)

Costs are billed through your Twilio account (contact support for billing setup).

Cost Management

To control costs:

  • Offer email as default, SMS as opt-in
  • Send SMS only for critical notifications (reminders, day-of confirmations)
  • Use email for less time-sensitive messages
  • Monitor SMS volume monthly

Enabling SMS for Locations

Location customer notification type

customerNotificationType chooses the customer email channel. It does not turn customer SMS on or off. Customer SMS follows smsConsent and a phone number.

curl -X PUT https://v3.onsched.com/v3/location/LOCATION_ID \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "customerNotificationType": "EMAIL"
  }'

Customers who opt in still receive appointment texts at this location. Customers who do not opt in receive email only.

Company SMS switch

company.notificationType chooses alerts sent to the company contact. It does not choose customer texts.

Turn customer and other SMS off for the whole company with disableSmsNotifications. That flag does not disable email.

curl -X PUT https://v3.onsched.com/v3/company \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "disableSmsNotifications": false
  }'

Testing SMS

Test Messages

Before going live:

  1. Create a test customer with your phone number
  2. Book a test appointment with Customer.smsConsent: true
  3. Verify the SMS arrives
  4. Repeat with smsConsent omitted and confirm no customer text is sent
  5. Test booking, reminder, and cancellation

Troubleshooting Test Messages

If SMS doesn't arrive:

  • Check phone number format (E.164)
  • Confirm smsConsent is true
  • Confirm the company has not disabled SMS
  • Verify the SMS provider account is active (contact support)

Common Issues

SMS Not Sending

Check:

  1. Customer has a phone number in E.164 format
  2. smsConsent is true
  3. Company Disable SMS notifications is off
  4. The SMS provider account is configured
  5. Appointment creation didn't specify skip_notifications: true

SMS Sent to Wrong Number

Check:

  1. Customer record has correct phone number
  2. No typos in phone field
  3. Country code is correct

SMS Delayed

SMS delivery typically takes seconds but can be delayed:

  • Carrier congestion
  • International routing
  • Twilio processing time

Delays beyond 5 minutes warrant investigation (check Twilio logs).

SMS Content Wrong

SMS templates are auto-generated. For customization:

  • Contact support for custom SMS templates
  • Or skip SMS and send via your own SMS gateway using webhook triggers

Best Practices

Ask for SMS Permission

Don't assume customers want SMS:

  • Add checkbox during booking: "Send SMS reminders?"
  • Respect opt-out requests
  • Comply with SMS regulations (TCPA in US, GDPR in EU)

Validate Phone Numbers

Before collecting smsConsent: true:

  • Verify phone number is provided
  • Check format is E.164
  • Consider phone validation service for extra reliability

Offer Both Options

Let customers choose:

  • Email only
  • SMS only
  • Both
  • Neither

Flexibility improves customer satisfaction.

Monitor SMS Volume

Track SMS usage monthly:

  • How many customers opted in?
  • Average SMS sent per appointment?
  • Total monthly cost?

Adjust strategy if costs are high.

Use SMS for Time-Sensitive Alerts

SMS is best for:

  • Same-day reminders – Day-of appointment alerts
  • Last-minute changes – Reschedules, cancellations
  • Urgent updates – Staff sickness, location closures

Email is better for:

  • Confirmations (not urgent)
  • Receipts
  • Marketing campaigns

Compliance

TCPA (US)

Telephone Consumer Protection Act requires:

  • Opt-in consent – Customers must agree to receive SMS
  • Opt-out mechanism – Provide way to stop messages (e.g., "Reply STOP to unsubscribe")
  • Business hours – Don't send messages late at night

GDPR (EU)

General Data Protection Regulation requires:

  • Consent – Explicit permission to send SMS
  • Purpose limitation – Only send appointment-related messages
  • Right to withdraw – Easy opt-out process

CAN-SPAM / CASL

Similar requirements in other jurisdictions. Always:

  • Get consent before sending
  • Provide opt-out
  • Honor unsubscribe requests immediately

Opt-Out Handling

Customer Requests Opt-Out

If customer replies "STOP" to SMS:

  • Twilio automatically blocks future messages to that number
  • Set smsConsent to false on the customer
  • Respect that opt-out across later appointments

Unsubscribe Process

  1. Customer texts "STOP" to SMS number
  2. Twilio blocks number
  3. Update customer in OnSched:
curl -X PUT https://v3.onsched.com/v3/customer/CUSTOMER_ID \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "smsConsent": false
  }'
  1. Confirm with the customer by email

Alternative SMS Solutions

Using Your Own SMS Gateway

If you prefer to handle SMS yourself:

  1. Leave smsConsent false, or set disableSmsNotifications on the company
  2. Configure webhooks for appointment events
  3. Your system receives webhook
  4. Send SMS via your gateway (Twilio, Plivo, AWS SNS, etc.)

This gives full control over:

  • SMS content
  • Timing
  • Cost management
  • Compliance tracking

Common Questions

Can customers reply to SMS?

Not directly to OnSched SMS. Messages are one-way notifications. To enable replies:

  • Use your own SMS gateway
  • Configure two-way SMS in Twilio (custom setup)

What if customer changes phone number?

Update customer record:

curl -X PUT https://v3.onsched.com/v3/customer/CUSTOMER_ID \
  -d '{"phone": "+15550NEW"}'

Future SMS will use new number.

Can I send custom SMS outside of appointments?

OnSched SMS is triggered by appointment events only. For marketing SMS:

  • Use your own SMS gateway
  • Export customer list and send via Twilio directly
  • Use marketing automation tools (Mailchimp, HubSpot)

How do I know if SMS was delivered?

Check Twilio logs:

  • Login to Twilio dashboard
  • View message logs
  • Check delivery status (sent, delivered, failed, undelivered)

Can I preview SMS before they send?

SMS templates are fixed per notification type. To preview:

  • Send test appointment to yourself
  • Review actual SMS received
  • Contact support for template customization

Related Documentation

SMS notifications reduce no-shows and improve customer experience. Configure thoughtfully, respect preferences, and comply with regulations to make SMS a valuable channel for your business.


Did this page help you?