Email hosting for agencies: a practical setup for multi-domain teams

Agencies have a specific email problem that most hosting products handle poorly: multiple domains, role-based inboxes shared across teammates, and a client roster that changes often enough that onboarding and offboarding need to be fast. SHIPMAIL keeps hosting and shared inboxes in one product, which makes the multi-domain, multi-person setup much easier to manage.

By Julien
March 9, 2026
AgenciesClient domainsShared inbox

Rust-based mail engine, independently audited by Radically Open Security. Open protocols, no lock-in.

How SHIPMAIL handles agency setups

SHIPMAIL structures pricing around mailboxes rather than users. An agency on the Team plan ($29/month) gets 50 mailboxes with unlimited team members. That covers the agency's own domain, several client domains, and all the shared role addresses the team needs, without per-seat cost scaling.

Calendar and contacts are included, so the team can manage client meetings and contact details without a separate tool. A typical agency uses eight or more mailboxes across three or more domains. On SHIPMAIL Team, the cost stays at $29/month regardless of how many team members access those shared addresses.

Why agencies are an unusually strong fit

Agencies rarely manage one neat inbox setup. They have their own domains, client domains, project-specific addresses, and teammates rotating through the same conversations on a weekly basis.

This is where per-user pricing and two-product stacks hurt the most. The cost is not just the dollar amount. It is the complexity created when hosting and collaboration live in different places. Two admin panels, two billing cycles, two sets of access controls, and two products that can break independently.

A one-product setup is useful here not because it is slightly cheaper (though it usually is), but because it removes a category of operational overhead that compounds with every new client domain.

The workflow agencies actually need

Agency email workflows revolve around role addresses, not personal inboxes. New leads come into hello@client.com. Support questions arrive at support@client.com. Invoice disputes land in billing@agency.com. All of these need more than one set of eyes.

If the email host is built around private inboxes first, agencies end up patching the shared part later with another tool. A host that treats shared access as a core feature matches the agency operating model directly: shared workflow is part of the job, not an afterthought.

When an agency should choose something else

An agency should stay on a traditional stack when it is deeply embedded in Google Workspace and the team uses Docs, Sheets, and Meet daily. Adding a shared inbox layer on top of an existing Google commitment makes more sense than switching email hosts.

A dedicated helpdesk product is also the better choice when ticketed support with SLAs and customer portals is central to the workflow.

But for agencies where shared client communication still runs through email, and for most agencies under twenty people it does, SHIPMAIL is usually the simpler structure and the cheaper one.

Core pain points

  • +Too many domains, too many logins. Client domains end up split across different tools or different accounts. Each new client means a separate onboarding process, sometimes with a different provider. When a client churns, cleaning up is manual and easy to forget.
  • +Shared access workarounds. Most email hosts are built around private inboxes. If an account manager and a project lead both need to handle hello@clientA.com, the typical workaround is forwarding, CC chains, or adding a collaboration tool on top.
  • +Per-user pricing. Once account managers, founders, designers, and support staff all need visibility into shared addresses, the seat count climbs fast. On Google Workspace at $7.20/user/month plus Missive at $15/user/month, an eight-person agency pays $178/month before the client domains are even set up.

Getting started

  1. 1Add the agency domain first. SHIPMAIL walks you through the setup and tells you exactly what to change at your domain registrar. Create the role addresses the internal team shares. Assign access to the relevant team members.
  2. 2Add client domains as you onboard them. Each client domain follows the same guided setup. Create the shared mailboxes the team will operate from.
  3. 3Assign access intentionally. Not everyone needs access to every client inbox. Give the account manager and the relevant specialist access to each client's shared addresses.
  4. 4Remove access when clients churn. When a client leaves, remove the domain and its mailboxes. Team member access disappears with the domain. No orphaned forwarding rules, no forgotten shared credentials.

FAQ

Questions worth answering.

Common questions about using SHIPMAIL for agency email.

Why is SHIPMAIL a strong fit for agencies?
Because agencies operate across multiple domains with role-based inboxes that multiple people share. SHIPMAIL's per-mailbox pricing and built-in shared inbox match that operating model without requiring a second product.
Can agencies separate client access cleanly?
Yes. Each client domain has its own mailboxes, and access is assigned per mailbox. An account manager working on Client A can have access to hello@clientA.com without seeing anything from Client B's inboxes.
Which plan usually fits an agency best?
Smaller agencies (under five people, under five client domains) often start with Pro at $9/month. Agencies with more shared mailboxes, more client domains, or higher send volume usually move to Team at $29/month.
How does SHIPMAIL compare to Google Workspace + Missive for agencies?
An eight-person agency on Google Workspace + Missive pays roughly $178/month. The same agency on SHIPMAIL Team pays $29/month. Both provide email hosting and shared inbox access. Google Workspace also includes Docs, Drive, and Meet, which SHIPMAIL does not.
What happens when a client relationship ends?
Remove the client's domain and its mailboxes from SHIPMAIL. Team member access disappears with the domain. There are no forwarding rules to clean up, no shared credentials to rotate, and no extra seats to cancel in a separate collaboration tool.
How do I share an email inbox with my team without sharing a password?
Create a shared mailbox in SHIPMAIL and grant access to team members. Each person logs in with their own credentials and sees the shared inbox alongside their personal one. No shared passwords, no forwarding.