SMS channel
Allow guests to interact with SmartBot through text messaging. When guests send an SMS to your center's SmartBot phone number, the system identifies the organization and center, creates a conversation session, and guides the guest through booking, FAQs, or other supported workflows β all within standard SMS constraints.
Audience: Administrators and staff understanding how the SmartBot SMS channel works.
Before you begin
- Your organization must have SmartBot provisioned with the SMS channel enabled for the center.
- A dedicated phone number must be provisioned for the center. See Configure the SMS channel.
SMS Bot deployment scenarios
The SMS Bot can be deployed in three scenarios. They are not mutually exclusive β many businesses run a combination.
| Scenario | Trigger | Setup required |
|---|---|---|
| A β Missed-call SMS | Guest calls your business; if the call is unanswered (out-of-hours or busy staff), an automatic SMS is sent to the caller's number. | Zero β only the missed-call IVR flow type needs to be configured. |
| B β IVR redirect | Guest calls your business; an IVR prompt offers an SMS option; the call is forwarded to a Twilio number provisioned by SmartBot, and the caller receives an SMS to text instead. | Call forwarding to the Twilio number, IVR prompt recording, redirect configuration. |
| C β Direct distribution | You publish the SmartBot phone number directly on appointment confirmations, reminders, QR codes at the front desk, on receipts, and on product displays. QR codes also enable per-surface usage tracking. | Per-surface QR generation; SmartBot number included in notification templates. |
How the SMS channel works
Receiving messages
When a guest sends a text to the SmartBot phone number, SmartBot identifies the organization and center using that phone number, validates that both are active, checks whether the guest's phone number is on the blocked list, and creates or resumes a conversation session.
Blacklisted phone numbers are silently ignored β no response is sent.
Session handling
Each SMS conversation session has a 30-minute TTL on the underlying conversational state record (this is a global value across all SmartBot channels β see Abandoned booking timing for the per-channel inactivity threshold that drives the SMS recovery message, which is a separate concept). Sessions can roll over to a new session ID while preserving the organization, center, and channel context.
If a guest sends a new message while a previous response is still being generated, SmartBot sends a brief hold message and skips the new message to prevent out-of-order responses.
Opt-out notice
The first SMS sent to a guest in a new conversation session includes an opt-out notice instructing the guest to reply STOP to unsubscribe from SmartBot messages. Subsequent messages in the same session do not repeat the notice.
Abandoned booking timing
SMS Bot abandoned-booking SMS recovery fires after 30 minutes of guest inactivity by default (env-overridable per deployment). For comparison, the Web Bot recovery fires after 10 minutes. Both are environment-configurable, so your tenant may use different values. The session-record TTL above (30 minutes) is a separate value with a different purpose β do not confuse them.
The recovery message instructs the guest to reply Hi to restart the conversation, or to use the included Webstore URL to book online. This recovery is enabled by default for all SmartBot deployments and requires no setup.
Message format and limits
SMS responses are limited to 1,600 characters per message. When a response would exceed this limit, SmartBot splits the content across multiple messages.
When presenting lists (such as services or time slots), SmartBot paginates at five items per page. Guests can type See More to load the next page of results.
Tip β service-catalog ordering: Because SMS guests must page through long lists, order your service catalog so that the most commonly booked services appear in the first five SMS results. Most guests will not page through multiple screens. The Web Bot offers a Show All option that doesn't have this constraint.
Usage tracking
SmartBot tracks daily SMS usage per center, recording the total number of inbound and outbound messages. You can review this data in the Usage Metrics panel.
Failure handling
If a message fails to deliver, SmartBot retries delivery up to two times automatically.
Tips
- Keep service names short. SMS displays five services per page with no images. Guests read service names only, so brief and descriptive names reduce the need for guests to page through multiple screens.
- Use missed-call SMS as a zero-cost recovery channel. Missed-call handling requires no additional guest-facing setup β it triggers automatically when a call goes unanswered. Enable it to recapture guests who call outside staffed hours.
- Publish the SmartBot number on printed materials. QR codes printed at the front desk, on receipts, or on retail displays give walk-in guests a frictionless way to start an SMS conversation and allow per-surface tracking of conversation volume.
- Monitor inbound vs. outbound SMS counts. A high ratio of inbound to outbound messages can indicate guests are sending messages that SmartBot is not recognizing. Review the Usage Metrics panel and consider adding FAQ entries to address common unmatched inputs.
- Remind guests of the opt-out path when testing. During setup and testing, each new conversation session triggers the opt-out notice. If your test number is opted out, messages will be silently dropped. Use a fresh number or contact your provisioning team to reset the opt-out status.
Troubleshooting
| Problem | Likely cause | Resolution |
|---|---|---|
| Guest sends an SMS and receives no reply | Guest's phone number may be on the blocked list, or the SMS channel may not be enabled for the center. | Verify that the SMS channel is enabled for the center and confirm the guest's number is not blocked. See Configure the SMS channel. |
| Guest receives the opt-out notice on every message | Each new conversation session appends the opt-out notice to the first message. If a guest sees it repeatedly, their session may be expiring between each message. | No action required β this is expected behavior when sessions expire between contacts. Encourage guests to complete their booking in a single session. |
| Guest reports messages arriving out of order or responses being skipped | A previous SmartBot response was still being generated when the guest sent a follow-up message. SmartBot sends a hold message and skips the duplicate to prevent out-of-order delivery. | Advise the guest to wait for each response before sending the next message. |
| Missed-call SMS is not firing after an unanswered call | The missed-call IVR flow type may not be configured for the center. | Confirm the correct IVR flow type is set. See Configure the voice channel. |