White Label Email Sending for Agencies
Honest explainer for agencies and freelancers managing outbound for several clients: what a client-workspace model actually gives you, what it does not (no client-facing portal, no built-in invoicing), and how the underlying AWS SES cost actually works.
EmailQo's client workspaces let one agency login run completely separate senders, domains, contacts and campaigns per client, with a usage breakdown (sends, opens, replies, bounces, sender and domain counts) for each. It is a sub-account model for the agency's own internal organization, not a portal your clients log into themselves, and EmailQo does not generate client invoices, it gives you the usage numbers to base your own billing on. It is a Scale plan feature.
What "client workspaces" actually means here
If you run outbound for more than one client, mixing everyone's senders, domains and contacts into one account gets messy fast, and a bad sending day for one client's domain can drag down reputation data you're looking at for a completely different client. A client workspace is a way to keep that separation without logging into a different tool, or a different login, for each one.
Concretely, each client you add gets its own senders, its own verified sending domains, its own contact lists, and its own campaigns, fully separate from every other client and from your own account's data. You stay on one login throughout, and switch between clients (or view your own account, called "My workspace") from the same dashboard.
Be clear about what this is and isn't: it's a sub-account model for your own internal organization as the agency, not a portal your clients log into themselves. There's no separate client-facing login. If what you actually need is for your end customers to sign in and see their own dashboard, that's a different kind of product than what this feature provides.
The per-client usage data you actually get
For each client, the dashboard rolls up: number of senders connected, number of verified sending domains, total contacts, active and total campaign counts, and performance across every campaign for that client, emails sent, open rate, reply rate and bounce rate. This is exactly the data you need as the basis for your own client reporting or billing, it just isn't a billing feature itself.
That distinction matters: EmailQo doesn't generate invoices, apply a markup, or show you a dollar cost per client. What it shows you is usage, counts and rates, that you can turn into whatever your own pricing or retainer structure with that client looks like.
Want every check on this page run automatically?
EmailQo runs SPF, DKIM, DMARC, blacklist, and content checks before every campaign, on your own Gmail, Outlook, or AWS SES sending account. Start the 7-day free trial, no card.
Start free trial →How the underlying sending cost actually works
If a client's sending runs through Amazon SES, Amazon bills usage directly to the AWS account connected, at Amazon's own published rate, with no markup added by EmailQo. If you're running multiple clients through separate AWS accounts (one per client, or your own with per-client sending identities), that AWS billing is also separated, which is often exactly what a reseller setup is trying to achieve.
If a client sends instead through Gmail, Outlook, Zoho or another SMTP account, there's no per-email cost at all beyond whatever that provider already charges for the mailbox itself, EmailQo's own plan price is flat regardless of send volume.
Either way, what you're paying EmailQo for is the platform, flat per month, not per email sent, and what AWS (if you use SES) charges is entirely separate and goes straight to your own AWS account.
Who this actually fits
A good fit: an agency or a freelancer running cold outreach for several clients at once, who wants each client's sending reputation, contacts and results kept cleanly separate, reported on individually, without juggling separate logins or separate tools per client.
Not a fit: if the actual requirement is giving your own customers a branded dashboard they log into themselves. Client workspaces here are for the agency's internal view, not a white-labeled product you hand off to someone else to use directly.
Related Resources
Does EmailQo support sub-accounts for agencies?
Yes, called client workspaces. One agency login can run completely separate senders, domains, contacts and campaigns for each client, with a usage breakdown per client, on the Scale plan.
Can my clients log in and see their own dashboard?
No. Client workspaces are for the agency's own internal organization under one login, not a separate client-facing portal. Your clients don't get their own sign-in.
Does EmailQo show me the dollar cost per client, or generate client invoices?
No. It shows usage data per client, sends, opens, replies, bounces, sender and domain counts, which you can use as the basis for your own billing. EmailQo itself doesn't generate invoices or apply a per-email charge.
If I use Amazon SES, who actually bills for the emails sent?
Amazon bills your connected AWS account directly, at Amazon's own published rate. EmailQo adds no markup on SES usage. EmailQo's own plan price is flat per month regardless of how much you send.
Is client data actually kept separate, or just labeled separately in one list?
Separate. Each client's senders, verified domains, contacts and campaigns are scoped independently, not just filtered views over one shared pool.
What plan do I need for client workspaces?
It's a Scale plan feature. Check the current plan details on EmailQo's pricing page, since plan features can change.
Keep the guide close, get deliverability tips monthly
One short, useful email per month covering SPF/DKIM/DMARC pitfalls, warmup, and cold-email content. No spam. Unsubscribe anytime.
By subscribing you agree to receive occasional tips at this address. See our Privacy Policy. Unsubscribe anytime from any email or at /unsubscribe.
Your emails deserve the inbox.
Start free trialKeep reading
SPF Setup Guide for Cold Email Senders
Step by step SPF record setup for cold email. Includes DNS examples, common mistakes, and how to validate your record is working.
GuideDKIM Setup for Amazon SES | Step by Step
Complete DKIM setup guide for Amazon SES. Generate keys, add DNS records, verify in AWS console, and start sending authenticated email.
GuideDMARC Setup Guide for Cold Email Senders
Step by step DMARC setup for cold email. Choose the right policy, set up reporting, and protect your domain from spoofing.
ComparisonAWS SES vs Mailgun: which is better for cold email
AWS SES and Mailgun side by side for cold email: pricing, limits and setup effort, explained for founders and small agencies.
ComparisonAmazon SES vs Postmark for cold email: which to use
Amazon SES and Postmark compared for cold email: price, sending rules and setup, in plain words. See which one fits your outreach.