Home Channels RCS

RCS.

Ship RCS from the same place you ship push, email, and SMS. No new vendor, no separate user database.

Read rate

~92%

Avg CTR

14.5%

Brand trust lift

+38%

The anatomy of a Rich Card message.​

Seven pins, seven decisions.

Tap any pin to open

The anatomy of a Rich Card message.

Tap any pin to open

Built for RCS. Backed by the platform

Build rich RCS campaigns with cards and carousels. Showcase multiple products in a swipeable format, each with images, pricing, and action buttons like Buy Now or View Details.

Integrate with all the top RCS providers, including Sinch, Infobip, and Jio. Connect your preferred provider and launch RCS campaigns without custom development.

Send Intelligently delivers each message at the time every recipient is most likely to engage. Instead of one send time for all, it optimizes delivery per user for higher engagement.

Track conversions by defining a goal event. See which touchpoint drove the conversion across channels, giving credit to the campaign that actually earned it.

Define several conversion events and see how each variation performs against every goal, alongside aggregate conversions and total revenue.

Built for RCS. Backed by the platform.

RCS Features

Native to this channel

Cards & Carousels
Build rich RCS campaigns with cards and carousels. Showcase multiple products in a swipeable format, each with images, pricing, and action buttons like Buy Now or View Details.Measure overall click performance of your SMS campaign. Track total and unique clicks on your link to understand how recipients engage with your message.
Integrate with all the top RCS providers, including Sinch, Infobip, and Jio. Connect your preferred provider and launch RCS campaigns without custom development.

Platform Features

Available everywhere relevant to Mobile too

Send Intelligently

Send Intelligently delivers each message at the time every recipient is most likely to engage. Instead of one send time for all, it optimizes delivery per user for higher engagement.

Track conversions by defining a goal event. See which touchpoint drove the conversion across channels, giving credit to the campaign that actually earned it.
Define several conversion events and see how each variation performs against every goal, alongside aggregate conversions and total revenue.

What's new for RCS teams.

Product Updates

WebEngage Is Now Salla Platform Native – Asia’s #1 CEP Joins Hands With GCC’s Largest E-commerce Platform

Salla is one of the largest commerce platforms in the GCC region, built specifically for merchants in the Middle East…

Read the announcement

Product Updates

Analytics Digest – Introducing Multi-splits in Event Analytics, Choose Between Uniques/Occurrences In Funnels, Hold Property Constant In Funnels & Compare Funnels Across Time Periods

WebEngage is rapidly becoming the de-facto Analytics toolkit for its customers across product and growth teams. As our usage grows…

Read the announcement

Product Updates

Introducing Entity Relationship Visualizer – Manage Relationships Between Your CDPx Data Objects In A Visual Interface

Last year, we launched a composable version of our Customer Data Platform; CDPx, and introduced Entities – a simple way…

Read the announcement

See All Releases

See the anatomy of the other six.

The WebEngage channel atlas

Email.

Web.

Mobile.

Ads.

Whatsapp.

SMS.

All Channels.

See the anatomy of the other six.

The WebEngage channel atlas

Web.

Email.

Mobile.

Ads.

Whatsapp.

SMS.

View all channels

FAQs

Yes. WebEngage integrates with RCS Service Providers including Sinch, Infobip, Tanla, TrustSignal, Karix, RouteMobile, and Jio, selected under Data Platform, Integrations, RCS Setup. You keep your provider relationship rather than being tied to one RCS vendor.
See docs →

RCS requires business verification before you can launch, which reduces spam and phishing risk and is a mandatory step. Plan verification lead time into your go-live, as it happens with your RSP and the RCS ecosystem.
Read more →

RCS templates are pre-approved message formats you create with your RCS Service Provider (RSP), then upload into WebEngage where each is mapped to its RSP.
See docs →

RCS availability depends on device and market. It is currently available on Android and iOS. Reach is therefore narrower than SMS today, so treat RCS as a premium channel for eligible users rather than universal coverage.
Read more →

RCS supports rich, actionable messages including rich cards and carousels through the connected provider, going beyond plain SMS text. Exact element support follows your RSP payload capabilities.
See docs →

Give your SMS the upgrade
it's been waiting for.

Back to Products

platform

Platform

Zero PII

No personal data stored.

AI-Powered

Atlas AI

AI-powered customer engagement suite.

Back to Products

Capabilities

Customer Data Platform

Your schema, your engagement rules

Automation

Automate workflows, orchestrate growth

Segmentation

Precise user segmentation, simplified

Personalization

Smarter web and app personalization

Analytics

Deeper analytics, sharper decisions

Recommendations

Context-aware recommendations that sell

Back to Products

channels

IVR, Chatbot, & more

Back to Products

Solutions

Travel & Hospitality

Healthcare

Automotive

Insurance

E-commerce and Retail

Back to Products

Resources

Product Releases

Ebooks

Blogs

Newsroom

Webinars

EngageMint

Impact Stories

Glossary

FEATURED

Featured Release

Introducing Entity Relationship Visualizer – Manage Relationships Between Your CDPx Data Objects In A Visual Interface

Read more

Upcoming Webinar

Winning Back Users: Proven Retargeting & Deep Linking Strategies.

Register now

Products

Platform

Zero PII, Black, Composable CDP

Capabilities

CDP, Segmentation, Analytics & more

Channels

Mobile, Email, WhatsApp, SMS & More

Solutions

BLACK

Resources

Request a Demo
Login

A picture of the jacket, in the message

The hero image; a photo of the Marlow Jacket sits inline in the message, rendered natively in Emma’s messaging app. No link, no preview placeholder, no extra tap. Image URLs can be personalized per user, so Emma sees the exact color and size she viewed, pulled from her last browse event. For richer launches, RCS also supports up to 10 scrollable product cards in one message.

Inline images

High-resolution images render inline in the messaging app- no link, no preview placeholder. Recommended file size: 40-100 KB to keep load fast and delivery reliable across carriers and devices.

See docs

Dynamic image URLs

Use merge tags inside the image URL to deliver per-user creative- last viewed product, regional banner, loyalty-tier visual. Emma sees the Marlow she actually looked at, not a generic hero image.

See docs

Up to 10 product cards

Need to show variants, a collection, or a category? A Rich Carousel stacks up to 10 scrollable product cards in one message, each with its own image, copy, and buttons.

See docs

02/06

Previous

Next

Lumen Atelier- verified, not unknown.

The header shows Lumen Atelier with a verified badge, not a short code, not “Unknown Sender.” RCS requires every brand sending messages to go through Google’s brand verification (RBM) and the RSP’s onboarding before a single template can ship. Once verified, every campaign carries the badge automatically. Emma sees who’s sending before she reads a word, and nothing on this surface can be spoofed by a third party.

Verified Business Profile

Your logo, brand name, and verified badge appear on every RCS message. Recipients see who’s sending before they read the first word, the same trust signal as a verified email sender or an Apple Verified Business.

See docs

No short codes

Brand name in the header, not a 5-digit number or generic alphanumeric sender. The same trust signal Emma uses to evaluate an email now works on her primary messaging app.

See docs

+38%

Avg brand trust lift vs SMS (source: Google RCS research)

01/06

Previous

Next

Emma, the Marlow's back.

The title and body aren’t typed. “Emma” is a merge tag from her profile, “Marlow” is the last product she viewed, and “size (M)” and “just 12 left” pull from her cart and live inventory data.

Generous character budget

Up to 4096 characters in title and body (varies slightly by RSP),roughly 26× the 160-character SMS limit. Room for context, urgency, and product detail without splitting into multiple sends.

See docs

Cross-channel merge tags

Same merge syntax as SMS, email, push, and WhatsApp. Emma’s first name, last product, cart state, and inventory levels all resolve at send time, defined once in the user profile, reused across every channel.

See docs

03/06

Previous

Next

Shop now. Two taps, no app switch.

The buttons aren’t links pasted into a paragraph, they’re native interactive elements rendered by the messaging app. Emma can tap “Shop now” to open the Marlow product page, or “View cart (3 items)” to deep-link straight to her cart. Each tap is captured as a campaign event in her profile, attributable to this exact send, and available for Journey logic to branch on i.e. which button did she tap, and what should happen next?

Three action types

WebEngage supports the three most-used RCS button types: OPEN_URL (open a link), CALL_PHONE_NUMBER (place a call), and SUGGESTED_REPLY (send a predefined reply back to the sender). Up to 4 buttons per Rich Card or carousel card.

See docs

Click attribution

Every button tap is captured as a campaign event in the user’s profile i.e. which button, when, on which campaign. Reports show CTR per button, so you know whether “Shop now” or “View cart” did the work.

Branch on which button

Did Emma tap “Shop now” or “View cart”? Different journeys for each. Did she tap nothing for 24 hours? Queue a WhatsApp follow-up. The RCS isn’t a dead-end, it feeds the next step.

Read More

14.5%

Avg click-through rate for RCS rich cards (industry benchmark)

04/06

Previous

Next

What it took to ship this card.

RCS templates can’t ship the moment a marketer writes them. Every template: the text, image, buttons, merge tag positions, has to be pre-approved by your RSP (RCS Service Provider) before it can go live, with a typical turnaround of 24–48 hours.

Per-template approval

Every RCS template is pre-approved by your RSP before it can be used in a campaign, typically 24–48 hours per template. This prevents spam and keeps your verified status intact at the carrier. Plan template work into your campaign timeline, not as an afterthought.

See docs

Choose RSP per template

WebEngage integrates with multiple RSPs for regional reach. Pick the right RSP for each template based on which markets, languages, or operators you need to cover.

See docs

05/06

Previous

Next

Did Emma read it? Yes, at 9:16 AM.

RCS, unlike SMS, provides full delivery telemetry: sent, delivered, read, failed. Every state is captured by WebEngage, written to Emma’s profile as a campaign event, exposed in reports, and available as a Journey branch condition. Did Emma read within an hour? Different next step. Did delivery fail because her device doesn’t support RCS or she’s off-network? Configure an SMS fallback in the Journey, so she still gets the message.

Full delivery telemetry

Sent, delivered, read, failed, every state captured per message, written to the user’s profile as an event, and exposed in campaign reports. Compare to SMS, where “delivered” is often the last data point you get.

See docs

Branch on every state

Configure journey branches on any delivery state. Read within an hour? Send a follow-up offer. Delivery failed? Route the user down a different path. Different state, different next step.

Read More

Configurable SMS fallback

When RCS delivery fails, the user doesn’t have to fall off the map. Add an SMS fallback step in your Journey, so the message still lands, just on a less rich channel.

~92%

Avg RCS read rate (industry benchmark, higher than email)

06/06

Previous

Next