---
title: "SMS Opt-Out STOP Keywords by Country"
description: "SMS opt-out and STOP keyword requirements by country: local-language keywords, one-step opt-out, replies, suppression lists and WhatsApp opt-out rules."
canonical: "https://omnichannels.ai/blog/sms-opt-out-stop-keywords-by-country/"
language: "en"
updated: "2026-11-08"
publisher: "BroadNet Technologies"
brand: "OmniChannels.ai"
category: "compliance"
primaryQuery: "sms opt-out stop keyword requirements by country"
keywords: ["sms stop keyword", "sms opt-out requirements", "sms unsubscribe keyword by country", "sms opt out arabic ايقاف", "stop sair sms", "sms suppression list", "whatsapp opt out policy", "dnd registry sms"]
published: "2026-11-08"
author: "OmniChannels.ai Editorial Team"
reviewer: "BroadNet Messaging Solutions Team"
readingMinutes: 10
answer: "In most markets we cover, marketing SMS must carry a way to opt out, and the keyword is STOP. Gulf and wider Arabic-speaking markets pair it with ايقاف, Brazil with SAIR, and Spanish-speaking Latin American markets with a Spanish opt-out word. Opt-outs are honoured network-wide, usually in one step, and stay in force until the person gives consent again. A few markets add a do-not-disturb registry, and India uses a preference register instead of a keyword. This is not legal advice."
takeaways: ["STOP is the common keyword; the data pairs it with ايقاف in Arabic-speaking markets (إيقاف for Egypt) with SAIR in Brazil, and with a Spanish word in Spanish-speaking Latin America.", "Many entries describe a one-step opt-out that is honoured network-wide and stays in force until the recipient gives consent again.", "Alphanumeric sender IDs cannot receive replies, so a STOP-by-reply opt-out needs a number that can receive messages, or another opt-out route.", "Keep one suppression list across channels and check it before every send, whichever channel the person used to opt out.", "WhatsApp opt-out is governed by Meta's policy, which says businesses must respect requests to block, discontinue or opt out, on or off WhatsApp."]
faq: 
  - q: "Is STOP mandatory in every country?"
    a: "No single rule applies everywhere. In the regulations data we maintain, most entries require STOP or an equivalent opt-out wording on marketing or promotional messages, but India uses a preference register rather than a keyword, and some entries only say opt-out wording without naming a keyword. Confirm the rule for your destination with BroadNet during onboarding."
  - q: "Which opt-out keywords do Arabic-speaking markets use?"
    a: "Our data lists STOP together with ايقاف for the UAE, Saudi Arabia, Qatar, Kuwait, Jordan, Bahrain, Oman, Iraq, Lebanon and several North African markets. Egypt's entry gives إيقاف, spelled with a hamza. Offer both the Latin and the Arabic keyword in the opt-out line, and accept either when a reply arrives."
  - q: "Do transactional messages need an opt-out line?"
    a: "The entries we use describe opt-out wording for marketing or promotional messages. They do not set a rule for transactional messages such as OTPs or delivery alerts, so we do not either. Keep promotional content out of transactional traffic, and confirm how your destination treats mixed messages."
  - q: "Can people reply STOP to an alphanumeric sender ID?"
    a: "No. An alphanumeric sender ID is a text label and cannot receive replies. If your opt-out relies on a STOP reply, send promotional messages from a number that can receive messages, or give another route, such as a link or a registry. Check which route your destination accepts before choosing the sender type."
  - q: "How do I handle opt-outs across SMS and WhatsApp?"
    a: "Keep one suppression list keyed by phone number in international format, and check it before every send on every channel. When someone opts out on one channel, record the date, channel and wording. Decide, with your own legal advice, whether that opt-out also covers other channels; do not assume it does or does not."
  - q: "How should a WhatsApp opt-out work?"
    a: "Meta's business policy says businesses must respect requests, on or off WhatsApp, to block, discontinue or opt out of communications, and recommends clear instructions on how to opt out. Treat a message such as stop sent in a chat as an opt-out, and add the person to your suppression list."
sources: 
  - title: "WhatsApp Business Messaging Policy"
    url: "https://whatsappbusiness.com/policy/"
  - title: "TDRA spam regulatory policy (UAE)"
    url: "https://tdra.gov.ae/-/media/About/regulations-and-ruling/EN/cellular-phone-spam-regulatory-policy-English.ashx"
  - title: "CST SPAM regulations (Saudi Arabia)"
    url: "https://www.cst.gov.sa/en/regulations-and-licenses/regulations/Document-522"
  - title: "TRAI: Telecom Commercial Communications Customer Preference Regulations (India)"
    url: "https://www.trai.gov.in/"
---

# SMS Opt-Out STOP Keywords by Country

Canonical: https://omnichannels.ai/blog/sms-opt-out-stop-keywords-by-country/
Language: en
Publisher: OmniChannels.ai by BroadNet Technologies

This guide is for marketing and compliance teams that send promotional SMS across several countries. It shows what our country data says about opt-out keywords, how to handle replies and suppression lists, and what Meta documents for WhatsApp. It is not legal advice, and rules change: confirm each market with BroadNet during onboarding.

## What do SMS opt-out requirements look like by country?

The pattern is consistent: promotional SMS must include opt-out wording, a keyword such as STOP must be honoured, and the opt-out is applied quickly. The details differ by region. The table gives each country's rule as the entry in our regulations data states it, with a link to that country's sender ID page. The data was last reviewed in 2026, so verify before you launch a campaign.

| Country | Opt-out rule as the entry states it |
|---|---|
| [Algeria](/sender-id/algeria/) | STOP / ايقاف on every marketing message; honoured network-wide; audited by the regulator |
| [Argentina](/sender-id/argentina/) | STOP plus a Spanish opt-out word (confirm the exact word with BroadNet during onboarding); one-step; applied across the operator |
| [Australia](/sender-id/australia/) | STOP plus a clearly stated unsubscribe on every marketing send; honoured within 5 business days at most |
| [Bahrain](/sender-id/bahrain/) | STOP / ايقاف on every marketing message; honoured network-wide; audited by the regulator |
| [Bangladesh](/sender-id/bangladesh/) | STOP; DND-registry suppression applied automatically; records retained per regulator requirements |
| [Belgium](/sender-id/belgium/) | STOP; honoured network-wide; one-step; irreversible until re-consent |
| [Bolivia](/sender-id/bolivia/) | STOP plus a Spanish opt-out word (confirm the exact word with BroadNet during onboarding); one-step; applied across the operator |
| [Brazil](/sender-id/brazil/) | STOP / SAIR; one-step; applied across the operator |
| [Cambodia](/sender-id/cambodia/) | STOP; DND-registry suppression applied automatically; records retained per regulator requirements |
| [Canada](/sender-id/canada/) | STOP; honoured immediately and confirmed once; CTIA short-code monitoring audits compliance |
| [Chile](/sender-id/chile/) | STOP plus a Spanish opt-out word (confirm the exact word with BroadNet during onboarding); one-step; applied across the operator |
| [Colombia](/sender-id/colombia/) | STOP plus a Spanish opt-out word (confirm the exact word with BroadNet during onboarding); one-step; applied across the operator |
| [Comoros](/sender-id/comoros/) | STOP / ايقاف on every marketing message; honoured network-wide; audited by the regulator |
| [Djibouti](/sender-id/djibouti/) | STOP / ايقاف on every marketing message; honoured network-wide; audited by the regulator |
| [Ecuador](/sender-id/ecuador/) | STOP plus a Spanish opt-out word (confirm the exact word with BroadNet during onboarding); one-step; applied across the operator |
| [Egypt](/sender-id/egypt/) | STOP / إيقاف; honoured network-wide; one-step; irreversible until re-consent |
| [France](/sender-id/france/) | STOP; honoured network-wide; one-step; irreversible until re-consent |
| [Germany](/sender-id/germany/) | STOP; honoured network-wide; one-step; irreversible until re-consent; required wording in German (the entry gives no word) |
| [Hong Kong](/sender-id/hong-kong/) | STOP; DND-registry suppression applied automatically; records retained per regulator requirements |
| [Indonesia](/sender-id/indonesia/) | STOP; DND-registry suppression applied automatically; records retained per regulator requirements |
| [Iraq](/sender-id/iraq/) | STOP / ايقاف on every marketing message; honoured network-wide; audited by the regulator |
| [Ireland](/sender-id/ireland/) | STOP; honoured network-wide; one-step; irreversible until re-consent |
| [Italy](/sender-id/italy/) | STOP; honoured network-wide; one-step; irreversible until re-consent |
| [Jordan](/sender-id/jordan/) | STOP / ايقاف; honoured network-wide; one-step; irreversible until re-consent |
| [Kuwait](/sender-id/kuwait/) | STOP / ايقاف; honoured network-wide; one-step; irreversible until re-consent |
| [Lebanon](/sender-id/lebanon/) | STOP / ايقاف on every marketing message; honoured network-wide; audited by the regulator |
| [Malaysia](/sender-id/malaysia/) | STOP; DND-registry suppression applied automatically; records retained per regulator requirements |
| [Mauritania](/sender-id/mauritania/) | STOP / ايقاف on every marketing message; honoured network-wide; audited by the regulator |
| [Mexico](/sender-id/mexico/) | STOP plus a Spanish opt-out word (confirm the exact word with BroadNet during onboarding); one-step; applied across the operator |
| [Morocco](/sender-id/morocco/) | STOP / ايقاف on every marketing message; honoured network-wide; audited by the regulator |
| [Nepal](/sender-id/nepal/) | STOP; DND-registry suppression applied automatically; records retained per regulator requirements |
| [Netherlands](/sender-id/netherlands/) | STOP; honoured network-wide; one-step; irreversible until re-consent |
| [New Zealand](/sender-id/new-zealand/) | STOP plus a clearly stated unsubscribe on every marketing send; honoured within 5 business days at most |
| [Nigeria](/sender-id/nigeria/) | STOP; honoured network-wide; NCC-run DND registry suppression applied automatically for promotional traffic |
| [Norway](/sender-id/norway/) | STOP; honoured network-wide; one-step; irreversible until re-consent |
| [Oman](/sender-id/oman/) | STOP / ايقاف on every marketing message; honoured network-wide; audited by the regulator |
| [Pakistan](/sender-id/pakistan/) | STOP; honoured network-wide; PTA-run DND-style registry suppression applied automatically |
| [Palestine](/sender-id/palestine/) | STOP / ايقاف on every marketing message; honoured network-wide; audited by the regulator |
| [Peru](/sender-id/peru/) | STOP plus a Spanish opt-out word (confirm the exact word with BroadNet during onboarding); one-step; applied across the operator |
| [Philippines](/sender-id/philippines/) | STOP; DND-registry suppression applied automatically; records retained per regulator requirements |
| [Poland](/sender-id/poland/) | STOP; honoured network-wide; one-step; irreversible until re-consent |
| [Qatar](/sender-id/qatar/) | STOP / ايقاف; honoured network-wide; CRA-audited; wording mandatory on every promotional message |
| [Romania](/sender-id/romania/) | STOP; honoured network-wide; one-step; irreversible until re-consent |
| [Saudi Arabia](/sender-id/saudi-arabia/) | STOP / ايقاف; honoured network-wide; one-step; irreversible until re-consent; CST audits the audit trail |
| [Singapore](/sender-id/singapore/) | STOP; DND-registry suppression applied automatically; records retained per regulator requirements |
| [Spain](/sender-id/spain/) | STOP; honoured network-wide; one-step; irreversible until re-consent |
| [Sri Lanka](/sender-id/sri-lanka/) | STOP; DND-registry suppression applied automatically; records retained per regulator requirements |
| [Sweden](/sender-id/sweden/) | STOP; honoured network-wide; one-step; irreversible until re-consent |
| [Switzerland](/sender-id/switzerland/) | STOP; honoured network-wide; one-step; irreversible until re-consent |
| [Taiwan](/sender-id/taiwan/) | STOP; DND-registry suppression applied automatically; records retained per regulator requirements |
| [Thailand](/sender-id/thailand/) | STOP; DND-registry suppression applied automatically; records retained per regulator requirements |
| [Tunisia](/sender-id/tunisia/) | STOP / ايقاف on every marketing message; honoured network-wide; audited by the regulator |
| [Türkiye](/sender-id/turkiye/) | STOP; honoured network-wide; one-step; irreversible until re-consent |
| [UAE](/sender-id/uae/) | STOP or ايقاف on every promotional SMS; honoured network-wide; audited by TDRA; one-step; irreversible until re-consent |
| [Ukraine](/sender-id/ukraine/) | STOP; honoured network-wide; one-step; irreversible until re-consent |
| [United Kingdom](/sender-id/united-kingdom/) | STOP; honoured network-wide; one-step; irreversible until re-consent |
| [Uruguay](/sender-id/uruguay/) | STOP plus a Spanish opt-out word (confirm the exact word with BroadNet during onboarding); one-step; applied across the operator |
| [USA](/sender-id/usa/) | STOP; honoured immediately and confirmed once; CTIA short-code monitoring audits compliance |
| [Vietnam](/sender-id/vietnam/) | STOP; DND-registry suppression applied automatically; records retained per regulator requirements |

### Which countries give no specific keyword?

Seventeen entries say only that every promotional message must include "STOP / opt-out wording", with DND-registry suppression applied automatically where the regulator runs one. They do not give a local-language keyword, and we do not invent one. Use STOP, add a clear plain-language opt-out line in the recipient's language, and confirm the exact requirement with our team:

[Angola](/sender-id/angola/), [Botswana](/sender-id/botswana/), [Cameroon](/sender-id/cameroon/), [Ethiopia](/sender-id/ethiopia/), [Ghana](/sender-id/ghana/), [Ivory Coast](/sender-id/ivory-coast/), [Kenya](/sender-id/kenya/), [Madagascar](/sender-id/madagascar/), [Mauritius](/sender-id/mauritius/), [Mozambique](/sender-id/mozambique/), [Namibia](/sender-id/namibia/), [Rwanda](/sender-id/rwanda/), [Senegal](/sender-id/senegal/), [South Africa](/sender-id/south-africa/), [Tanzania](/sender-id/tanzania/), [Uganda](/sender-id/uganda/), [Zambia](/sender-id/zambia/).

India is different. The entry says recipients block promotional messages, fully or by category, in the preference register (by SMS or call to 1909, USSD, IVRS, an approved app or an OTP-verified web portal), and operators add the details needed to revoke consent to every promotional message. Preferences and revoked consents are scrubbed on DLT before delivery. For [India](/sender-id/india/), build your process around the register and DLT scrubbing, not a keyword alone.

## Which regional patterns matter most?

- **Arabic-speaking markets:** STOP together with ايقاف (Egypt: إيقاف). Put both in the line, for example "للإلغاء أرسل ايقاف / Reply STOP". Arabic text switches the SMS to Unicode, so mind the length.
- **Latin America:** STOP together with a local-language word (SAIR in Brazil; confirm the Spanish word with BroadNet for the other markets), one-step, applied across the operator.
- **Europe and other STOP-only entries:** STOP, honoured network-wide, one-step and irreversible until the recipient consents again. Germany's entry adds required wording in German without naming a word, so confirm it.
- **United States and Canada:** STOP is honoured immediately and confirmed once, and the entry says CTIA short-code monitoring audits compliance.
- **Australia and New Zealand:** STOP plus a clearly stated unsubscribe on every marketing send, honoured within 5 business days at most.
- **DND-registry markets:** STOP, plus automatic suppression against the registry and record retention per the regulator.

## Do transactional and promotional messages differ?

Yes in practice, though our data speaks only about marketing and promotional traffic. The entries describe opt-out wording on marketing or promotional messages. They set no rule for transactional messages such as OTPs, receipts or delivery alerts, so do not add or remove obligations on that basis. Two habits help:

1. Keep promotional content out of transactional messages, and confirm with BroadNet how your destination treats a message that mixes both.
2. Route each type through the sender and registration your destination expects. See [SMS marketing rules by country](/blog/sms-marketing-rules-by-country/) and [quiet hours by country](/blog/sms-quiet-hours-by-country/).

## How do I handle STOP replies?

A STOP reply only reaches you if the sender can receive messages. Alphanumeric sender IDs cannot, as explained in [SMS sender ID types](/blog/sms-sender-id-types-explained/). A two-way number can, as covered in the [two-way SMS guide](/blog/two-way-sms-guide/).

Procedure:

1. Check every inbound message for the opt-out keywords before any other logic, in each language you send.
2. Add the number to your suppression list immediately, with the date, the channel and the exact text received.
3. Send one short confirmation only if your market's rules expect it. The US entry in our data says STOP is "confirmed once".
4. Stop all scheduled sends to that number, including queued batches.
5. Keep the record for as long as your market requires it. The data says several markets require records to be retained per the regulator.

If you send promotions from an alphanumeric sender ID because the country requires it, give a route that does not depend on a reply: a short link to a preference page, or a registry where one exists. Whether that satisfies a market is a question for the regulator and your counsel.

## How do I keep opt-out lines short?

The opt-out text competes with your message for space. "Reply STOP to opt out" is 21 characters. In GSM-7 text a single SMS holds 160 characters and a Unicode one only 70, so a bilingual Arabic and English line can push a message into a second segment. See [SMS character limits and Unicode](/blog/sms-character-limits-unicode-arabic/).

Tips:

- Put the opt-out last, in plain words: "Reply STOP to opt out."
- Use short links. See [SMS link tracking](/blog/sms-link-tracking-short-links/).
- Write the Arabic line first when your audience reads Arabic, then add the Latin keyword.
- Count segments with the [SMS character counter](/tools/sms-character-counter/) before sending.

## How do I manage suppression lists across channels?

Treat opt-out as a property of the person, stored once. Use E.164 numbers as the key, as in [E.164 phone number format](/blog/e164-phone-number-format/), and check the list at send time, not only at import time.

| Decision | Recommended practice |
|---|---|
| Where the list lives | One central list, read by SMS, WhatsApp, RCS and voice sends |
| What you store | Number, date, channel, exact wording, campaign |
| When you check | Immediately before each send and again at scheduled run time |
| Re-consent | Record a fresh opt-in with evidence; do not simply delete the entry |
| Scope across channels | Decide with your own advice whether an opt-out applies to all channels |

For consent evidence, see [opt-in and consent for multichannel campaigns](/blog/opt-in-consent-multichannel-campaigns/).

## What does WhatsApp say about opt-out?

WhatsApp opt-out is governed by Meta's policy, not by an SMS keyword table. The WhatsApp Business Messaging Policy says businesses must respect all requests, on or off WhatsApp, by a person to block, discontinue or otherwise opt out of communications, including removing the person from their contact list. It recommends clear instructions for how people can opt out of specific categories of messages, and clear, intuitive opt-in and opt-out flows.

In practice: treat words such as stop or unsubscribe in a WhatsApp chat as an opt-out, add a clear opt-out instruction to marketing templates, and suppress the number across channels. For wider sending practice, see [sending without getting banned](/blog/whatsapp-bulk-messaging-without-getting-banned/).

## Worked example: a retailer launching in four markets

"Souq Rafiq" (synthetic) plans a promotional SMS to customers in the UAE, Saudi Arabia, Brazil and Germany.

1. UAE and Saudi Arabia: the entries call for STOP or ايقاف on promotional SMS, so the message ends with "Reply STOP / ايقاف". It is sent from a sender that can receive replies, or with another opt-out route agreed during onboarding.
2. Brazil: the entry gives STOP / SAIR, so the line is in Portuguese and offers both words.
3. Germany: the entry mentions required wording in German, so the team confirms the exact wording with BroadNet before launch.
4. All four: replies feed one suppression list, checked before every send, and the same list is used for WhatsApp campaigns.

## What are the common mistakes?

- **Inventing a keyword** for a country whose entry does not name one.
- **Only English.** In Arabic-speaking and Portuguese or Spanish-speaking markets, accept the local word as well as STOP.
- **Alphanumeric sender with a STOP-by-reply line,** which cannot work.
- **Late suppression,** where queued or scheduled sends go out after an opt-out.
- **Channel silos,** with SMS and WhatsApp lists that never meet.
- **Treating this table as final.** It is a summary of our data; regulators and operators change rules. Confirm with BroadNet during onboarding, and seek legal advice for your own case.

## How OmniChannels.ai helps

OmniChannels.ai sends two-way SMS, bulk SMS and WhatsApp from one platform, with Arabic and Unicode support, duplicate filtering in campaigns and delivery reports. Replies appear in one shared inbox, and you can run channel fallback per use case. Our team prepares and files sender ID registrations with you and confirms each market's current requirements during onboarding. See the [SMS channel](/channels/sms/), the [sender ID pages](/sender-id/) and the [shared inbox](/platform/unified-inbox/).