SMS is a short plain text. It fits a code, a one-line alert, or a message that has to arrive even when the phone cannot show anything richer. RCS is a message in the phone’s messaging app that can carry more than that text: a card, an image, and a button the person can tap.
RCS replaces SMS when the message needs that card and the recipient’s phone can show it. It does not replace SMS on every phone. When the phone cannot show RCS, the same notice can go out as plain SMS. The person still gets the text. They do not get the card.
Key takeaways
RCS is a phone message with a card, media, and buttons. SMS is the plain-text version of a notice.
Use RCS when the recipient’s phone can show the card and the message needs an image or a tap.
Use SMS when the phone cannot show RCS, or when a short plain text is enough.
A verified sender shows the business name and logo in the message header after verification is done.
A button records a tap. It does not, by itself, prove a purchase, a confirmed appointment, or a completed survey.
Open rate, click rate, and read rate are not results this article is reporting.
What an RCS message contains
An RCS message can include pieces a plain text cannot hold in the same screen.
A card with an image and a short description, such as a product or an order.
A row of cards the person can scroll, when there is more than one item to show.
Up to four action buttons, such as confirm, reschedule, track, or call.
Suggested replies, so the person taps an answer instead of typing one.
A file or a location, when the message needs that attachment.
SMS can carry the words and a link. It cannot show that card inside the message. If the point of the message is the image or the button, the SMS version is a shorter stand-in, not the same message.
What the recipient sees
Before the card, the recipient sees who sent it. After the business is verified, the header can show the brand name, the logo, and a verification badge. That is the difference between a named sender and a message from a number the person does not recognize.
Verification is a setup step with the carrier. Until it is done, the rich card can still be sent, but the header is not yet the verified brand. Do not describe an unverified sender as a trusted badge.
When the phone supports it, the sender can see that the message was delivered and that it was opened. A missing receipt means the phone did not report one. It does not mean the person ignored the message.
When RCS is the right send
Send RCS when both of these are true: the phone can display it, and the plain text would drop the part the person needs to see or tap.
An order notice that should show the item and a tracking button.
An appointment reminder with confirm and reschedule buttons.
A short survey with suggested replies.
A product message with one card per item, when the image is the point.
The button label should be the action the business can actually take. A “Buy” button that does not open a real checkout is a dead end. A “Confirm” button should record that tap against the appointment or the order it belongs to.
When SMS stays
SMS stays in three cases.
The phone cannot show RCS. The fallback is the plain text, with the essential fact and a link if the card cannot travel.
The message is a short code, a one-time password, or a one-line alert. A card does not help.
The rich version is not ready: no image, no verified name, or no button that goes anywhere. A plain text is clearer than an empty card.
The fallback text has to stand alone. Write it as if the card will not be there, because on some phones it will not.
How the two sends stay separate
The message | RCS | SMS |
|---|---|---|
One-time code or one-line alert | No card needed | Send the text |
Order notice with a product image | Card plus a tracking button | Text and a link, if the phone cannot show the card |
Appointment reminder | Confirm and reschedule buttons | The time, the place, and a link to change it |
More than one product | A scrolling row of cards | One text, or do not send the catalog as SMS |
Phone cannot show RCS | Do not leave the person with nothing | Send the fallback text |
Reply the buttons do not cover | Hand the thread to a person | The text has no thread to continue |
What a tap should record
A finished send needs an outcome the team can filter.
Sent as RCS, and the phone accepted the card.
Sent as SMS, because the phone could not show RCS.
Button tapped, and which label.
Suggested reply chosen.
No tap, which is not the same as a refusal.
Handed to a person, with the message and the reply attached.
A tap is the record. It is not a sale, a kept appointment, or a finished survey unless a later step stores that result.
Where a person steps in
The card handles the choice the buttons already list. A person takes over when:
The reply is a complaint, or it does not match a suggested answer.
The tap asks for a change the button is not allowed to make.
The order, the appointment, or the survey answer looks wrong.
The person asks to talk to someone.
The person should see the card that was sent, the button that was tapped, and any reply text. They should not ask the customer to describe the message again.
What this is not
RCS does not, by itself, prove a higher open rate, a higher click rate, more replies, fewer missed appointments, or a larger order. Those depend on the list, the offer, and whether the phone showed the card. Treat RCS as a richer message for phones that can display it, not as a measured lift over SMS.
The same limit applies to read receipts and to fallback. A receipt is a report from the phone, not proof of a sale. Fallback means the plain text can still go out. It does not mean every person saw the card.
RCS is also not WhatsApp, and it is not a phone call. It appears in the phone’s messaging app. WhatsApp is a separate app. A voice agent speaks. This message is something the person reads and taps.
Explore Fonada
RCS messaging for cards, buttons, a verified sender, and SMS fallback
SMS vs RCS for what a text can carry and what a card can carry