What Boni CPaaS Is
Boni CPaaS is a campaign and outreach platform from Boni — the same company that builds Bow Chat and Bino.
It lets you send WhatsApp Business messages and email at scale: to customers, partners, leads, suppliers, or candidates. But unlike a simple bulk sender, it is built around compliance. Every send goes through a chain of controls — approved templates, suppression checks, throttling, canonical campaign identity, and provider-level delivery telemetry — before and after the message leaves.
Some parts — particularly the customer self-serve setup flow and the SMS and RCS channels — are still in development. This article says so plainly where that is the case.
The Problem It Solves
Sending a few hundred WhatsApp messages is easy. You open the app, send them one by one, and it works.
Sending ten thousand messages — to a partner list, a customer segment, a procurement list — breaks down fast.
The problems are predictable. You send from a number that is not meant for bulk use and it gets flagged or banned. You re-send to someone who already opted out. You have no way to know whether the message was delivered, read, or ignored. You run a big send and realise halfway through that half the addresses are stale. You have no audit trail if anyone asks what was sent, to whom, and when.
Email has the same problems plus its own set: your sender domain gets blacklisted because you sent from a mailbox that was not set up for bulk, your messages land in spam because there is no SPF/DKIM/DMARC on the domain, you have no way to track opens or clicks, and you have no suppression list so you keep emailing people who bounced months ago.
Boni CPaaS is built to handle all of this in one place, across both WhatsApp and email.
How It Works in Plain Words
Campaigns start with a canonical identity
Every send — whether it is a WhatsApp broadcast, an email campaign, or a follow-up step — must be registered as a campaign before dispatch starts. That means a stable campaign ID, a source reference, and one recipient row per real recipient. Nothing goes out without this identity in place.
This matters because it makes every send traceable. If you need to check what happened, find a specific message, reconcile a reply, or pull a delivery report six weeks later, you can do it because every send is tied to a campaign and a recipient.
WhatsApp: approved templates, the right number, throttled dispatch
WhatsApp Business only allows outreach outside an active conversation if you use a pre-approved template. Boni CPaaS enforces this. You pick an approved template, Boni routes the send through the correct WhatsApp Business number for your use case, and dispatch runs in batches with throttling — so you do not hit provider rate limits or trigger spam signals.
Boni manages multiple WhatsApp numbers for different purposes — customer outreach, partner communication, HR, and others. The routing policy determines which number gets used for which type of send. You do not choose the raw phone number yourself; you configure the purpose and the system picks the right sender.
Reply events flow back into Bow Chat, Boni's conversation platform. When a recipient replies to a WhatsApp campaign message, that reply is attributed back to the campaign and appears in the inbox. You can hand it off to a human agent, let a bot continue, or mark it as a goal completion.
Email: sender domains, templates, and provider-level authentication
For email, Boni CPaaS uses a dedicated sending infrastructure — not a personal mailbox, not a shared relay, not a consumer email client. Each sending subdomain goes through full DNS authentication: SPF, DKIM, and DMARC enforced. This is the baseline requirement before any external send is allowed.
When you set up an email campaign lane, you create a sender domain setup (for example campaign.yourcompany.com), a brand kit with your logo and company details, a sender identity, and a template version. The platform checks that all of these are approved and verified before it will submit a single message to the provider.
Templates go through an approval step. Unapproved templates are blocked. Templates that are missing required variables are blocked. Sender identities that are not verified are blocked. These are hard stops, not warnings.
Once a send is approved, messages go through a managed relay, not a self-hosted mail server. Delivery events — accepted, delivered, opened, clicked, bounced, complained, unsubscribed — come back from the provider and are recorded against the campaign and recipient row.
The email layer also has a sender readiness gate. Before any new sender lane can reach real external recipients, it must pass: DNS verification, a reachable reply path, postmaster and abuse addresses set up, unsubscribe headers configured, and a seed message that lands in the inbox (not spam) at a test mailbox. If the seed lands in spam, external sending stops until the lane is fixed.
Suppression runs before every send
Suppression is not an afterthought. Before each message is dispatched, the platform checks a central preference and suppression ledger. If a recipient has hard-bounced previously, unsubscribed, complained, or been explicitly blocked, the message is suppressed and the suppression is logged.
For email, active suppressions per campaign are visible in the delivery report. For WhatsApp, the system checks a business preference store before dispatch and skips opted-out contacts.
The goal is a single suppression decision that applies across channels. As of now, this is implemented for email and partially for WhatsApp. Extending the same gate uniformly to all channels — SMS, RCS, voice — is on the active product roadmap.
Delivery telemetry, not guesses
Every send generates a delivery trail. For email: accepted, delivered, opened, clicked, replied, bounced, complained, or unsubscribed — with timestamps and provider message IDs. For WhatsApp: sent, delivered, read, failed — tied back to the campaign recipient row.
This is the evidence layer. If someone asks whether a message was delivered, you do not have to rely on "we sent it." You can pull the delivery record with provider ID and timestamp.
Open and read signals are engagement indicators, not guaranteed proof that a human read the message. Click, reply, and action-completion signals are stronger. The platform treats them differently in reporting.
Campaign reports are accessible through Boni's control panel. Recipient-level drilldowns, export, and domain health checks are available. The panel is actively being improved; some views are still internal-grade rather than polished customer-grade.
What You Can Do With It
WhatsApp partner and customer outreach
Send approved WhatsApp template messages to a list of customers or partners. Set the pace — Boni throttles the send in batches so it does not look like a flood to the provider. Track delivery and read signals. Replies land in Bow Chat for follow-up.
Email lifecycle campaigns
Set up a dedicated sending subdomain for your brand. Build a template with your logo, copy, and personalisation variables. Send to a CRM-sourced list. Track who received it, who opened it, who clicked, and who bounced. Suppressions are enforced automatically.
Supplier and procurement outreach
Bino uses Boni CPaaS internally for supplier RFQ outreach — sending quote-request emails to suppliers at scale, with reply routing back to a monitored inbox. The same lane is available for any structured procurement workflow.
Transactional notifications
Order confirmations, ticket receipts, payment reminders, and subscription notices can run through Boni CPaaS as transactional sends — dedicated sender identity, brand kit, template, and delivery confirmation per message.
Multi-step follow-up sequences
After an initial campaign send, a no-reply follow-up can be scheduled automatically. If the recipient replies to the first message, the follow-up is cancelled. If not, it fires after the configured window. This is the beginning of a sequence/journey builder; the full visual journey editor is still on the roadmap.
Who It Is For
Boni CPaaS is a fit for Indian businesses and teams that:
- need to send WhatsApp or email at scale without managing raw provider accounts or handling compliance themselves
- have real outreach use cases — partner acquisition, customer lifecycle, procurement, HR recruiting — where a few dozen messages a day is not enough
- want delivery evidence and suppression, not just a sent count
- are using or considering Bow Chat as their conversation platform and want campaigns and replies to live in the same place
It is not the right fit for someone who only needs to send a handful of messages a week and has no compliance or deliverability concerns. A regular WhatsApp Business account handles that fine.
What Is Still Being Built
Some things are worth being direct about:
- The customer self-serve onboarding flow for email — where you set up your own sender domain, brand kit, and templates without Boni's team doing it manually — is partially built and being actively improved. Right now it works for Boni's own sends and some partner lanes; the polished self-serve flow is still in progress.
- SMS and RCS channels are in architecture and early setup. The regulatory registration for SMS in India is complete, but the live SMS product channel is not yet available.
- A full visual sequence/journey builder with branches and goal-based exits is on the roadmap but not shipped.
- The central suppression gate does not yet cover all channels uniformly. Email and Bino WhatsApp business outreach are covered; other WhatsApp paths are being migrated.
- Reply reconciliation between the email delivery ledger and the Bow Chat conversation inbox is not yet fully automated. For now, campaign review combines the delivery report with a manual check of the reply inbox.
How to Start
Boni CPaaS is available as part of the Boni platform. If you are already using Bow Chat, some of this infrastructure is already in place.
For new setups, reach out through Boni CPaaS to describe your use case — channel (WhatsApp, email, or both), approximate volume, audience type, and what you are trying to accomplish. Boni's team will assess sender readiness, configure the right lanes, run internal canaries, and bring you up to compliance posture before any real external send goes out.
Top comments (0)