> ## Documentation Index > Fetch the complete documentation index at: https://help.wotnot.io/llms.txt > Use this file to discover all available pages before exploring further. # SMS > Deploy AI agents to SMS to automate responding to incoming text messages. ![Screenshot 2026 08 31 133924](https://mintcdn.com/wotnot/79SKP2TEnpNsM0nK/images/Screenshot-2026-08-31-133924.png?fit=max\&auto=format\&n=79SKP2TEnpNsM0nK\&q=85\&s=b915cccdafbebc11c15934a87351d525) > [!NOTE] > > SMS supports plain text only. There are no buttons, images, or rich formatting, so flows designed for web or other channels may need to be simplified rather than directly ported to SMS. [YouTube video player](https://www.youtube.com/embed/-cP-SF9zRy4) # Before you start ### A number and a provider To publish an agent to SMS, you need an SMS-capable phone number from a supported provider. Before connecting the number, make sure you have: * An active SMS number that can receive incoming messages. * An account with your SMS provider. * The provider credentials required to connect the number to WotNot. * Permission to configure inbound messaging or webhooks for the number. * A registered sender identity where required by your country or carrier. > [!NOTE] > > SMS provider availability and required credentials can vary by region. Use the provider's documentation to confirm the requirements for your country. ### Regional registration SMS registration requirements are determined by carriers and local regulations, not by WotNot. Registration can also take significantly longer than the technical setup. Common examples include: * **India:** DLT registration may be required before commercial SMS traffic can be sent. * **United States:** 10DLC registration is required for many application-to-person (A2P) SMS use cases. * **Other regions:** Local sender registration, brand registration, or other carrier requirements may apply. Complete the required registration before publishing your agent. Approval times depend on the carrier or local authority and can range from a few days to several weeks. # Connecting a number Connect your SMS provider and number to WotNot before publishing the agent. ### Entering provider credentials To launch your chatbot on your SMS channel, first, you need to get APIs from our list of SMS partners: 1. Twilio 2. TechAlpha Once you receive the SMS APIs, follow the steps mentioned below: #### Twilio * Go to Settings > Channels > SMS > Configuration * Click “Create SMS configuration” * Enter the “Phone number” * Login to your [Twilio account](http://twilio/login) * Navigate to the Account > Settings 1. Copy the “Account SID” 2. Copy the “Auth token” * Paste these values on the WotNot configuration screen and hit “Save” * Test by sending “Hi” to your SMS number #### TechAlpha > [!NOTE] > > Contact sales: [sales@techalphagroup.com](mailto:sales@techalphagroup.com) 1. Go to Settings > Channels > SMS > Configuration 2. Click “Create SMS configuration” 3. Enter the “Phone number” 4. Reach out to your Account Manager at TechAlpha 1. Copy the “Username” 2. Copy the “Password” 3. Copy the “ANI” 4. Copy the "MMS account username" 5. Copy the "MMS account password" 5. Paste these values on the WotNot configuration screen and hit “Save” 6. Test by sending “Hi” to your SMS number ### Verifying inbound routing The SMS number must route incoming messages to WotNot. Depending on your provider, this may require configuring an inbound webhook in the provider dashboard. After connecting the number: * Open your SMS provider's dashboard and locate the **Inbound SMS** or **Messaging** configuration. * Confirm that the inbound message webhook points to the endpoint provided by WotNot. * Send an SMS to the connected number from a real mobile phone. * Check the conversation or chat logs in WotNot to confirm that the incoming message reached the agent. > [!WARNING] > > If messages sent to the number do not reach the agent, check the provider's inbound webhook configuration first. A missing or incorrect webhook is one of the most common causes of inbound SMS not reaching the bot. # Designing for SMS SMS conversations work best when they are short, linear, and easy to understand without visual formatting. A flow that works well on a web widget may need to be redesigned for SMS rather than copied directly. ### Character limits and segments SMS messages are divided into segments based on their length and character set. A standard SMS can contain up to **160 characters** when using the GSM-7 character set. Longer messages are split into multiple segments. When a message is split, each segment has less available space because part of the message is used for concatenation information. The exact limit can also change when special or Unicode characters are used. For example: * A short message may use one SMS segment. * A longer message may be split into two or more segments. * Using emojis or certain non-GSM characters can reduce the number of characters available in a segment. * Each additional segment may be charged separately by the SMS provider. ### What interactive blocks become SMS does not support interactive buttons, lists, or other rich controls. WotNot converts supported interactive options into numbered text so that the contact can respond using a number. For **example**, a web flow might display: Choose an option: Book an appointment Check an existing appointment Talk to support In SMS, the same interaction can appear as: Choose an option: 1. Book an appointment 2. Check an existing appointment 3. Talk to support Reply with 1, 2, or 3. The contact can then reply with the corresponding number, and the agent continues through the matching path. ### Keeping flows short Design SMS conversations around the limitations of the channel. * Ask one question at a time. * Keep messages short and focused. * Avoid long introductions or explanations. * Use numbered options instead of expecting users to type long responses. * Do not rely on images, buttons, lists, or visual formatting. * Break complex web experiences into a few simple SMS steps. ## Publishing the agent Once your number is connected and inbound routing is working, connect the agent to the SMS number and publish it. * Open the agent you want to publish. * Select the SMS number. * Select the flow or agent version you want to publish. * Review the SMS configuration and confirm that the correct number is connected. * Click **Deploy** to make the agent live. ### Testing Test the deployed agent from a real mobile phone rather than relying only on the builder preview. Send messages to the connected SMS number and verify: * The incoming message reaches the agent. * The agent response is delivered to the handset. * Long messages are split as expected. * Numbered options are displayed clearly. * Replies such as `1`, `2`, or `3` select the correct option. * Invalid or unexpected replies are handled correctly. * The conversation continues through the expected flow. > [!NOTE] > > Always test the complete conversation after deployment. A flow that looks correct in the builder may behave differently when converted to plain SMS. ## Compliance ### Opt-in and opt-out Contacts must have consented to receive SMS messages from your business ![Image](https://mintcdn.com/wotnot/ZvBlY58cOcRHCVBj/images/image-595.png?fit=max\&auto=format\&n=ZvBlY58cOcRHCVBj\&q=85\&s=d4ca00534d6295c60d2cea2cda577423) Your SMS program should: * Collect and retain appropriate consent before sending messages. * Clearly identify the business or service sending the messages. * Provide a way for contacts to stop receiving messages. * Honour opt-out requests such as STOP and other applicable keywords. * Include opt-out instructions where required by local regulations or carrier rules. > [card] To open that follow these steps: > > Go to Settings→ Channel→ SMS→ Opt-in and opt-out→ Fix Keywords→ Save Changes ### Sender Identity The sender identity shown to a contact depends on the country, provider, and number type. Depending on the region, SMS may use: * A **long-code phone number** as the sender. * An **alphanumeric sender ID**. * Other sender types supported by the local carrier. * You need the **Phone Number, Account SID, Auth Token, and Webhook URL**. # Troubleshooting > [accordion] Inbound messages are not reaching the bot > > Check the following: > > * Confirm that the correct SMS number is connected in WotNot. > > * Verify that the number can receive SMS messages. > > * Check the inbound messaging configuration in your SMS provider. > > * Confirm that the provider webhook is configured with the endpoint provided by WotNot. > > * Send a new message from a real mobile phone and check the conversation logs. > > * Confirm that the latest version of the agent has been deployed. > > > [!NOTE] > > > > The provider webhook should be the first thing to check when inbound messages are not reaching the bot. > [accordion] Outbound messages are not delivered > > Check the following: > > * Confirm that the SMS number and provider connection are active. > * Verify that the recipient's number is valid and can receive SMS messages. > * Check the provider's delivery status and error details. > * Confirm that your account has sufficient SMS credits or balance. > * Check whether the message or sender identity is blocked by the carrier. > * Verify that any required regional registration has been completed. > [accordion] Messages are split unexpectedly > > Messages can be split when they exceed the character limit for a single SMS segment. > > Check whether: > > * The message exceeds the applicable segment limit. > * The message contains emojis or Unicode characters. > * Multiple segments are being generated by the provider. > > Shorten the message where possible to reduce segmentation and messaging costs. > [accordion] Numbered replies are not matching an option > > Check that: > > * The interactive block is configured with the expected options. > * The SMS message clearly tells the contact which number to reply with. > * The contact is replying with the expected number. > * There are no additional characters or text causing the reply to be interpreted differently. > * The deployed agent contains the latest version of the flow. > [accordion] Registration or template is rejected by the carrier > > Carrier registration and message approval requirements vary by region. > > Check the following: > > * Whether your business or sender identity is registered. > * Whether the required DLT, 10DLC, or equivalent registration is complete. > * Whether the submitted sender details match your business information. > * Whether the message content meets local carrier requirements. > > If the carrier rejects the registration, review the rejection reason provided by your SMS provider and complete the required changes before trying again. > [accordion] SMS costs are higher than expected > > Long messages may be charged as multiple SMS segments. > > Review the following: > > * The length of your outgoing messages. > * Whether Unicode characters or emojis are increasing segmentation. > * The number of segments reported by your provider. > * Whether the same response is being sent repeatedly due to a flow configuration. > > Keep responses concise and check your provider's pricing for each SMS segment. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.