Cold Email Inboxes for Agencies: Isolation First

Brand isolation. Cold email never runs on the client's primary company domain or on your agency primary domain. Dedicated outbound domains sit close to each brand and redirect to the main site. See Primary Domain Isolation for Cold Email.

Client isolation. Each client gets a separated pool of domains and mailboxes. Prefer separate Google organizations when the plan supports it. At minimum, pools must be clearly separable so you can pause one client without touching another.

Platform isolation. Know whether seats are official Google Workspace in an organization you admin, or seats on shared SMTP / shared tenants. Shared pools couple strangers to your clients. See Dedicated Google Workspace vs Shared Cold Email Infra.

• One Workspace organization holds every client "for convenience."
• Domains are mixed in one sequencer workspace with no naming standard.
• A single shared SMTP product is resold to every client as "inboxes."
• Density climbs on one domain because buying another domain feels slow.
• The agency primary domain is used for demos and then left in a live campaign.

Each of those choices saves an afternoon and costs a quarter when one client burns.

1. Dedicated domains only, registered or controlled by the client (or clearly transferable to them).
2. Two or three mailboxes per domain, soft ceiling around five.
3. Daily caps around roughly 20 to 40 cold sends per warmed mailbox including follow ups.
4. Authentication complete (MX, SPF, DKIM, DMARC) before warmup ends and campaigns start. Google's sender guidelines apply to mail hitting Gmail.
5. Admin access with 2FA so your team can offboard senders without tickets.
6. Sequencer connection using methods Instantly and Smartlead support (OAuth or IMAP/SMTP with app passwords), with mailbox names that encode client and domain.

Size the pool from the client's daily target, not from a slogan number. See Google Workspace Sending Limits for Cold Email and Mailbox Rotation for Cold Email Infrastructure.

• One client, one pool. Do not rotate prospects across another client's domains.
• Separate billing and ownership conversations early. Who pays for domains, who keeps them at offboarding, who holds the Admin console.
• Health reviewed per client. A weekly sort by reply rate and bounce rate per pool beats a blended agency dashboard.
• Pause authority. Your runbook should let ops pause a client pool in minutes when complaints or bounces spike.
• No shared warmup excuse. Warmup helps new seats build history; it does not justify mixing clients on one domain.

Multiple organizations (or equivalent separation) are plan dependent at many providers. Confirm on the plan you are actually buying.

• Official Google Workspace (if that is your standard) with a named organization model.
• Bring your own domains plus a clear path if domains are purchased through the provider.
• Automated SPF, DKIM, DMARC, and MX you can still inspect.
• Admin panel access with 2FA.
• Optional warmup you can enable or skip.
• Mailboxes ready to connect in Instantly and Smartlead using the methods those tools support.
• Documented support for multiple organizations or clearly separated pools on your plan.

Use the broader chooser in Cold Email Infrastructure Provider: How to Choose when you are still shortlisting vendors.

• The vendor cannot explain whose Google organization the seats live in.
• Domains cannot move with the client at offboarding.
• One shared pool is proposed for "all your clients."
• Pricing or packaging pushes placement percentages instead of control.
• Setup skips visible DNS.

Plan the exit on day one.

• Domains stay with the client whenever possible.
• Admin roles are documented so you can remove agency users cleanly.
• Sequencer connections are disconnected on a checklist, not by memory.
• Warmup and campaign schedules stop before DNS changes begin.

A clean offboarding is part of isolation. Messy exits leave orphaned seats sending, or leave the client unable to prove ownership of the domains that hold their reputation.

Agencies often get pressured into the cheapest pooled option. Cheap shared infrastructure is how one client's mistake becomes your whole book of business problem. Keep the conversation on control: named platform, admin access, separated pools, transferable domains. Unit price belongs on the provider site, not in a race that strips isolation. Price clarity for ColdMail stays on coldmail.app; this article does not quote mailbox rates.

Many clients already live in Instantly or Smartlead. Your job is to deliver mailboxes that connect with the methods those tools support, named so the client's ops team can see which domain each seat belongs to. If the client uses n8n or another automation layer, the same rule holds: documented Google or IMAP paths only. Ask how any handoff works and check the sequencer docs before you rely on a custom connector story.

ColdMail provisions official Google Workspace mailboxes on dedicated domains, with automated SPF, DKIM, DMARC, and MX, an admin panel per domain with 2FA, and provider health indicators for Gmail, Outlook, and Yahoo. AI warmup is available as an optional add on; see coldmail.app for current add on pricing. Multiple organizations are available on supporting plans so agencies can keep client pools apart. There is no shared SMTP pool and no Microsoft 365 mix in the product.

ColdMail is not a sequencer. Mailboxes are ready to connect in Instantly and Smartlead using the methods those tools support, and they work with n8n and other tools.

Set up isolated client pools at coldmail.app, or Book a Strategy Call to design domains and organizations per client.