Blog

How to manage a shared mailbox

The routine for a shared address: who owns it this week, how two people avoid answering the same message, what done means, and the few readings worth keeping.

Someone is on holiday, [email protected] keeps taking mail, and nobody is sure who is covering it this week. A shared mailbox rarely fails at setup. It fails on the Tuesday when the person who normally answers is away.

Manage a shared mailbox by giving every message one owner and every working day one person on duty. Three habits carry most of the weight: a named rotation with a written handover, a claim the whole team can see before anyone replies, and a definition of done that separates read from answered.

What acts on a message when it arrives is shared mailbox rules. Putting several people on one Gmail address is how to set up a shared inbox in Gmail. Who may open the mailbox or send from it is shared mailbox permissions, which is a separate job.

The three ways a shared mailbox fails

Almost every problem on a shared address is one of three failures, and each has a routine answer.

Failure What it looks like by Friday The routine that prevents it
The unowned address Mail arrived on a day nobody was covering, and the oldest unanswered thread is a week old One named owner per week, and a handover at the end of each shift
The double answer Two people replied to the same message within minutes, with different answers A claim the whole team can see before anyone writes a reply
The quiet thread Somebody read it, decided it needed work, and never came back to it A definition of done, and a habit of reading the oldest thread first

Who is on the address, and who covers the holiday

With eight readers and no owner, the address gets read by everybody and answered by whoever feels guilty first.

Start with a rota. One person owns the inbox for the week, everybody else is backup, and the name goes where the team already looks. That turns “who has support today” into a question with an answer.

The handover is the part teams skip. At the end of a shift the person on duty writes three lines: what is open, who owns it, and what it is waiting on. That is the difference between cover and a mailbox nobody has opened since Thursday.

When someone takes a week off, they hand over threads rather than an inbox, or the thread waits for the person who knows its history. The customer waits with it.

For a team of five, one owner per week is enough, and the address rots when the rota is an assumption rather than a name.

How two people stop answering the same message

The collision happens between reading and replying. Two people open the same message, both decide it deserves a proper answer, and both send one.

A claim prevents it. Whoever picks the message up makes that visible before writing the reply: star the thread, move it out of the unread list, or post a line in the team channel that says you have it.

A claim is not a reply, and the two get confused constantly. The customer does not need to know the thread exists, only that a person has it. A short reply from that person does the job, and what first response time measures covers why an acknowledgement and a first answer are two different numbers.

Tools help when they can show a claim instead of hiding it. In a Google group running as a collaborative inbox, a member takes a conversation and their name goes on it (Use a group as a Collaborative Inbox), and what a collaborative inbox is covers where that stops.

The rule to write down: nobody replies to a message somebody else has claimed, and claiming means saying so where the team can see it.

What done means on a shared address

Read and answered are different states, and a shared address hides the gap between them. Four people can read the same thread and none of them can tell whether anybody has replied.

State What it means What the team can see
Read Somebody opened it Nothing the others can act on
Replied The customer has an answer The reply, if it went out through the shared address
Done Nothing on the thread is waiting on your team The state of the thread, if it lives on the thread and not in somebody’s head

Done has a specific meaning here. Either the customer has an answer, or the next move is theirs, or the work sits in a tracker with an owner and a state. A thread waiting on a fix is not done, even after the customer has been told the fix is coming.

That last case is where the quiet thread comes from. Somebody reads a message, decides it needs a change, and moves on, and the next person to open it reads the whole thing again.

The habit that catches it is dull. Read the oldest unanswered thread first, and treat “we are looking into it” as a thread that still needs a name against it.

What to do with mail that is not for anyone

A support address collects things it was never meant to answer: a colleague’s forward, a cc, a receipt, an invoice that belongs to billing.

Four people open each of those, work out it is not theirs, and close it again. The real risk is the message that did belong to somebody and gets closed in the same pass.

The fix is a decision about the address itself. Write down what it is for, then move everything else out of it. Receipts, password resets and build notifications are the biggest group, and auto-generated email and do-not-reply addresses covers the class.

Two habits make that stick. If you would not expect the team to answer it, do not send it to the address. And when mail arrives that nobody owns, move it out, because a message everyone has silently decided to ignore is worse than one that never arrived.

When a second address appears

[email protected] and [email protected] are two mailboxes, and the moment the second one exists, somebody has to say whether the same routine covers both.

Two arrangements work. One rota covers every address, which means the person on duty answers billing questions they may not know. The alternative is one owner per address, with the rota covering support alone.

Either is fine, and leaving it unsaid means the second address inherits the first one’s habits without its coverage.

The signal that you have stopped running one mailbox is a customer answered twice from two addresses, or a thread moving between addresses with no owner.

The shape question is separate. Whether a second address should be a shared mailbox, a distribution list or an alias is shared mailbox versus distribution list, and what a shared inbox is covers the layer a plain mailbox does not have.

What to measure, if anything

On a team of five, most support reporting measures the reporting. Three readings earn their place, and the first needs no tool at all.

Reading What it tells you Where it misleads
The oldest unanswered thread Who is waiting right now Nowhere, which is why it goes first
First response time How long a customer waited to be heard It stops at the first reply, so it says nothing about whether the problem is fixed
CSAT Whether the answer landed On five replies a week it is noise, not a trend

Everything else, from messages per person to labels per thread, describes who was on the rota that week.

Keep the oldest unanswered thread and one promise about reply time, which is what what a support SLA is is for.

Where Chirp fits

Chirp is a shared inbox for small software teams that track their work in Linear.

An address nobody owns is harder to ignore when the thread carries an owner. Press i to link, create or search a Linear issue, then snooze until done: when every linked issue is Done or Canceled, the thread comes back with a reply drafted for you that names the issue. The Issues view (g i) sorts linked issues by how many customers are waiting, so the quiet thread lands on a list instead of in somebody’s memory.

Rules close, tag, assign, snooze and write drafts, and no rule has a send action, so nothing in Chirp answers a customer on your behalf. Access is set per inbox, so support@ and billing@ can have different readers. Gmail, Google Workspace and IMAP mailboxes all connect, and the mailbox stays the source of record.

FAQ

What are the disadvantages of a shared mailbox?

Three: an address nobody owns, two people answering the same message, and a thread that goes quiet after somebody reads it.

How many people should share one mailbox?

As few as can cover the hours you promise. Everybody who may answer should be on the rota, and one person should be named as the owner for the week.

Is a shared mailbox the same as a distribution list?

No. A shared mailbox is an address your team answers from, and a distribution list is a different shape with a different owner story. Shared mailbox versus distribution list covers the choice in full.

How do you know a message has been handled?

Read is not handled. A thread is handled when nothing on it is waiting on your team, which means the customer has an answer or the next move is theirs.

Next step

The routine above gives every message an owner. If it keeps breaking in the same place, the choice is between a mailbox and a queue, and shared inbox versus help desk works through which one a team of five actually needs.