Route mail per mailbox: support@, billing@, and friends

Connect support@, billing@, and sales@ to one Leodesk workspace and route each mailbox to its own team and default owner, so a billing question lands on finance and a how-do-I question lands on support — automatically, the moment it arrives. You keep separate, sensible addresses for customers while your agents work a single shared queue with one set of contacts, search, and reports. The trick is configuring each mailbox deliberately: where it routes, who owns it, and which address it replies from.

One workspace, many mailboxes

The mistake most teams make early is treating each address as its own island — a separate login for support@, another for billing@, a personal inbox for sales@. That fragments your history and means no one can see the whole customer. Leodesk inverts it: one workspace holds many connected mailboxes. Every address you run becomes a shared inbox inside the same workspace, sharing contacts, search, agent accounts, SLAs, and reporting. A customer who once emailed sales@ and now emails support@ is the same person, with one timeline.

This matters because support volume rarely arrives at a single address. You publish support@ on the help center, billing@ on invoices, and sales@ on the marketing site — and each gets a different mix of questions from a different kind of sender. Keeping them as distinct mailboxes inside one workspace lets you treat them differently where it counts and identically where it helps.

Route each mailbox to a team and an owner

Each connected mailbox can route to a default group (team) and auto-assign a default agent the moment mail arrives. That is the core of per-mailbox routing: billing@ drops onto the finance team and, optionally, onto the one person who handles invoices; support@ drops onto the support team and into whatever assignment scheme you've chosen; sales@ goes to the account owners. Nobody has to read the To: header and drag the ticket somewhere — the mailbox already knows where it belongs.

Two settings do the work, and they're independent:

• Default group — the team a new ticket from this mailbox is filed under. Set this on every mailbox; it's what makes the queue make sense.
• Default agent — an owner the ticket is assigned to on arrival. Set this only when the mailbox has a clear single owner; otherwise leave it blank and let assignment run.

Because routing is per mailbox, you can be precise: a default group on all three, a default agent on billing@ only, and round-robin on the busy support@ queue. Layer Leodesk's automation engine on top when you need conditional routing within a mailbox — set priority, tag, or reassign based on subject or sender — but the per-mailbox defaults handle the common case with zero rules.

How Leodesk ingests mail

None of this requires you to migrate providers. Leodesk ingests mail two ways, so any host works:

• Forwarding / SES — point an address at Leodesk (or forward to it) and messages are delivered straight in. This is the cleanest path: mail arrives in real time, with no mailbox for Leodesk to log into.
• IMAP polling — give Leodesk read access to an existing mailbox over IMAP and it polls for new messages. This works with Gmail, Microsoft 365, or any IMAP host, and is handy when you can't change where mail lands yet.

You can mix the two: forward support@ for instant delivery while polling a legacy billing@ over IMAP. Both feed the same workspace, so the routing and assignment rules above apply identically regardless of how the message got in. For broader delivery context, the support email deliverability guide covers what to set up so inbound and outbound both behave.

Pin an owner, or leave it for round-robin

The default-agent decision comes down to volume and ownership. Pin a mailbox to a single owner when it's low-volume and someone genuinely owns it end to end — a billing@ that one finance person handles is the textbook case. The ticket lands on their plate, the SLA clock has a name attached, and nothing waits to be claimed.

Leave a mailbox unassigned when one owner would become a bottleneck. A busy support@ should distribute across the team, so leave the default agent blank and let round-robin or load-based assignment spread tickets to whoever's available. Pairing per-mailbox routing with fair distribution is what keeps a high-traffic address from piling onto one person — and Leodesk's collision detection stops two agents from replying to the same ticket at once. We go deep on that in round-robin, collision detection, and presence. A good rule of thumb: route every mailbox to a group, but only pin an agent when you'd be comfortable telling a customer "this person owns your case."

Pitfalls to avoid

Three patterns turn multi-mailbox support sour:

• One inbox for everything. Funnelling billing, sales, and support into a single address throws away the routing signal you'd otherwise get for free. Keep distinct addresses and let the mailbox decide the team.
• No ownership. A mailbox routed to a team but never assigned to a person is a queue everyone assumes someone else is watching. Either pin an owner or run round-robin so every ticket has a name on it — an unowned ticket is an unmeasured SLA.
• Replying from the wrong address. If a ticket arrived at billing@, the reply should go out as billing@ — not as a catch-all support@. Each connected mailbox keeps its own outbound identity so this stays correct. Sending everything from one address confuses customers and muddies the conversation; see From, Reply-To, and the address customers actually see for why the header matters. Authenticate each sending domain with BYODKIM so all of your addresses send as you, and set a Reply-To only when you deliberately want replies to land elsewhere.

Get those three right and multi-mailbox routing is mostly invisible: customers email the address that makes sense to them, and the right team picks it up without anyone playing traffic cop. For the deliverability side of running several sending addresses, start with Leodesk's email deliverability features.

Frequently asked questions

Can I connect more than one mailbox to a single workspace?

Yes. Leodesk is built around one workspace holding many connected mailboxes — support@, billing@, sales@, and any others you run. Each one is configured separately, so support@ can route to your support team while billing@ routes to finance, but they all share the same contacts, search, reporting, and agent accounts. You do not need a separate login or account per address.

Does each mailbox have to use the same email provider?

No. Leodesk ingests mail two ways: by forwarding or SES so messages are delivered to Leodesk directly, and by IMAP polling so it can read an existing mailbox on Gmail, Microsoft 365, or any IMAP host. Because it supports both, mailboxes on different providers can all land in the same workspace. You can mix forwarding for one address and IMAP for another.

Should a mailbox auto-assign to one agent or stay unassigned for round-robin?

Pin a mailbox to a default agent when it has a clear owner — a low-volume billing@ that one person handles, for example. Leave it unassigned and let round-robin or load-based assignment distribute tickets when volume is high enough that one owner would become a bottleneck, such as a busy support@. You can route every mailbox to a default group regardless, then decide assignment per mailbox.

How do I make sure replies go out from the right address?

Each connected mailbox has its own outbound identity, so a reply on a ticket that arrived at billing@ goes back out as billing@, not as support@. The most common deliverability mistake is sending every reply from one address regardless of which mailbox received it, which confuses customers and can hurt sender reputation. Authenticate each sending domain with DKIM so all of your addresses send as you.