Managing multiple client email accounts without merging their lists
Tags in one account are fast to set up, until a suppression or a segment crosses a client boundary it shouldn't. What separate client accounts fix instead.
Most agencies start by running every client from one account, with a tag or a list marking each one. It is fast to set up and it works, right up until a contact who unsubscribed from one client’s mail turns out to still be mailable by another, or a segment built for one client quietly pulls in a second client’s contacts too. Those are not rare failures. They are what one shared account does by construction, the moment it holds more than one client’s list.
This is the contact-and-consent half of running client accounts. See email marketing for agencies for the reputation half: the same separation question applied to what a mailbox provider actually judges.
What one account with tags actually shares
A tag or a list separates contacts on the screen. It does not separate the account underneath them, and several things live at the account level whether you meant them to or not.
Suppression. A suppressed address is usually a row against the account, not against a list or a tag, because the record it protects, the contact, belongs to the account rather than to any one list. Run two clients through one account and an opt-out earned by client A makes that address unmailable to client B too, even though B did nothing to earn it. The reverse failure is just as possible: a suppression scoped too narrowly, to a list rather than the account, means an opt-out from client A’s mail does nothing to stop client B’s list from mailing the same address, so the person who unsubscribed keeps getting mail from you regardless. Check which way the suppression list in your tool draws the line before assuming either.
Segments. A segment’s rules can filter by list, tag, status, signup date or engagement, but nothing makes a segment scoped to one client automatically. Build a segment meaning to catch client A’s stale subscribers, using only an engagement rule with no list or tag condition, and it matches every contact in the account that fits the engagement rule, whichever client they belong to. Attach that segment to a campaign targeted at client A’s list, and client B’s stale contacts get mailed too. The rule that would have caught this, add a list or tag condition to every segment, is easy to forget on the tenth client, because nothing in the segment builder requires it.
Exports and reports. An export can be filtered by list, tag, status or segment on the way out, but a suppression has no client dimension to filter by in the first place. There is no export that produces “just client A’s suppressions”. A report pulled from an unfiltered export has the same problem: the columns don’t say which rows belong to which client, so somebody has to reconstruct that from tags before it’s safe to hand over.
Offboarding a client. Contacts come out cleanly, by filtering on the tag. Suppressions do not, for the reason above, and neither does the sending history, since campaigns and reports are account-wide rather than tagged per client. The tag or list itself often cannot even be deleted while a live segment or a scheduled campaign still names it, so a departing client’s tidy-up can outlive the relationship by weeks, with the account holder having to hunt down every reference before the tag will let go.
The consent problem
This is the one that matters most. A contact agreed to hear from a specific client, not from your agency and not from your other clients. Mailing them on behalf of a different client is a consent violation no matter what the tool allowed you to do, and the fastest way to lose it is exactly the mechanism above: a segment or a suppression gap that quietly widens who gets mailed past the boundary the contact agreed to.
It also does not stay contained to the one relationship. Sending reputation is commonly pooled at the account level, so a complaint spike from one client’s list can register against the shared sending identity every client rides on. In EmailFig, reputation is isolated per account, so this is specifically a shared-account risk, not a fact about every tool: running two clients through one account puts them on the same footing, and a complaint problem from one becomes a deliverability problem for the other. Separate accounts, ours included, give each client its own domain and IP, so one client’s bad list cannot sink another’s inbox placement.
Separate accounts vs. tags in one account
| Tags in one account | A separate account per client | |
|---|---|---|
| Setup effort | One signup, tag as clients arrive | One account to configure per client (sending domain, footer, from address) |
| Suppression scope | Account-wide; one opt-out can silence every client | Scoped to that client by construction |
| Segment scope | Runs over the whole account unless every rule is list- or tag-limited | Naturally bounded to that client’s own contacts |
| Sending reputation | Commonly one shared identity across every client | Commonly isolated per client |
| Billing | One pooled bill across every client’s contacts | Each client’s own subscription, tier and contact count |
| Offboarding a client | Contacts filter out cleanly; suppressions and reports don’t | Close or hand off one account; nothing to unpick |
Billing usually tracks the same split. One shared account means one bill for the sum of every client’s contacts, with nothing in the invoice saying whose contacts they were; if you pass sending costs on to clients, you’re doing that allocation by hand, from a tag count you have to pull yourself. A separate account per client has its own subscription, its own tier and its own contact count, so how pricing works for one client never depends on how many contacts a different client happens to be carrying that month.
Three things worth checking before you pick a shape, whatever tool you’re on:
- How many clients, and how different are their lists. Two clients with clean, engaged lists sharing an account is a smaller bet than a fifth client whose list you haven’t vetted yet.
- Whether a client ever needs their own view of their numbers, separate from the rest of your book. A pooled bill and a pooled report make that a manual job every time someone asks.
- What happens the day a client leaves. If the answer involves reconstructing a suppression list from memory, that is a cost you’re paying later for setup speed now.
- Whether the tools you’re weighing actually differ here. Not every vendor draws the line the same way; our comparison pages go through what a given tool charges and what it separates, client by client.
Where a competitor gets this right
BigMailer splits every client into its own sub-account, and it does this on every plan, including its free Startup tier. That is a genuine strength worth crediting: an agency can see real client separation before committing a card to anything. Our BigMailer comparison has the pricing detail, including the part that page is not upfront about: the free and cheapest paid plans both still require you to bring your own Amazon SES account, billed by AWS on top of whatever BigMailer charges.
What EmailFig does
Multi-account is live: one login, a client account per customer, one level deep. Each client’s contacts, suppressions and sending are kept separate, because each client is its own account underneath, with its own suppression list, its own segments, and its own sending reputation. There is no white labelling at any account size, so if what a client needs to see is a tool that looks like it’s theirs alone rather than a shared platform run by an agency, that’s a real gap, not a missing coat of paint.
Each client account is free up to 4,000 subscribers with no credit card, on the same terms as any other account, and paid plans start at $6 a month from there. The pricing page has the current numbers for both plan families; get in touch if running client accounts is what you’re evaluating us for.
The choice, plainly
If you run one client, tags in one account cost nothing extra, because there is no second client’s boundary to cross yet. The moment a second one arrives, nothing in the account knows there are two clients in it except you. That’s the point where separate accounts stop being overhead and start being the thing keeping each client’s consent, and your own reputation, where they belong.