Client sub-accounts you can step into without a second password. Twenty seats with permissions set per section. An audit log of who did what. And a report link the client opens without an account. One platform under the whole book of business.
The sending platform. The list-verification tool. The automation builder — or the hours you spent bolting one together. And whatever you use to draft copy. Four vendors, four invoices, four sets of credentials. Multiply that by eleven clients and it is not a stack, it is an administrative job.
CleverlyBox collapses the four into one. Verification is native. Automation is native. AI copy is native. Sending is included — no AWS console, no separate setup. And you are priced on the software, not on how many contacts your clients happen to have accumulated.
Illustrative. Your stack is your own — the point is the count of vendors, not the figures.
Each client gets an isolated sub-account under your parent account — its own lists, campaigns, automations and reports. Nothing leaks sideways. You move between them from one dashboard.
One click puts you inside the client account. Your own identity is held underneath, a banner tells you whose account you are in, and switching back pops you out. No password manager. No second browser profile for the client who insisted on their own tenant.
Suspension stops an account without emptying it. The list, the campaigns and the history all stay. Resume and it picks up where it left off. A late invoice never costs a client their data.
Created, suspended, resumed, deleted, switched into — each written down with the actor and the timestamp. When a client asks what happened to their account on the 14th, you answer with a record rather than a recollection.
Illustrative. Client names are examples.
The Agency plan includes twenty team seats. Each person gets their own login and a permission matrix — module by module, action by action. Create, read, update, delete, run, generate, across lists, campaigns, automations, templates, forms, sending domains and AI copywriting.
Not a vague "role" that turns out to mean admin. A campaign executive can build and send but never touch a DNS record. A designer can draft but not run. And when someone leaves, you switch off one seat — you don't rotate eleven client passwords.
Every campaign report can be published to a public URL. No login, no seat, no "can you add me to the account". You paste it into the monthly email and the client sees the numbers themselves.
The finance director who will never sign into an email tool can still see what went out on Tuesday. A shareable URL, opened by anyone holding it, with the campaign's numbers on the other side.
The link points at the report, not at a PDF you exported on the 3rd. Opens, clicks and geo keep updating. You stop rebuilding the same deck every month.
When a client wants to know whether one particular buyer opened it, you have per-recipient logs and CSV export sitting behind the same report. The answer takes a minute, not a support ticket.
Not a procurement exercise. A sub-account, a verified domain, a cleaned list and a first send.
Empty and isolated, from your dashboard. No new subscription, no new invoice, no waiting on their IT to provision anything.
The records are generated for you and checked in the interface. You see green before you send, not after the first bounce report. Warm-up is available if the sending domain is new.
The list they hand over on day one is the list nobody has touched for two years. Run it through verification — sixteen providers built in — and you find out what you inherited before you put your reputation behind it.
Drag-and-drop builder, up to five subject variants with the winner picked on open or click rate, then the public report link goes to the client. That is week one.
Per-contact pricing punishes you for doing your job. Grow a client's list and your own cost goes up — so the win becomes a line item. Here the plan is the plan, sending is included, and a good quarter for the client is just a good quarter.
If you would rather send through your own infrastructure, nine providers are supported from the Business tier — Amazon SES, SendGrid, Mailgun, SparkPost, Elastic Email and the rest, or any SMTP. You are not required to.
No. It is a session push. Your identity is held underneath, a banner shows which client you are inside, and switching back returns you to the parent account. You never type a second password.
Not to see the numbers. A campaign report can be published to a public URL that opens without any account, which covers the usual request. If a particular client wants hands-on access to their sub-account, that is a decision you make per client.
Yes. Permissions are granted per module and per action — create, read, update, delete, run, generate — across lists, campaigns, automations, templates, forms, sending domains and AI copywriting. A junior can draft campaigns without being able to send them or touch a sending domain.
No. Sending is included — there is nothing to configure on day one. If you prefer your own, nine providers are supported from the Business tier, including Amazon SES, SendGrid, Mailgun, SparkPost, Elastic Email, Gmail OAuth and any SMTP server.
It stays. Suspension stops the account; it does not empty it. Lists, campaigns, automations and history remain, and resuming restores the account as it was. Deletion is a separate, deliberate action.
Sub-accounts, seats, permissions, audit log and sending — on one invoice.