SMS.

Lands on every phone – no app, no internet needed. WebEngage runs it inside your journeys, not as a parallel CPaaS account.

Delivery rate

98.5%

Integration Partners

40+

The anatomy of an SMS message.​

Seven pins, seven decisions.

Tap any pin to open

The anatomy of an SMS message.

Tap any pin to explore

Four surfaces, one message

Built for SMS. Backed by the platform

Measure overall click performance of your SMS campaign. Track total and unique clicks on your link to understand how recipients engage with your message.

Connect with 50+ SMS providers out of the box. Integrate your preferred RSP in a few clicks and start sending campaigns without any complicated development.

See total SMS sent versus delivered so you know exactly how many message parts went out and can manage sending costs accurately.

Prevent message fatigue by capping how many messages users receive. Set daily, weekly, and monthly limits plus minimum time gaps, per channel or combined across all.

Set Do Not Disturb time slots to avoid messaging users during odd hours. Messages are held during DND and delivered once the window ends.

Personalize messages with dynamic fields like name, order ID, and status. Insert placeholders into your template and each recipient sees content tailored to their own data.

Built for SMS. Backed by the platform.

SMS Features

Native to this channel

Click Tracking
Measure overall click performance of your SMS campaign. Track total and unique clicks on your link to understand how recipients engage with your message.
Connect with 50+ SMS providers out of the box. Integrate your preferred RSP in a few clicks and start sending campaigns without any complicated development.
See total SMS sent versus delivered so you know exactly how many message parts went out and can manage sending costs accurately.

Platform Features

Available everywhere relevant to Mobile too

Frequency Capping
Prevent message fatigue by capping how many messages users receive. Set daily, weekly, and monthly limits plus minimum time gaps, per channel or combined across all.
Set Do Not Disturb time slots to avoid messaging users during odd hours. Messages are held during DND and delivered once the window ends.
Personalize messages with dynamic fields like name, order ID, and status. Insert placeholders into your template and each recipient sees content tailored to their own data.

What's new for SMS teams.

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…

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…

See the anatomy of the other six.

The WebEngage channel atlas

See the anatomy of the other six.

The WebEngage channel atlas

Web.

Email.

Mobile.

Ads.

Whatsapp.

RCS.

View all channels

FAQs

You bring your own SMS Service Provider. WebEngage integrates with 40 plus SSPs including Twilio, Exotel, Plivo, MSG91, Infobip, plus a Private SSP option. SSPs act as the middlemen carrying messages from WebEngage to mobile operators, so you keep your aggregator and its rates.
See docs →

WebEngage supports the TRAI DLT regime. You register your entity for a PE ID, register your sender IDs or headers as transactional or promotional, and whitelist templates for Template IDs, with both PE ID and Template ID passed in each message payload or delivery fails. WebEngage can enable PEID and TemplateID fields on your configuration for Indian sends.
See docs →

Yes. WebEngage guides you through TRAI's mandate for whitelisting links and CTAs used in SMS, so URLs and callbacks in your templates need to be registered to pass DLT scrubbing.
See docs →

Your SSP sends delivery status notifications to WebEngage through a webhook URL, so statuses such as sent, delivered, failed, and queued are tracked under campaign stats. This gives you per-message delivery reporting inside the dashboard.
See docs →

SMS content personalizes using tracked user attributes and custom event properties through tokens, for example a user first name or an order ID from an event. Content stays within DLT template constraints for Indian users.
See docs →

SMS is billed per part, not per message: longer messages or emojis split into multiple parts carriers charge for individually. WebEngage surfaces an SMS Part Count that aggregates the actual number of parts from the delivery receipts your SMS provider returns, giving you a transmission-accurate figure to reconcile against the provider invoice.

Every link in SMS, WhatsApp, RCS, and Viber campaigns can be automatically shortened by WebEngage so clicks are tracked and rolled into campaign analytics, giving click-level visibility on channels that otherwise offer little native measurement.

Make SMS a step in your customer journey, not a standalone blast.

platform

Platform

Zero PII

No personal data stored.

AI-Powered

Atlas AI

AI-powered customer engagement suite.

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

Solutions

Travel & Hospitality

Healthcare

Automotive

Insurance

E-commerce and Retail

Resources

Product Releases

Ebooks

Blogs

Newsroom

Webinars

EngageMint

Impact Stories

Glossary

FEATURED

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

Winning Back Users: Proven Retargeting & Deep Linking Strategies.

Products

Platform

Zero PII, Black, Composable CDP

Capabilities

CDP, Segmentation, Analytics & more

Channels

Mobile, Email, WhatsApp, SMS & More

Solutions

BLACK

Resources

Every word earned its place.

The full message “Hi Emma…” counts 08 characters. That’s one part, one bill, one delivery. SMS bills per 160-character part (70 if you add an emoji or non-Latin script). Cross 160 and it silently becomes two parts; cross 320 and it’s three. WebEngage’s composer shows live part count and encoding as you type, and lets you preview the rendered message against any user in your audience before launch.

Live length preview

See part count and encoding update as you type. Switch the preview to any user in your audience and the count recalculates with their actual data, so you can check whether a long first name or product title pushes you over 160.

Per-part billing visibility

Reports show how many parts actually sent per user, so when finance asks why the SMS bill tripled, you have the answer in two clicks instead of a week of reconciliation.

160

Characters in a single GSM-7 SMS (70 with emoji or non-Latin scripts)

Sender ID: what shows up at the top.

The recipient sees the brand the second the SMS lands, not a random ten-digit number that looks like spam. WebEngage routes each campaign through the right Sender ID and handles the regional registration, including India’s DLT portal, so messages aren’t blocked at the carrier.

Alphanumeric headers

The recipient sees LUMEN, not a number. Trust shows up before the message is read, and an SMS from a recognized brand gets opened far more often than one from a stranger.

Numeric short codes for transactional

OTPs, order alerts, and shipping updates go through short codes (like 57575), higher deliverability than long codes, and carriers don’t throttle them during peak periods.

DLT-compliant sending

India’s DLT rules require every Sender ID and message template to be pre-registered with the carriers (Jio, Airtel, Vi, BSNL) before SMS can be sent. WebEngage validates every outgoing message against your registered template at send time, so anything that doesn’t match gets caught before it hits the carrier and fails silently thereby protecting your delivery rate, not just your peace of mind.

01/04

Hi Emma, the Marlow you viewed.

The “Hi Emma” isn’t typed. It’s a merge tag pulling Emma’s first name from her profile, and “Marlow Jacket” is the product name from her last browse event, slotted into the template text around it. Same merge syntax as every other channel: one user profile feeds push, email, WhatsApp, and SMS without remapping fields per channel. For Indian transactional sends, WebEngage attaches your registered PE ID and DLT Template ID to every outgoing message, so carriers can match against your registered templates during scrubbing.

Dynamic Merge Tags

Drop any user data or recent behavior into the message- name, last product, order ID, loyalty tier, and it fills in per person at send time.

Template ID tagging

For Indian transactional SMS, WebEngage attaches your registered PE ID and DLT Template ID to every outgoing message. You select the right template at campaign-build time; carriers do the final scrubbing against your registered templates.

One profile, every channel

The same user attributes, events, and merge syntax work across SMS, push, email, and WhatsApp. Define the user model once and channels reuse it without re-mapping fields per channel.

The link is the whole point

SMS has no buttons, no images, no carousel. The link is the only thing that drives action, and it has to fit inside the same 160-character budget as the message. By default, WebEngage shortens every link to weurl.co/[var] (~18 characters). Brands that want their identity on the link can configure a custom short path. Every tap is captured, attributed back to the campaign, written to Emma’s profile as an event, and available for Journeys to branch on; did Emma tap or not?

Auto-shortened, fully tracked

Long URLs eat your character budget and lose attribution. WebEngage shortens every link to ~18 characters and tracks each tap back to the user and campaign, no third-party shortener, no broken attribution chain.

Branch on tap or no tap

If Emma tapped, send her down the post-click flow. If she didn’t, queue a WhatsApp follow-up the next day. The SMS isn’t a dead-end channel; it feeds the rest of the journey.

Read More

04/04