Two-Way SMS: How It Works, Use Cases and Setup Guide

How should you handle keywords and STOP?

Handle STOP before anything else: check each inbound message for opt-out words first, suppress the number immediately and send one confirmation. Then handle your own keywords.

For US marketing messages, the FCC's rules treat replying "stop", "quit", "end", "revoke", "opt out", "cancel" or "unsubscribe" as a reasonable way to revoke consent, bar senders from naming one exclusive method, and require requests to be honoured as soon as practicable and within 10 business days at most. A one-time confirmation text is allowed, and it must only confirm the opt-out. If your system cannot accept replies, say so in the message and offer another way to opt out. CTIA's messaging principles, which carriers use for 10DLC and short-code programs, are consistent with this approach. Check the current rule text in 47 CFR 64.1200 with your counsel.

Outside the US the requirements differ. Our country pages and the opt-in and opt-out glossary entry summarise the rules we track, for example that an opt-out keyword is required in several GCC markets.

A practical keyword table:

Normalise replies before matching: trim spaces, ignore case, and convert Arabic-Indic digits (١، ٢) to Western digits (1, 2). Customers type them both ways.

How do you set up two-way SMS?

Setting up two-way SMS means choosing a reply-capable sender, deciding where replies go, writing the message flows and testing the full loop. Allow time for number or registration lead times.

Setup steps

1. Define the conversation. Write the flow as a table: outbound text, valid replies, next action, fallback for unexpected replies.
2. Pick the sender per country. Choose a long code, 10DLC, toll-free or short code where available. Use the sender ID checker and ask the account team to confirm availability.
3. Register where required. In the US this means 10DLC brand and campaign registration, toll-free verification or a short code application. We prepare and file these with you; approvals stay with carriers.
4. Choose the reply destination. Use the shared inbox when people answer, a webhook endpoint when software answers, or SMPP for volume.
5. Build opt-out handling first. Test STOP before testing anything else.
6. Write the flows. Add a reply to every inbound message, including "I did not understand, reply 1 or 2".
7. Test the loop on each operator. Send, reply, confirm the reply appears in your system and send the next message. Test Arabic replies and long replies.
8. Launch small. Start with a segment and watch reply rate, opt-out rate and unmatched replies.

Where does two-way SMS not work?

Two-way SMS is not available everywhere. Whether a business can receive replies depends on the country, the operator and the sender type, and some markets only support alphanumeric sender IDs for business traffic.

Examples from our regulation data: the US has no alphanumeric sender IDs and uses 10DLC, toll-free or short codes; Canada uses common short codes or long codes, with short codes applied for through txt.ca; the UAE and Saudi Arabia use registered alphanumeric sender IDs, which are one-way. In those Gulf markets, the practical reply channel is WhatsApp, a link to a web form or a call-back number in the message. See the sender ID pages for each country.

Two cost-related cautions. First, inbound messages may be billed or restricted differently from outbound ones; confirm with your account team. Second, a reply-capable number costs more effort to keep healthy than a one-way sender, because it needs monitoring for spam replies and unmatched keywords.

What are the common mistakes with two-way SMS?

The common mistakes are launching without a tested STOP path, asking open questions that automation cannot parse and leaving replies unanswered.

• No STOP path or a slow one. Suppress at once.
• Open-ended questions where a number or keyword would do.
• No reply to unmatched messages. Silence feels broken.
• Replies landing in a mailbox no one watches. Route to an inbox with an owner and a response target.
• Ignoring Arabic digits and spelling variants.
• Using an alphanumeric sender and expecting replies.
• Advertising a keyword before the number is live.
• Mixing OTP and conversation traffic on one number. Keep them separate.

Worked example: a clinic confirming appointments

"Marsa Clinic", a synthetic clinic in Doha, sends reminders 24 hours before each visit from a reply-capable number.

The message reads: "Marsa Clinic: your visit is tomorrow at 10:30. Reply 1 to confirm, 2 to reschedule, or STOP to opt out of reminders." A reply of 1 marks the booking confirmed. A reply of 2 sends a message with the next three available slots, and a reply of 1 to 3 books one. Any unrecognised reply creates a conversation in the shared inbox, where a receptionist answers during opening hours and the system sends a polite auto-reply outside them.

The clinic tracks four numbers each week: confirmation rate, reschedule rate, unmatched replies and opt-outs. When unmatched replies rise, it reads a sample and adds the missing variants to its keyword table. For related patterns see appointment reminders over WhatsApp and SMS.

How do two-way SMS and WhatsApp fit together?

SMS reaches any mobile phone without an app, while WhatsApp supports richer conversations. Many businesses use both, with WhatsApp first and SMS as the fallback.

Two-way SMS suits short structured exchanges and customers who are not on WhatsApp. WhatsApp suits buttons, media and long threads, with Meta's rules for the customer service window and templates. Configure channel fallback so that a message goes to WhatsApp first and falls back to SMS where WhatsApp cannot deliver, and compare the channels in WhatsApp vs SMS vs RCS.

How OmniChannels.ai helps

OmniChannels.ai, powered by BroadNet Technologies, supports two-way SMS over BroadNet's direct operator connectivity, with replies handled in the Omni Inbox, via webhooks or on SMPP 3.4 for high volume. Agents can assign and tag conversations and reply with templates and media. Our team prepares and files sender ID, 10DLC, toll-free and short-code registrations with you, and the account team confirms which sender types and numbers are available per destination. Approvals stay with carriers and regulators. Book a demo and bring your reply flow; we will map it to the right sender in each country.