Skip to content

Messaging platform

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

Delivery receipts on every message · Volume pricing

channels behind one API
2
characters per GSM SMS part
160
RCS conversation window
24h
characters per Unicode SMS part
70

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 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: SMS lands on every handset without internet, and RCS upgrades the native SMS inbox with branding and buttons. A platform that runs both 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 both channels.

Channel chooser

SMS 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 caseSMSRCS
OTPs & transactional alertsBestGood
Marketing campaignsGoodBest
Two-way customer support—Best
Rich product showcases—Best
Reach without internetBest—

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

Channels

Two channels, each with its own page

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

WhatsApp Business API is now part of DoveMesh.

Unified API

One integration, automatic fallback

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

  • Single REST API and webhook format across both channels
  • Fallback chains: RCS → SMS, set per message
  • One delivery-receipt stream and one analytics view across channels
  • Sender/template compliance applied automatically per channel
POST /v1/messages
{
  "to": "+919800000000",
  "channels": ["rcs", "sms"],
  "template": "order_shipped",
  "vars": { "order": "4821", "eta": "Thursday" }
}

Industries

Messaging that runs real businesses

The flows our customers run on this platform every day — usually across both channels at once.

01

Fintech & banking

Transaction alerts and OTPs on SMS, statements as rich RCS cards.

02

E-commerce & D2C

Order updates on RCS with SMS fallback; cart recovery on RCS.

03

Logistics

Driver assignments by SMS, delivery updates with reschedule buttons on RCS.

04

Healthcare

Appointment reminders on SMS, rescheduling with RCS suggested replies.

05

SaaS & apps

Login OTPs and security alerts on SMS, onboarding and renewal nudges on RCS.

06

Travel

Booking 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 RCS.

Which channel should I use for OTPs?

SMS is the default for OTPs: it reaches every handset without internet and delivers in seconds. Send via RCS 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 RCS from one API?

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

How is messaging billed?

SMS is billed per message part (160 GSM / 70 Unicode characters). RCS bills per 24-hour conversation for two-way sessions, with single rich messages billed individually. Talk to sales for rates by destination and volume.

Do I get delivery reports?

Yes — every message on every channel returns a delivery receipt (DLR) via webhook, with read receipts on 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: registered sender IDs and templates transfer to our routes, 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.

Volume pricing · No lock-in