Create a sub-account for each client. Step into it with one click — no second password, no second browser profile. Give your team exactly the permissions they need and nothing else. Every state change is written to an audit log.
One account per client, each on its own plan, each with its own bill. Someone leaves and you rotate eleven passwords. A junior needs to schedule one campaign and you hand them the keys to the whole account, because the tool has no idea what "junior" means.
CleverlyBox treats the agency as the unit. Your account is the parent. Clients are sub-accounts underneath it. Your team are sub-users with a permission matrix. One login, one bill, one audit trail.
Illustrative. Client names shown are examples.
The full lifecycle of a client account, from the parent dashboard. No support ticket, no second tool.
Create a sub-account from the agency dashboard. It comes up empty and isolated — its own lists, its own campaigns, its own automations, its own reports. Nothing leaks between clients.
Switching into a client is a session push. You keep your identity underneath; a banner sits at the top of the screen telling you whose account you are inside, with a switch-back button. You are never guessing which tab is which client.
Suspend a sub-account and it stops. Resume it and it picks up where it left off — the data is still there. Suspension is a switch, not a deletion, so a late invoice never costs a client their list.
Created, suspended, resumed, deleted, switched into. Each one lands in the audit log with who did it and when. When a client asks what happened to their account on the 14th, you have an answer instead of a theory.
How many client sub-accounts you can run is governed by your plan. See pricing.
A parent account creates sub-users. Each sub-user gets a permission matrix — not a vague "role" that turns out to mean admin. You grant access module by module, and within each module, action by action.
| Module | Create | Read | Update | Delete | Run | Generate |
|---|---|---|---|---|---|---|
| Lists | ✓ | ✓ | ✓ | — | · | · |
| Campaigns | ✓ | ✓ | ✓ | — | ✓ | · |
| Automations | — | ✓ | — | — | — | · |
| Templates | ✓ | ✓ | ✓ | ✓ | · | · |
| Forms | ✓ | ✓ | — | — | · | · |
| Sending domains | — | ✓ | — | — | · | · |
| AI copywriting | · | ✓ | · | · | · | ✓ |
An example matrix for a campaign executive: can build and send campaigns, can read the automations but not touch them, cannot go near the sending domains.
Not twenty for an extra fee. Twenty included. Account managers, copywriters, designers, the contractor you use three months a year — each gets their own login with their own permissions, and you switch one off the day they leave.
Because roles live at the customer level, a person is a person in your account — not a shared password taped to a monitor.
Every campaign report can be published to a shareable public URL. No login, no seat, no "can you add me to the account". You paste the link into the monthly email and the client sees their numbers.
A public report URL opens for anyone holding it. That means the finance director who will never log in to an email tool can still see the campaign that went out on Tuesday.
The link points at the report, not at a PDF you exported on the 3rd. Opens, clicks and the rest keep moving. You are not rebuilding a deck every month.
Read-only sharing means you don't hand out a login just so someone can look. The account stays yours; the numbers go to whoever needs them.
Your clients need lists cleaned, campaigns sent, automations run and copy drafted. In most agencies that is four vendors, four invoices and four sets of credentials — multiplied by every client you have.
Here it is one platform with sub-accounts underneath it. The verification is native. The automation is native. The AI copy is native. You are billed once, and you can see all of it from one dashboard.
No. It's a session push, not a re-login. Your own session is held underneath, a banner tells you which client you are currently inside, and switching back pops you straight out. You never type a second password, and you never lose your place.
Not to see their numbers. A campaign report can be published to a public URL that opens without a login, which covers the most common request — "can you send me the results". If a client does want hands-on access to their own sub-account, that is a separate decision you make per client.
Your plan governs the number. The Agency plan is built for running a book of clients; smaller plans allow fewer. The pricing page has the current numbers.
Nothing. Suspension stops the account — it does not empty it. Lists, campaigns, automations and history all stay put, and resuming brings the account back as it was. Deletion is a separate, deliberate action.
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. Combined with sub-accounts, that lets you keep people out of the parts of the platform they have no business touching.
Client account state changes — created, suspended, resumed, deleted, switched into — are written to the audit log with the actor and the timestamp. It's there for you when a question comes up about who did what.
Sub-accounts, seats, permissions and an audit log. One platform, one bill.