Seats with permissions set per section. An audit log of who changed what. Deliverability monitored per mailbox provider. A REST API with webhooks. And a full export of your data on any day you choose — because the ability to leave is the only guarantee that means anything.
The sending platform. The verification service. The automation builder. The AI copy tool. Four contracts, four security reviews, four renewals, four sets of user accounts to deprovision when somebody leaves. Most of the cost of an enterprise email stack is not the licence — it is the administration of it.
CleverlyBox is the four in one platform. One login, one invoice, one set of seats, one audit log. Sending is included, so there is no separate relay to provision. And the price is set by the software, not by how many contacts your CRM happens to hold this quarter.
"Role" in most tools is a menu with two options, one of which is admin. Here, permissions are granted per module and per action, so the access someone has is the access their work requires — and nothing beyond it.
Each is a section. Each section has its own grant. A campaign executive can build and send; they never see the sending-domain configuration, so they cannot break the DKIM record on a Friday afternoon.
Read without update. Update without delete. Build without run — so a draft cannot be sent by someone who was only meant to review it. The distinctions are the point.
People are people in the account, with their own login. When they leave, you switch one seat off. There is no shared credential to change and no list of tools to work through from memory.
Account state changes — created, suspended, resumed, deleted, switched into — land in the audit log with the actor and the timestamp. When the question comes six weeks later, you have a record.
Illustrative view. The values shown are examples, not a benchmark.
A single aggregate deliverability number hides the only thing worth knowing: that one mailbox provider has quietly turned against you while the rest are fine. Break it out by provider and the problem is visible while it is still small.
SPF, DKIM and DMARC are generated and verified in-app. The IP warm-up engine ramps new sending — linear or exponential. Sending pauses automatically when bounce or complaint rates spike, one-click unsubscribe is implemented to RFC 8058, and a blacklist and banned-word check run before the campaign leaves.
A platform that cannot talk to your stack becomes a silo within a month. This one is addressable from both directions.
Create and update contacts, manage lists and tags, write custom fields, and trigger an automation directly from your own systems — API is one of the twelve automation triggers.
Events land in your warehouse or CRM as they happen. A webhook node can also sit mid-automation and POST to your endpoint at any step in the flow.
WordPress, n8n, your own application — route them through the CleverlyBox SMTP relay and that mail travels the same authenticated, monitored path as your campaigns.
SMTP Relay → API, webhooks & SMTP relay → Sending providers →
Every campaign report exports to CSV, including the per-recipient logs — delivered, opened, clicked, bounced, by contact. Contacts, lists, tags and fields are addressable through the API. Nothing is held behind a support ticket or a retention conversation.
And if you would rather own the sending path entirely, nine providers are supported from the Business tier — Amazon SES, SendGrid, Mailgun, SparkPost, Elastic Email, Blastengine, Gmail OAuth, Sendmail or any SMTP server. Your infrastructure, our platform. Or ours end to end, with nothing to configure.
The Business and Agency plans cover 100,000 contacts. If your volume, contact count or seat requirement sits beyond that, talk to us and we will work out what the shape of it is — rather than guessing at a number on a webpage.
The published tiers stop at 100,000 on Business and Agency. Beyond that, get in touch and we will work out the arrangement with you directly. We would rather have the conversation than print a number we cannot stand behind.
Per module and per action. The modules are lists, campaigns, automations, templates, forms, sending domains and AI copywriting; the actions are create, read, update, delete, run and generate. You can grant read on automations without granting update, or build on campaigns without granting run.
Account state changes — created, suspended, resumed, deleted, switched into — are written to the audit log with the actor and the timestamp. It is there when a question arrives weeks after the event.
Yes, on any day. Campaign reports and per-recipient logs export to CSV, contacts and lists are addressable through the REST API, and open and click events can be streamed to your own systems by webhook. There is no exit process to negotiate.
From the Business tier, yes — Amazon SES, SendGrid, Mailgun, SparkPost, Elastic Email, Blastengine, Gmail OAuth, Sendmail or any SMTP server. Nine providers in total. If you would rather not, sending is included and requires no setup at all.
Volume, seats, permissions, API and the export button. Start on the free plan and see it work.