Communications and CPaaS
Request Messaging CPaaS, receive Boni-admin approval, then target CRM or Bow Chat contacts with an approved sender.
One communication operating model
Boni connects channels such as email, WhatsApp, SMS, campaigns, and Bow Chat to customers, owners, workflows, and CRM context. Channel delivery is not treated as the final business outcome; replies and next actions remain visible.
In this section
| Page | What it covers |
|---|---|
| Sender domains, DNS verification, brand kits, templates, delivery reporting and suppression | |
| Sender classes, approved templates, replies and consent | |
| Channel availability | Which channels are generally available today, and which are not |
For calls, numbers and routing, see Boni Voice.
Request Messaging CPaaS
An organization owner or admin opens Add Modules in Boni Panel, chooses Messaging CPaaS, and selects Request access. The request appears in Boni's admin approval queue. A Boni platform admin reviews and approves or denies it; after approval, the Messaging page becomes available to the tenant's eligible owners and admins.
The tenant does not provide a platform secret for this flow. Request approval unlocks the workspace and panel only. It never sends or schedules a message.
One campaign flow
| Step | Choice |
|---|---|
| Audience | Select CRM contacts, Bow Chat contacts, or an uploaded contact set |
| Sender | Use a customer-connected number, a Boni-managed number enabled for the workspace, or an allocated DID after its setup is ready |
| Delivery | Review the campaign, then send now or choose a schedule |
Boni Panel and Bow Chat open the same campaign composer and delivery record. Templates, sender readiness, permissions, suppression, scheduling, replies, and delivery results therefore stay in one workflow rather than being copied between panels.
Sender ownership
Every outbound route uses an approved sender, domain or phone identity for the exact organization. Connecting a domain does not require moving an existing Google Workspace or Microsoft 365 mailbox. Boni first preserves the current mail records, then manages future sender records after delegation. Sender activation, consent, suppression, templates, and provider delivery remain explicit parts of setup.
A customer-connected number remains customer-owned. A Boni-managed number appears only when Boni has enabled it for that workspace. An allocated DID remains unavailable for sending until allocation and channel setup are complete.
Assistant use
The Assistant can prepare communication work with the context and tools enabled for the current workspace. Drafting can be automatic; sending follows the configured authority and approval policy.