Boni
Boni
Browse documentation
Communications·overview·Version 2

Communications and CPaaS

Connect email, messaging, campaigns, Bow Chat, and customer replies without losing sender authority or workflow ownership.

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.

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.

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.