Platform
API
The team runs Nandi from the dashboard. When a flow no longer belongs there, the API is the same product: a message, a signed webhook, and a wallet debit in one write.
Same objects, as code
{
"channel": "whatsapp",
"to": "+2348021149930",
"template": "order_shipped"
}WhatsApp is a connected service, not an airtime rate. SMS is billed per message.
What you get
01
The same objects
Numbers, calls, messages, contacts, routing. Not a second product with a different vocabulary.
02
Writes you can retry
Scoped keys, per-key limits, idempotency on every write, and errors you can branch on.
03
Events you can trust
Signed webhooks for calls, messages, and conversations. The ledger moves with the message.
Works with the rest of Nandi
Team-led
Messaging
WhatsApp and Telegram are free services you connect. SMS sits on the same timeline, billed per message.
Team-led
Voice
A business number for the calls you place and the calls you answer. The minute is airtime.
Team-led
Shared inbox
One shared inbox. One customer timeline. Statuses a floor can actually run.
Three steps
01
Run the center first
The dashboard is enough. Open the API when a workflow outgrows the screen.
02
Send with a key
A scoped key, an idempotency key, and the rate shown the same way the wallet shows it.
03
React to the event
A signed webhook fires. The inbox still makes sense the next morning.
Ready to run sales and support from one contact center?
Early access is open.
No credit card · Free inbox · Live in under 12 minutes