Email CPaaS
Send from your own subdomain with verified DNS, brand kits, versioned templates, delivery reporting and central suppression.
What Email CPaaS gives you
Email CPaaS lets an organization send from its own domain with verified authentication, its own branding and versioned templates, and get delivery reporting and suppression back in one place. Humans work in Panel → Email CPaaS → Setup & Health; an authorized workspace Assistant can call the same tenant-scoped API.
| Object | What it is |
|---|---|
| Sender domain setup | The domain you send from, plus the DNS records that authenticate it |
| Brand kit | Logo, colours and layout applied to your templates |
| Sender identity | A specific From name and address on a verified domain |
| Template | A versioned message you can preview with real variables before use |
| Send and events | The message ledger, with delivery and engagement events |
| Suppression | Addresses excluded from future sends |
Use a subdomain
Boni's recommended setup sends from a subdomain rather than your root domain:
| Subdomain | Purpose |
|---|---|
tx.yourcompany.com | Transactional and product email |
campaign.yourcompany.com | Marketing and lifecycle email |
Separating the two protects transactional deliverability from campaign reputation. Root-domain sending is possible but is an advanced choice and should be rare.
Setup, step by step
- Create the domain setup for the subdomain you want to send from.
- Boni returns the exact DNS records to add — ownership, SPF, DKIM and DMARC, plus bounce, tracking or reply records where they apply.
- Add those records at whichever DNS provider holds your zone.
- Boni verifies the records in public DNS. Production sending is not enabled until verification passes.
You do not have to move your root domain, your website or your mailbox MX to send with Email CPaaS. If you separately choose to have Boni manage your DNS through Connect your domain, that still does not move your existing website or mailbox.
Templates and previews
Templates are versioned, and a preview renders a specific version with the variables you supply and reports readiness warnings before you send. Preview a template with realistic values whenever the variables change; an unresolved variable is far cheaper to find in preview than in an inbox.
Reporting and suppression
Sends produce a message ledger with delivery and engagement events. Suppression is applied centrally, so a suppressed address stays excluded across later sends and across channels.
Treat provider acceptance and delivery as different facts. A send that was accepted is not proof it reached the inbox; read the delivery events.
Related: Communications overview, WhatsApp, Channel availability.