Skip to content
Launch offer — free domain with annual hosting, GST invoice included.Claim

Messaging platform

Every messaging channel. One API.

Send the same alert as a plain SMS, a WhatsApp message or a rich RCS card — one integration, automatic fallback, DLT handled, unified delivery analytics.

DLT support · INR billing · Delivery receipts on every message

3

channels behind one API

160

characters per GSM SMS part

2B+

users reachable on WhatsApp

24h

RCS & WhatsApp conversation window

What is a business messaging platform?

A business messaging platform sends A2P (application-to-person) messages — OTPs, order updates, reminders, campaigns — and receives customer replies, across SMS, WhatsApp and RCS from one system. Under the hood it manages the parts that make messaging hard: sender registrations, template approvals, carrier routing, retries, delivery receipts and the 24-hour conversation windows that rich channels bill by.

Reach is the reason messaging outperforms every other channel in India: SMS lands on every handset without internet, WhatsApp is the country's default chat app, and RCS upgrades the native SMS inbox with branding and buttons. A platform that runs all three lets you match the message to the moment — and fall back automatically when a channel can't deliver.

Everything on this page rolls up to one integration: one API to send, one webhook for replies and receipts, one dashboard for campaigns and analytics across all three channels.

Channel chooser

SMS vs WhatsApp vs RCS — which channel when?

Every A2P messaging channel has a job it does best. Match the message to the channel, and let fallback cover the gaps.

Use caseSMSWhatsAppRCS
OTPs & transactional alertsBestGoodGood
Marketing campaignsGoodBestBest
Two-way customer supportBestGood
Rich product showcasesGoodBest
Reach without internetBest

“Best” reflects typical delivery, engagement and cost per use case — your mix may differ; we'll help you model it.

Channels

Three channels, each with its own page

Deep-dive into the channel you need — capabilities, compliance and pricing units are different on each.

Unified API

One integration, automatic fallback

Define the message once and set a channel chain. If the handset can't receive RCS or the user isn't on WhatsApp, the same message lands as SMS — no second integration, no dropped alerts.

  • Single REST API and webhook format across all three channels
  • Fallback chains: RCS → SMS, WhatsApp → SMS, or any order you choose
  • One delivery-receipt stream and one analytics view across channels
  • DLT template mapping applied automatically on the SMS leg
POST /v1/messages
{
  "to": "+919800000000",
  "channels": ["rcs", "whatsapp", "sms"],
  "template": "order_shipped",
  "vars": { "order": "4821", "eta": "Thursday" }
}

Industries

Messaging that runs real businesses

The flows Indian businesses run on this platform every day — usually across two or three channels at once.

Fintech & banking

UPI alerts and OTPs on SMS, statements and support on WhatsApp — compliance-clean on both.

E-commerce & D2C

Order updates on RCS with SMS fallback; abandoned-cart nudges and COD confirmations on WhatsApp.

Logistics

Driver assignments by SMS, live delivery conversations with customers on WhatsApp.

Healthcare

Appointment reminders on SMS, report delivery and rescheduling over WhatsApp chat.

Education

Fee reminders and exam alerts to parents on SMS, admission counselling on WhatsApp.

Travel

PNR confirmations on SMS, boarding passes and gate changes as rich RCS cards.

FAQ

Messaging questions, answered

Channel choice, fallback and how the billing units actually work.

What is A2P messaging?

A2P (application-to-person) messaging is any message a software system sends to a person — OTPs, delivery alerts, reminders, promotions. The reverse direction, P2A, is what enables two-way conversations on WhatsApp and RCS.

Which channel should I use for OTPs?

SMS is the default for OTPs: it reaches every handset without internet and delivers in seconds. Pair it with a voice-call fallback for noisy destinations, or send via RCS/WhatsApp first and fall back to SMS to cut costs on smartphone-heavy user bases.

What is channel fallback?

A priority chain you set per message — for example RCS first, then SMS. If the recipient's handset or carrier can't receive the richer channel, the platform automatically re-sends on the next channel, so the alert always lands and you only pay for what's delivered.

Can I send SMS and WhatsApp from one API?

Yes. One REST endpoint, one authentication scheme and one webhook format cover SMS, WhatsApp and RCS. Switching a flow from SMS to WhatsApp is a field change, not a new integration.

How is messaging billed?

SMS is billed per message part (160 GSM / 70 Unicode characters). WhatsApp and RCS bill per 24-hour conversation for two-way sessions, with single rich messages billed individually. All rates in ₹ with GST invoices — talk to sales for your volumes.

Do I get delivery reports?

Yes — every message on every channel returns a delivery receipt (DLR) via webhook, with read receipts on WhatsApp and RCS. The dashboard aggregates them into per-campaign delivery, read and click rates, and you can export or stream the raw events into your own analytics.

Can I migrate from my current messaging provider?

Yes, and it's routine: your DLT entity, headers and approved templates transfer to our routes, WhatsApp numbers move via Meta's provider-migration process, and we run both providers in parallel during cutover so no OTP is ever dropped.

Pick a channel — or let fallback pick for you

Tell us your use case and monthly volumes; we'll recommend a channel mix and send the rate card.

DLT guidance included · GST invoice