Client campaigns that do not share a reputation.
The failure mode specific to agencies is cross-contamination. Run every client through the same sending identity and one client's aggressive list will quietly degrade delivery for all the others — usually discovered weeks later, from a chart nobody can explain.
What goes wrong, and what handles it.
One client's bad list damages every other client
Each client can be given its own authenticated sending domain and its own mailboxes. Reputation is built per domain, so a complaint spike on one campaign has no path to affect the others.
Suppression records get mixed between clients
Suppression is scoped to the workspace and stored as SHA-256 hashes. An opt-out from one client's campaign is honoured permanently without leaking that contact into another client's reporting.
Clients ask for proof the campaign ran
Open and click data, including approximate geography and device breakdown, exports as a PDF campaign report you can send on directly.
Deliverability problems surface too late
Domain authentication is checked with live DNS lookups before sending, and accounts hitting provider rate limits are cooled down and reported in real time rather than failing silently.
How a campaign runs.
- 01
Authenticate one sending domain per client and let the DNS checker confirm SPF, DKIM and DMARC before anything goes out.
- 02
Connect that client's mailboxes — Google Workspace, Microsoft 365, or their own SMTP host.
- 03
Upload and validate the list; malformed addresses and duplicates are rejected before the campaign is queued.
- 04
Build the campaign with mail merge for personalisation and Spintax so messages are not byte-identical.
- 05
Send. Volume rotates across that client's mailboxes with randomised pacing, staying under provider thresholds.
- 06
Export the PDF report when the campaign completes.
Where this is not the right tool
Each account is a single workspace. If you need genuinely separate logins and billing per client, you will be running several accounts rather than one multi-tenant dashboard. Platforms built specifically for agency multi-tenancy handle that better, and it is worth weighing before you switch.
Questions from agencies teams.
Setup, limits and the things worth knowing before you commit.
Can I manage several clients from one account?
You can run several clients' domains and mailboxes inside one workspace, which is enough for most small agencies. What you do not get is separate client logins, per-client billing, or a client-facing portal. If those matter, an agency-specific platform is a better fit and we would rather say so up front.
How many clients can one plan cover?
It comes down to domains. The Unlimited plan allows ten sending domains with ten mailboxes each. If you give each client one domain, that is ten clients with a hundred sending accounts between them.
Do clients need to give us their mailbox passwords?
You connect their sending accounts with credentials they provide, stored encrypted at rest with AES-256 and never displayed back in full after saving. Many agencies prefer the client to create a dedicated sending mailbox for this rather than sharing a personal one.
Can we white-label the reports?
Reports export as PDF for you to send on. There is no full white-label mode with your own branding applied across the dashboard.
Send a real campaign first.
Connect a mailbox, run your domain through the authentication checker, and see the results before you commit to a plan.
Start Free Trial