iMessage vs SMS vs RCS vs WhatsApp for business: which channel fits (2026)

How we compared the four channels

We compared the four channels on six criteria: reach, cost, what you must do before the first send, what the thread can show, rules on messaging people first, and which jobs each suits. ZeroSettle is an iMessage API: a real phone number on real iMessage, running on Apple hardware we operate for you, that your code texts customers from and hears back on through a bearer token and signed webhooks.

How we checked: ZeroSettle facts come from its API docs, homepage and terms; the rest from Apple's, Google's, Meta's, Twilio's, AWS's and four iMessage providers' own pages, all read on October 8, 2026 and listed under Sources. Twilio and AWS stand in as example providers; others price differently. We sent no test traffic on any channel for this page. More head-to-heads are in the comparisons hub.

Which channel reaches whom?

SMS is the only one of the four that reaches every mobile phone; iMessage, RCS and WhatsApp each depend on what the recipient uses.

Sources: ZeroSettle docs; Apple Support; Meta, “Per-user marketing template message limits”.

At the edge of its reach, Google's RCS API returns 404 NOT_FOUND when a recipient can't receive RCS and leaves fallback to “the fallback methods defined in your infrastructure.” ZeroSettle sends only to iMessage addresses, but you can check whether a number or email is on iMessage before texting it, and the check sends nothing. See blue vs green bubbles for business texting for why the color matters.

How do costs compare?

ZeroSettle charges a flat monthly price ($49 for one number on Pro); SMS and RCS charge per message plus carrier fees and registration fees; WhatsApp charges per delivered message, by message category and the recipient's country. Below a few thousand texts a month, SMS costs less in total than ZeroSettle's flat plan.

The cost math at small volumes

Our arithmetic, at the published rates above:

• SMS: one outbound segment to a Verizon customer costs $0.0083 + $0.005 = $0.0133, so 1,000 texts cost $13.30, plus $1.15 for the number, $46 of one-time 10DLC fees and the monthly campaign fee. Replies are billed too.
• Break-even: $49 buys about 3,680 outbound Verizon segments on Twilio, before replies and fixed fees. Below that, SMS is cheaper per message; ZeroSettle's flat price buys the blue-bubble thread, not a lower unit cost.
• RCS on AWS: fixed fees alone are $500 + $200 + 12 × $200 = $3,100 per agent in the first year.
• ZeroSettle Pro: the cap is on people, not messages: 5 new contacts a day, so at most about 150 conversations you start in a 30-day month. People who text you first don't count.

Growth, for several numbers working as one, is from $599/mo; see pricing and, for the SMS side in depth, ZeroSettle vs Twilio.

What does each require before you send?

ZeroSettle's Pro plan is self-serve in four steps with no carrier registration step; SMS, RCS and WhatsApp each need a registration or review first.

iMessage through ZeroSettle

1. Press Get started and sign in with your phone number (a one-time SMS code). A number is set aside while you finish.
2. Answer one question: what the number is for (sign in with iMessage, branded messages, or an AI agent). That claims the number.
3. Set your brand name and photo and text yourself a test message (you can skip the test and change the name and photo later).
4. Subscribe. The console and API open once the subscription is active.

Numbers can sell out (there is a waitlist). After step 4, the first send is one call with free-form text and no template:

BASE=https://portal.zerosettle.io   # ZEROSETTLE_TOKEN is read from your environment
curl -s -X POST -H "Authorization: Bearer $ZEROSETTLE_TOKEN" -H 'Content-Type: application/json' \
  -d '{"to":"+15555550142","text":"Hi Sam, this is Northside Bikes. Your repair is ready. What time suits you for pickup?"}' \
  $BASE/api/imessage/send

SMS, RCS and WhatsApp

• SMS: “Anyone sending SMS/MMS messages over a 10DLC number from an application to the US must register for A2P 10DLC” (Twilio). Sends from an unregistered 10DLC number are blocked with error 30034.
• RCS: you work through a partner such as Twilio or AWS, create an agent with a name and logo, and pass a review that “includes brand verification” plus carrier approval. “Google-managed launches take 1–3 business days” when Google's conditions are met (Google); Twilio says to “allow four to six weeks or longer” when launching in several regions, and its Messaging Services fall back to SMS or MMS when RCS fails (Twilio).
• WhatsApp: you register the number with a display name, and “Template messages generally require approval before you can send them” (Meta).

What can each do in the thread?

RCS and WhatsApp add cards, carousels and buttons; SMS carries text and MMS media. On ZeroSettle, customers on iPhone see blue bubbles, your brand name and photo, typing indicators, and tapbacks, “because every message goes through Apple's own iMessage network.”

Sources: ZeroSettle docs; Apple Support; Google RCS for Business “Send messages” and “Receive events”; Twilio “Track outbound message status” (read receipts “currently RCS and WhatsApp”); Meta “Service messages” and “Typing indicators”.

Group chats split the channels too: WhatsApp's Cloud API can “Create, manage, and message WhatsApp group conversations,” while ZeroSettle conversations are one-to-one, with group chats on the roadmap.

Who can you message first, and how often?

All four channels require consent, and each limits outreach differently: ZeroSettle by new contacts per number, 10DLC by daily segments per brand type, RCS by agent category, and WhatsApp by business-initiated users per portfolio.

On ZeroSettle, anyone who texted the line first is never limited, nor is an ongoing conversation. A send over the cap returns 429 new_contact_limit with retry_after_s.

Which channel for which job?

Pick by job: iMessage for conversations with US iPhone customers, SMS (or RCS with SMS fallback) for codes and campaigns that must reach every phone, and WhatsApp for customers outside the US.

With ZeroSettle's hosted agent, labeled “Managed by AI Agent” (Beta), “our hosted agent answers every inbound text on the group's lines, from your business context,” at one AI credit per text it sends; Pro includes 1,000 a month. Or run your own model behind the webhook. The Sign in with iMessage docs cover Firebase, Supabase, Auth0 and Clerk sessions, plus a QR-code flow for non-Apple desktops.

To run iMessage for iPhone users and SMS for everyone else, see moving business texting from SMS to iMessage. Apple's own business chat is a separate product: Apple Messages for Business vs an iMessage number.

When ZeroSettle is not a fit

ZeroSettle is the wrong channel, or not enough alone, when:

• Most of your customers use Android. “The address must be on someone's iMessage; there is no SMS or email fallback.” SMS fallback is on the roadmap. A “text us” sms: link opens the SMS app on Android, so offer email or chat there too.
• Your customers are mostly outside the US and live in WhatsApp. Use WhatsApp there.
• You run high-volume marketing. ZeroSettle's terms prohibit it, and Pro allows 5 new contacts a day. Use an SMS short code or RCS with written consent.
• You must send one-time codes to every phone. Sign in with iMessage covers iPhone users only; SMS covers the rest.
• You need group chats, video or files, rich cards, read status, or a contractual SLA. ZeroSettle has none of these. Its homepage shows “99.9% uptime” as a stat, not an SLA.

For iMessage with SMS fallback from one vendor, see the iMessage API providers comparison. If iMessage fits, get a number or read the limits and compliance docs.