Shared inboxes for teams: running support@ and office@ together

What a shared inbox has to solve

The moment two people answer the same address, the same questions come up: has anyone replied to this yet? Who is dealing with it? What did we tell this customer last week? And when someone leaves, how do you take their access away without changing everyone else's? A good setup answers all four - and the options differ mostly in how well they do.

The four common approaches

1. Forwarding or a distribution list

Mail to support@ is copied to several personal mailboxes. It takes a minute to set up, which is why it is so common. But everyone gets their own copy and nobody can see whether a colleague has replied, so customers get two answers or none. Replies usually go out from each person's own address, so the conversation leaves the shared address, and the history ends up scattered across several mailboxes. Fine for a low-volume info@ that one person really handles; poor for anything a team answers.

2. One mailbox, one shared password

Everyone signs in to the same account. At least there's a single history. But you can't tell who did what, you can't give someone read-only access, two-factor sign-in becomes impractical, and when someone leaves you have to change the password and hand the new one to everyone who stays. Avoid it - it is also exactly the kind of account that gets compromised, because the password ends up in chats and sticky notes.

3. A shared mailbox with individual access

The shared address is its own mailbox, and each person reaches it with their own sign-in and their own permissions. The large suites have this: Microsoft 365 has shared mailboxes with "Full Access", "Send As" and "Send on Behalf" permissions, and Google Workspace has mail delegation and Google Groups configured as a collaborative inbox, in which members can take and assign conversations. Email-only providers offer it in various forms. This is the right default for most small teams.

4. A helpdesk tool

A dedicated support tool turns each message into a ticket with a status, an owner, a priority and a response-time target, plus canned replies, a customer history and reporting. It's worth it when you have many requests a day, several people on rotation, or service-level commitments. Below that it's often more process than you need, and it's another system where customer data lives - which matters for the GDPR.

Roles and permissions: least privilege

Whichever approach you pick, separate three levels of access:

Keep the last level small. Anyone who can grant access can also grant it to the wrong person, and anyone who can delete the inbox can delete its history.

Assignments and internal notes

Two features do most of the work of keeping a team inbox orderly. Assignment marks one person as responsible for a message, which answers "who's dealing with this?" at a glance and stops two people replying at once. Internal notes let colleagues discuss a message next to it - "customer called, refund approved" - without forwarding it around or, worse, writing it into a reply. The rule that matters: notes must never reach the customer.

Team conventions that make it work

• Assign before you answer. Take the message (or assign it) first, then reply.
• One voice. Reply from the shared address, with a shared signature that names the person writing.
• Agreed response time - even "same working day" is better than nothing, and someone should own the daily check.
• Close the loop. Release or reassign messages you can't finish, and move handled ones out of the way.
• Offboarding. Remove access on a person's last day, along with any app passwords or devices that connect to the inbox.

Shared inboxes in AnyMail

In AnyMail, the owner of an inbox can share that single inbox - not the whole mail server or account - with another AnyMail account, from the inbox's Access panel. Each person gets one of two roles:

• The person you share with finds the inbox under Shared with me and opens it like their own.
• Assignment: the owner can assign a message to anyone who has access to the inbox; a manager can take a message ("Assign to me") or release it. Only people who already have access can be assigned.
• Internal notes are stored separately from the message and are never sent to its sender or recipient, nor shown in mail apps.
• Mail apps: each inbox can also have up to five app passwords for IMAP and SMTP. You can give a colleague their own app password for the shared inbox and revoke it individually - but in a mail app there is no assignment or notes, so the web app is the better place for team work.

Two honest limits. Each person you share with needs their own AnyMail account, and AnyMail currently deletes an account without an active plan two months after its plan ended, or after registration if it never had one (with warning emails first) - so sharing works best between accounts that each have a plan. And AnyMail is not a helpdesk: there are no ticket statuses, response-time targets or canned replies. For a small team answering support@, roles, assignment and notes are usually enough; for a large support operation, a dedicated tool is the better fit.

A shared address is also a popular target for phishing and fake invoices - see business email security basics.