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 inboxMulti-domain email

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

Real pricing: eight-person agency email stack

An agency managing 8 client domains with 16 mailboxes costs: Shipmail Team at $29/month for all 16 mailboxes. On Google Workspace, 8 users × $7 = $56/month for email only. Add shared inbox (Front at $19/user): 8 × $19 = $152/month. Total: $208/month. Add Slack ($8/user): $64/month. Grand total: $272/month for the same 8 people with fragmented tools. Shipmail is 9.4× cheaper and is one product instead of three.

The true cost includes operational overhead too. Workspace, Front, and Slack each have their own user management, access controls, and billing. Shipmail handles all of it in one place.

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.

Real agency workflow: email without forwarding

Client A emails support@clientA.com at 9am. Sarah (account manager) and Priya (project lead) both have access to that mailbox. Priya drafts a response, Sarah reviews it within the Shipmail interface, and it sends from support@clientA.com. No forwarding chain. No CC games. One shared inbox, two collaborators, full context.

Client B submits a change request to billing@clientB.com at 11am. The request auto-routes to the Finance shared mailbox that only the finance team can access. By day's end, the invoice is updated and sent without leaving email. No forwarding across domains, no leaked access to other client mailboxes.

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. When a client emails support@clientdomain.com, the only way to share that message with your project lead on Google Workspace is to forward it (which breaks the From address) or set up a Google Group (which requires admin access to that client's workspace). Both are fragile.
  • +Per-user pricing at scale. An eight-person agency on Google Workspace ($7/user) plus a shared inbox tool like Front ($19/user) pays 8 × ($7 + $19) = $208/month before client domains are set up. Shipmail Team handles 50 mailboxes at $29/month flat.

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.
How much do agencies save by switching from Workspace + Front to Shipmail?
An 8-person agency on Google Workspace plus Front shared inbox spends $208/month. The same agency on Shipmail Team pays $29/month. That is $179/month saved, or $2,148/year.
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.
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.