Vani

Vani features

Vani features: a DLT-compliant SMS, WhatsApp and email platform, module by module

Channels, compliance, devotee lists, routing, consent, billing and the developer API — everything Vani does today, with the one module still in early access marked as such.

Request accessVani overview

What is a DLT-compliant SMS platform?

A DLT-compliant SMS platform sends SMS in India only when the message matches a template the sender has registered on a telecom operator’s DLT (Distributed Ledger Technology) portal, as TRAI rules require. Vani stores a temple trust’s DLT entity, sender headers and 19-digit template IDs, compares the registered text with each rendered message character for character, and tracks approval per telco. Vani also handles WhatsApp template approval and email deliverability.

On this page
  1. SMS & DLT compliance
  2. WhatsApp templates & two-way replies
  3. Email with bounce protection
  4. Broadcasts & devotee lists
  5. Routing & failover
  6. Consent & privacy
  7. Billing & wallet
  8. Teams, roles & security
  9. Developers & API
  10. Visual automation builder

SMS & DLT compliance Live

Everything TRAI’s DLT rules ask of a sender, kept in one place and checked before a message goes live.

Entities, headers and templates

Store your DLT entity, six-character sender headers and 19-digit template IDs for each project.

Character-for-character check

The registered template text is compared with the rendered message, so a stray “Rs.” or a missing full stop is caught before carriers reject it.

Approval per telco

See whether a template is approved on Jio, Airtel, Vi and BSNL separately.

Variable length check

Variable values longer than the 30 characters TRAI allows are flagged.

Import and export

Load headers and templates from your DLT portal’s CSV export, and export them again for your records.

OTP, transactional and promotional

Each message carries its category, matched to the right template and sender header.

WhatsApp templates & two-way replies Live

Bulk WhatsApp for temples goes out as Meta-approved templates. Vani builds them, submits them and listens for replies.

Template builder

Every Meta component type — header (text or media), body with variables, footer and buttons.

Submit to Meta, sync status

Send a template for approval from Vani; its approval status syncs back automatically.

Dynamic URL buttons

A button that opens a link built for each devotee, such as their own receipt or booking page.

CSV import

Bring existing approved templates into Vani in bulk instead of rebuilding them.

Inbound replies

Devotee replies are received in Vani and kept in that contact’s message history.

STOP handling

A STOP reply adds the number to the opt-out list, so promotional messages stop.

Email with bounce protection Live

Donor letters, annual reports and appeals, with checks that keep a trust’s domain off spam lists.

HTML and MJML composer

Write responsive email in HTML or MJML, or reuse a saved template.

Attachments

Attach PDFs and images — an annual report or a programme card — to a broadcast or a single message.

Pre-send address checks

Common domain typos and addresses whose domain has no mail server (MX record) are caught before sending.

Bounce suppression

Addresses that hard-bounce are suppressed so the next broadcast skips them.

Auto-pause on high bounces

If hard bounces climb during a broadcast, it pauses itself before your sender reputation suffers.

Unsubscribe, opens and clicks

An unsubscribe footer on broadcasts, with open and click tracking in the reports.

Broadcasts & devotee lists Live

Reusable lists that understand Indian households, and broadcasts you can schedule, pause and resume.

Family-aware de-duplication

Lists are de-duplicated on contact and name, so family members sharing one phone number or email stay on the list separately.

Merge and overlap checks

Combine lists and see how many devotees appear in more than one before you send.

Per-recipient variables

Name, seva, date or receipt number filled in for each devotee.

Schedule, pause and resume

Set a send time, pause a running broadcast if something looks wrong, and resume it later.

Per-contact history

Every message sent to a devotee, on every channel, in one timeline.

Delivery reports

Delivered, failed, opened and clicked counts for each broadcast and channel.

Routing & failover Live

Several providers behind every channel, so one provider’s outage does not stop a temple’s messages.

Priority, weighted or least-cost

Choose how each channel’s traffic is split across providers.

Automatic failover

A circuit breaker per provider moves traffic to the next route when one starts failing.

Rate caps

Limit how fast a project sends, to stay within provider and carrier limits.

SMS providers

AWS End User Messaging, Karix and TrustSignal.

WhatsApp providers

AWS, Karix, QuickReply.ai and TrustSignal.

Email providers

Amazon SES, ZeptoMail and TrustSignal.

Billing & wallet Live

Pay per message from a prepaid wallet. No published tiers; pricing is on request.

Prepaid wallet

Top up once and each message draws from the balance.

Rate cards per channel

A per-message rate for SMS, WhatsApp and email, set out in your rate card.

Per-message credits

Each message is debited from the wallet in credits, so spend is traceable.

Monthly quotas

Set a monthly volume quota for each project.

Teams, roles & security Live

Structure for a trust that runs several temples, and controls an auditor will ask about.

Company, brand and project

One company account, a brand for each temple or institution, and projects under each brand.

Live and test environments

Each project has a test side, so new templates and integrations are tried before devotees see them.

Roles

Company Admin, Brand Admin, Developer, Auditor and Viewer, plus custom roles.

Two-factor sign-in

Administrators must sign in with an authenticator app (TOTP).

Encrypted provider credentials

Provider API keys are stored with envelope encryption.

Audited support access

When our support team acts inside your account, it is recorded in the audit trail.

Developers & API Live

Integrate once with POST /v1/messages; Vani handles providers, DLT, consent and delivery reports.

One send endpoint

SMS, WhatsApp and email through one request, with OTP, transactional and promotional categories.

Scheduled sends and idempotency

Schedule a message ahead, and pass an idempotency key so a retry never sends twice.

Dry-run preflight

Check the template, suppression list, quota and route for a message without sending it.

Signed webhooks

Delivery status events posted to your server with a signature you can verify.

Docs and SDK

OpenAPI 3.1 reference, a Postman collection and a TypeScript SDK.

Sandbox test keys

Build against test keys before switching a project to live.

Visual automation builder Early access

A drag-and-drop flow builder already exists in Vani; we are connecting it to temple events. Ask us for early access.

Triggers, waits and conditions Early access

Start a flow, wait, and branch on what happened.

Multi-channel steps Early access

Mix SMS, WhatsApp and email in one flow.

Wait for a reply Early access

Branch a flow on a devotee’s WhatsApp reply.

FAQ

Frequently asked questions

Something else? Write to [email protected] or book a demo.

What does “DLT-compliant” mean for a temple?

It means every SMS the temple sends matches a template registered on DLT under the trust’s own entity and sender header, as TRAI requires. Vani checks the text before it goes live. Our DLT registration guide explains how a trust registers.

Can Vani import our existing DLT templates?

Yes. Vani imports sender headers and templates from your DLT portal’s CSV export, and can export them again.

How does Vani stop emails from bouncing?

Vani checks each address for common typos and a working mail server before sending, suppresses addresses that hard-bounce, and pauses a broadcast by itself if hard bounces climb.

What happens if an SMS provider goes down?

A circuit breaker on each provider moves new messages to the next route automatically. You choose priority, weighted or least-cost routing per channel.

Is the automation builder available?

It is in early access. The visual builder exists in Vani, and we are connecting it to temple events. Ask us if you would like to try it.

Can our developers test without sending real messages?

Yes. Every project has sandbox test keys and a test environment, and the send API has a dry-run mode that checks a message without sending it.

See Vani with your own DLT templates

Send us your DLT export and a sample devotee list. We will load them into a test project and walk you through a broadcast.

  • Pay per message, prepaid wallet
  • Pricing on request
Request accessSee Vani pricing