Skip to content

← All writing

Guides

Shared team inboxes and the things that go wrong

12 July 2026 · 2 min read · TMailr

support@, sales@, info@: one address, several people, and a set of failure modes so consistent that you can usually name a team’s problem from the symptom.

Everybody can see it, so nobody owns it

The classic. Three people read a message, each assumes one of the others has it, and it sits for two days. The customer chases, somebody apologises, and the fix proposed is to check the inbox more often, which is not a fix.

What works is assignment. A message with a name against it is somebody’s job; a message in a shared list is nobody’s. Whether that comes from a helpdesk tool or a discipline about who takes what matters less than the property itself.

Replying as yourself

Somebody answers from their own address because it is quicker. Now the thread has left the shared inbox, the customer replies to a person, and when that person is on holiday the conversation is invisible to everyone else.

Always reply from the shared address. The reader should never learn an individual address unless you intend them to have it, and the moment they do the thread stops being recoverable by the team.

Forwarding to personal mailboxes

A tempting shortcut that quietly breaks three things. Forwarded mail loses SPF and, if anything rewrites it, DKIM, so it is more likely to be filtered. Replies come from the individual. And there is no record of what happened, because the copy that mattered is in somebody else’s mailbox.

The address that is not read

Worse than a slow inbox is a published one nobody opens. Every legal page lists a contact address, and a good proportion of them bounce or go to a mailbox last checked in 2019.

This is worth checking rather than assuming, because the failure is invisible from the inside: you never hear from the people who tried. Send a message to every address you publish and confirm it lands somewhere a person looks.

We found ours refusing mail outright. The privacy page printed a data protection address that answered 550, so anybody exercising a legal right got a bounce and nothing on our side ever knew they had tried. There is now a daily check that reads the addresses off the site and asks the real mail server whether it would accept them.

A short list of what helps

  • One person owns each message, visibly.
  • Replies always come from the shared address.
  • No forwarding into personal mailboxes.
  • Every published address is tested on a schedule, not on a hunch.
  • Only publish addresses you intend to read. Two that work beat six that might.

More on guides