Channels

One API. One compliance layer. Four ways to reach someone.

Your audience lists, DLT registration and delivery reporting do not change when the channel does.

DLT-registered A2P

SMS

The channel that reaches every handset in India, on every network, without an app or a data connection.

Start sending

Promotional, transactional, service and OTP
All four categories on the same connection, priced the same. We do not charge a premium for the traffic you need most.
DLT enforced before dispatch
Entity, header and template are checked against your registration. Content that does not match its template is stopped rather than gambled on.
Unicode and long messages
GSM-7 and UCS-2 detected automatically, with correct segment counting so your billing matches the carrier’s.
SMPP or REST
Bind to us with up to your contracted session count, or use the HTTP API. Same routing, same reporting.

Rich messaging on Android

RCS

Your brand name, your logo and a verified badge in the default messaging app — with SMS underneath when the handset cannot take it.

Start sending

Verified sender identity
Your business name and logo, not a six-character header. Recipients see who is writing.
Cards, carousels and suggested replies
Structured content and tap-to-reply, in the same inbox as SMS.
Automatic SMS fallback
If the handset or network cannot take RCS, the message goes as SMS. You send once.
Read receipts
Delivery and read state where the handset reports it — more than SMS can tell you.

Official Cloud API

Utility and marketing templates through the official Business API, billed per conversation rather than per message.

Start sending

Template management
Submit, track and version your templates. Approval state visible before you schedule a send.
Two-way conversations
Replies arrive on your webhook. A conversation window opens and you can respond freely inside it.
Per-conversation billing
Utility, authentication and marketing priced separately, as Meta charges them.
Media and interactive
Images, documents, buttons and list replies.

Bring your own model

AI agents

Messaging is the transport; the intelligence stays yours. An inbound reply is posted to your endpoint with the full thread, and whatever your model returns goes back out on the same channel — SMS, RCS or WhatsApp — through the same compliance checks and the same delivery reporting.

We deliberately do not host the model. You choose it, you control the prompt, and your customer data never becomes training data for someone else.

POST https://your-app.example/agent
{
  "conversation_id": "cv_8f2a",
  "channel": "whatsapp",
  "from": "919820012345",
  "message": "where is my order?",
  "history": [
    { "role": "agent", "text": "Hi! How can I help?" }
  ]
}

// reply within 20s
{ "text": "Your order ships today.",
  "handoff": false }

Full thread history on every call, so your model has context without you storing it
Return handoff: true and the conversation routes to a human
Replies pass the same DLT template and window checks as any other message
Timeouts fall back to your configured holding message rather than silence

Status: in development. Talk to us if you want to shape it — we would rather build against a real use case than guess.