An agency is a strange kind of business. You have one company, but all day you're speaking as a dozen others. A reply to a prospect on behalf of a client has to sound like that client, come from that client's domain, and carry no trace of the eleven other brands you're also running. The moment one client sees a stray reference to another, something quietly breaks, and it's the kind of break that costs a retainer.
Most agencies grow into an email setup rather than choosing one, and by the time it hurts, the patchwork is load-bearing. This is a guide to the structure that actually fits the work: every client brand cleanly separated, the right identity automatic, and one place to see all of it without the streams blending.
A normal business has one identity. An agency has as many identities as it has clients, plus its own. That changes the problem in three ways that ordinary email tools never account for.
You send as other people. When you manage inbox@clientbrand.com, your replies have to go out as that brand, on that domain, with that signature. Get it wrong and you've either outed the agency relationship the client wanted kept quiet, or worse, named a different client in front of this one.
Work is shared, not solo. Often more than one person on your team touches a client's mail. That means the setup can't live in one founder's head or one person's Outlook profile. It has to be a shared, structured thing that a new hire can be dropped into without a week of tribal knowledge.
Clients come and go. Onboarding and offboarding happen constantly. Every new client should be a small, clean addition, and every departing client should be a clean removal, not a careful untangling of forwarding rules nobody documented.
Two arrangements are nearly universal, and both have a ceiling.
A login per client. Each client gives you a seat on their Google Workspace or Microsoft 365, so your team lives in a wall of tabs and browser profiles. Nothing mixes, which is the upside, but nobody has a view across clients, mail gets missed because the right tab wasn't open, and onboarding a teammate means provisioning them into every client tenant one at a time.
Everything forwarded into a shared agency inbox. All client mail pours into one help-desk-style inbox. Now you can see it, but every brand is jumbled together, replying as the correct client is a manual act of attention on every single message, and the risk of cross-client leakage is highest exactly when the team is busiest.
Both are coping strategies. Neither was designed for a business whose core shape is many identities at once.
Name the jobs and the right structure becomes clear. There are three.
Hard separation per client brand. Each client is its own walled space. Working inside one client, your team sees only that client, and there is no path for one brand's mail or name to appear inside another's.
Correct sending identity, by default. A reply on a client's thread goes out as that client, set by which client space you're in, not by a From dropdown someone has to select correctly every time under pressure.
Oversight without merging. The owner needs to see across every client at a glance, so nothing goes silent on a client who's paying you monthly, while each client still stays in its own lane. Visibility and separation at the same time is the whole trick.
Whether the client gives you an address on their domain (you@clientbrand.com) or you manage a shared client inbox, the principle holds: one canonical address per brand that mail routes through. Resist the urge to spin up a brand-new mailbox and login for every client. What you want is a structure where the address mail arrives on tells you which client it belongs to, so sorting is automatic rather than something a person does.
Agencies live or die on repeatable process. Make client email onboarding one of them: a short, written sequence for adding a client's address, setting their sending identity and signature, and giving the right team members access. When adding a client is a five-minute checklist instead of an improvisation, offboarding becomes just as clean, you remove the address and the access, and nothing dangles.
Agencies sign up for an enormous number of tools, often on behalf of clients: analytics, ad platforms, design libraries, the SaaS-of-the-week a client wanted tested. Route all of that through a throwaway catch-all domain instead of any client address or your real agency inbox. The verification codes and platform notifications land somewhere searchable, and no client's address gets harvested into marketing lists. Our guide to spam domains walks through the setup.
This is where standard email clients stop being enough. They were built to hold a few accounts in a sidebar, not to run a business made of many identities. What agency work needs is a dashboard where each client brand is its own context: its own incoming and sent mail, its own threads, and a sending identity locked to that context so a reply on Client A's account simply cannot go out as Client B or as the agency.
This is the problem Cereal was built for. Each client brand gets its own bowl. Mail routes into the right bowl by the address it was sent to, so the sorting is automatic. The owner sees every client at a glance on one screen without the brands blending, and any reply takes its identity from the bowl it's sent from. The wall-of-tabs problem and the wrong-brand problem both go away, because the structure stopped depending on everyone staying vigilant.
When client mail gets overwhelming, the tempting fix is to centralize harder: pour everything into one agency inbox so nothing is lost. It trades a missed-mail problem for a brand-bleed problem, and brand bleed is the more expensive one. A client who catches a competitor's name in a thread, or gets a reply that's clearly from a generic agency address rather than their own brand, starts wondering what else is being handled carelessly.
The goal isn't one inbox. It's clean per-brand separation with full oversight on top. You want to look at Client A without Client B anywhere in view, reply as Client A with no possibility of it going out as anyone else, and keep every tool-signup notification quarantined far from real client threads. Build that once and it scales: the tenth client is the same clean addition as the second.
Once this is in place, the part of agency life that used to be a constant low-grade risk, sending as the wrong brand, missing a quiet client, leaking one account into another, stops being something your team has to actively prevent. The structure prevents it.