--- title: "Channels are not interchangeable: the most common early mistake" summary: "SMS, WhatsApp, RCS and email differ in who may start a conversation, what may be said, what silence tells you and what a mistake costs. Those differences are not cosmetic." canonical: https://cpaas.co/en/learn/channels-are-not-interchangeable kind: explainer depth: foundation origin: original published: 2026-10-09T16:26:18.899Z updated: 2026-10-14T16:26:19.406Z topics: ["Fundamentals", "Messaging", "Omnichannel"] language: en --- # Channels are not interchangeable: the most common early mistake It is tempting to treat channels as interchangeable pipes: write `send(to, text)` once and pick SMS, WhatsApp or email at the last moment. That kind of shortcut is useful. It is also the source of most early trouble, because it invites you to believe the channels behind it are the same thing with different logos. They are not. They differ on four things that matter. ```diagram:compare Channel | Who may start | What silence tells you SMS | Any registered business, subject to consent | Nothing — delivered and ignored look identical WhatsApp | Only with an approved template, outside the 24-hour window | Read receipts, so silence is a real signal RCS | As SMS, where operators have launched it | Delivery and read, where supported Email | Anyone, with abuse punished later by spam filters | Open rates have been unreliable for years > Four channels, one message, four different designs. Model the differences rather than hiding them. ``` ## 1. Who is allowed to start - **SMS:** a business may start the conversation, provided it has registered its sender where the country requires it and holds the person's consent. - **WhatsApp:** a business may only start with a **template** — a message format Meta has approved in advance. A free-form message to someone who has not written to you in the last 24 hours is refused. (See [the 24-hour window](/en/learn/the-24-hour-window).) - **RCS** (the richer successor to SMS built into phones' default messaging apps): broadly the same rules as SMS, plus brand verification, and only where operators support it. - **Email:** anyone can start; abuse is punished later and quietly by spam filters. A system that models "send a message" without modelling "am I allowed to start this conversation?" works in testing and fails in production. ## 2. What may be said - **SMS** is plain text in **segments**. One segment holds 160 characters in the basic alphabet, but only 70 if the message contains characters outside it — Arabic, Hindi, Chinese, Greek, or even a single emoji. Longer messages are split and billed per segment. - **WhatsApp** templates must be approved, and the category you file them under (marketing, utility, authentication) decides the price. - **RCS** carries images, buttons and suggested replies, which changes what a "message" can be. - **Email** allows anything, which is why its filters are so strict. ```diagram:bars # Characters in one SMS segment Basic alphabet | 160 | Latin letters, digits, common punctuation Anything outside it | 70 | Arabic, Hindi, Chinese, Greek — or a single emoji > Longer messages are split and billed per segment — which is why the same notice costs more in a non-Latin script. ``` ## 3. What silence tells you On SMS, a message that was delivered and ignored looks exactly like one that was delivered and read. WhatsApp and RCS give read receipts where the user allows them. Email open rates have been unreliable since privacy features such as Apple's [Mail Privacy Protection](https://www.apple.com/newsroom/2021/06/apple-advances-its-privacy-leadership-with-ios-15-ipados-15-macos-monterey-and-watchos-8/) (2021) began loading images automatically. So any journey that waits for a reply must say what to do when nothing comes back — and the right wait differs by channel. ## 4. What a mistake costs The penalty for getting it wrong differs too, and varies by country: | Mistake | Example consequence | |---|---| | Wrong WhatsApp template category | Higher cost, or the template is rejected | | Unregistered business SMS in the United States | Blocked: carriers have rejected unregistered 10DLC traffic since February 2025 | | Unregistered sender name in Singapore | Labelled "Likely-SCAM", then blocked, under the national Sender ID Registry | | Commercial SMS in India without registered templates | Filtered out by operators' DLT checks | | Promotional SMS without the required label (some markets, such as the UAE) | A regulatory matter, not just a delivery one | See [sender registration around the world](/en/learn/sender-registration-around-the-world) for the wider picture. ## A worked example: "your order has shipped" - **SMS:** allowed if you hold consent and your sender is registered in that market. Costs more in non-Latin scripts. Arrives in seconds. You will not know whether it was read. - **WhatsApp:** needs a utility template unless the customer wrote to you in the last 24 hours. You get delivery and read receipts, and the customer can reply — often more valuable than the notification itself. - **Email:** cheap, but competing with everything else in the inbox, and the open rate does not measure what you think. - **RCS:** the same notice with a "track parcel" button where the handset and operator support it — and an SMS version for everyone else. Four channels, one event, four designs. ```diagram:matrix # "Your order has shipped", four ways SMS | Allowed with consent and a registered sender. Arrives in seconds; you will not know whether it was read. WhatsApp | A utility template unless the customer wrote in the last 24 hours. Delivery and read receipts, and the customer can reply. Email | Cheap, but competing with everything else in the inbox — and the open rate does not measure what you think. RCS | The same notice with a "track parcel" button where supported, and an SMS version for everyone else. ``` ## Build the rules in, not around The shortcut is still worth having. Just make the rules unavoidable: - **Check permission inside the send function.** It should take an intent ("shipping update"), a contact and a consent basis, and **refuse with a reason** when the combination is not allowed. - **Look up capability at send time.** Whether a number can receive RCS, or whether a WhatsApp window is open, changes from day to day. Decide when sending, cache briefly, and fall back rather than fail. - **Test it by calling it wrongly.** If the answer is "it sends anyway and we hear about it from a complaint", the rules are decoration. ```diagram:decision # What the send function decides Is this intent allowed for this contact, on this consent basis? | | Refuse, and say why Can the number receive this channel right now? | Send on it | Fall back rather than fail > The second answer changes from day to day — whether a number takes RCS, whether a WhatsApp window is open — so it is looked up when sending and cached only briefly. ``` ## Where to go next - [Choosing a channel per message](/en/learn/choosing-a-channel-per-message) — the next step in this track. - [The 24-hour window](/en/learn/the-24-hour-window) — WhatsApp's key rule, explained. - [What RCS changed](/en/learn/what-rcs-changed) — the richer successor to SMS. - [Which channel for which need](/en/learn/which-channel-for-what) — every channel compared, with a primer for each, from [SMS 101](/en/learn/sms-101) and [WhatsApp 101](/en/learn/whatsapp-101) to [Email 101](/en/learn/email-101). ## Sources [^1]: [Ten-Digit Long Code (10DLC) Registration Guidelines](https://learn.microsoft.com/en-us/azure/communication-services/concepts/sms/ten-digit-long-code-guidelines) — Microsoft Learn [^2]: [WhatsApp Business Platform pricing](https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing) — Meta for Developers [^3]: [Deadline for mandatory registration with Singapore SMS Sender ID Registry expires on 31 Jan 2023](https://cms.law/en/sgp/legal-updates/deadline-for-mandatory-registration-with-singapore-sms-sender-id-registry-expires-on-31-jan-2023) — CMS, January 2023 [^4]: [Apple advances its privacy leadership with iOS 15, iPadOS 15, macOS Monterey and watchOS 8](https://www.apple.com/newsroom/2021/06/apple-advances-its-privacy-leadership-with-ios-15-ipados-15-macos-monterey-and-watchos-8/) — Apple Newsroom, 7 June 2021 --- Published by the company behind five products in this category. Those products appear in this site's directory alongside competitors under the same published criteria and are labelled as its own. Editorial content does not recommend them.