Blog

Email collaboration for a small team

The team norms behind a shared address: who may speak for the company, how five writers sound like one, and when a thread should become a call.

Five people answer [email protected], and the arguments are never about the tool. They are about the reply a new teammate should not have sent, the thread that reached nine messages before anyone suggested a call, and the decision you remember differently six months later.

Email collaboration comes down to agreements that no setting provides: who may commit the company to something, how five writers sound like one, what gets written down, and when a thread should stop being email. The routine for the address itself is a separate job, and how to manage a shared mailbox owns it: who covers it this week, how two people avoid a double answer, and what done means.

What acts on a message when it arrives is shared mailbox rules, and who may send from the address is shared mailbox permissions. The labels are on what a shared inbox is and team inbox versus shared inbox.

Who is allowed to speak for the company

Everyone on the address can answer a question about an invoice. Not everyone can promise a fix date, a refund, or a feature that has not been built.

A permission cannot draw the line. A send grant says who may send from the address, and it says nothing about what they may commit to.

The habit that works is the internal note. When a question goes past what the writer knows, they write the reply as a note instead of sending it, a teammate corrects the promise, and the reply goes out under one name.

The question Who can answer alone What happens first
Where is my invoice Anyone reading the address Nothing, it is a lookup
Is this bug fixed yet Whoever owns the issue Check the issue state, then answer
Can you add this feature Whoever owns the roadmap Ask in an internal note
Can we have a discount The person who set the price Internal note, because the number is a commitment

Nothing in that table is a permission, which is why the habit matters more than access. A junior teammate is safe on the address when writing a note is normal rather than an admission of not knowing.

How you keep the tone the same when five people answer

Five writers produce five companies unless a few things are fixed. The teammate who writes like a press release and the teammate who writes like a text message are both understandable alone, and a customer who deals with both gets a different impression each time.

Fix the parts a customer reads as the company, and leave the rest alone.

Element The house default Where it is written down
The greeting The same opening line on every reply Email salutations
Saying no Name what you cannot do, then what you can The norm doc
Promises No date without a check The question table above
The sign-off One closing line, one signature Email sign-offs

Everything else can vary. Two writers keep their own phrasing inside those four lines, and the customer still reads one company.

The habit that carries it is small. Read a few replies the team sent this week before writing your own, which takes two minutes on a team of five. What a professional email signature looks like is the same decision in miniature: one default, set once, used by everyone.

What you write down, and what you say

A decision that only exists in a call is a decision the next person relitigates. The ones that matter change a customer’s answer: what you charge for, what you do not support, when a refund is yours to give, and what your reply-time promise is.

The decision Where it lives Who keeps it current
The reply-time promise The page customers read The person who owns support
When a refund is allowed The internal norm doc The founder
Why a feature was turned down The Linear issue that closed it Whoever closed it
What a status page means The internal norm doc Whoever runs incidents

The internal note is the short version for whoever picks the thread up next, and it does not replace the page. A note explains one reply, and the page settles the argument that reply started.

Write it down as a rule: if it changes what a customer is told, it goes where the team searches, and a call does not count.

How to disagree with a colleague in front of a customer

The customer should never watch two of you work out the answer, because a correction in front of them tells them the team is not sure. Keep the disagreement in an internal note on the thread, which settles it before the reply goes out and leaves one voice on the reply.

If the wrong answer already went out, the follow-up comes from the same person rather than a second one. “I have the details now” works. “That is not what we do” makes the team look like it is arguing, because it is.

A disagreement about policy belongs in the written decisions above, not in a thread with a customer on it. If it cannot be settled quickly, the customer gets a holding reply with a date.

When to take it off email

A long thread is not a customer problem. It is a sign that two people are typing past each other, and the fastest fix is a call.

Signal What it means What to do
The ninth reply adds no new information You are negotiating in a queue Fifteen minutes on a call
The same question appears twice One person has not read the other’s answer Call, then one line back in the thread
A reply starts with “as I said” The thread has become an argument Call, and drop the point
Two of your team are answering one customer The customer has two conversations running One owner, one reply

Whatever you decide on the call goes back into the thread in one line, or the next person starts from nothing. The customer gets the outcome, not the transcript.

Some teams cap a thread at three replies before moving to a call. The number matters less than writing one down. If the call needs someone who knows more, that handover is escalation without a tier system.

What a new person reads on day one

Guessing is the default for a new person on a shared address, and one page removes most of it.

Five things belong on that page:

  • The address they are on, and who else reads it.
  • The four tone defaults, including the greeting and the sign-off.
  • Which questions they can answer alone, and which need an internal note first.
  • Where decisions are written, and that a call does not count.
  • The one promise the team makes about reply time.

The first week is a reading week. Read the last fifty replies before writing many, draft the first few with a teammate checking them, and ask where an answer lives.

The test of the page is simple. If a new person has to ask what the team’s tone is, the page is missing a line rather than the person being slow.

Norms only hold if somebody enforces them

A norm nobody checks is a preference, and preferences lose to a busy Thursday. On a team of five the checker is usually the founder, because they care most about the customer and they are the only one who can say a promise was not yours to make. That works until they take a holiday, and then the norm is whatever the most confident person in the thread believes.

Write down what the founder is carrying.

Norm What enforces it when they are away
The tone defaults One page, and the week’s checker reads yesterday’s replies
Who may answer what The question table, and a note before anything that commits
Decisions The written page, because a call does not survive a holiday
The off-email threshold The number, so the ninth reply is not a judgement call

The enforcement habit is small. Once a week, someone reads the replies the team sent and lists every date, price and promise. Anything the team cannot keep gets raised that day.

The holiday test tells you whether the norms are real. If the team can run a normal week with the founder out of the thread, they are written down. If not, the missing page is the part that person is carrying.

Where Chirp fits

Chirp is a shared inbox for small software teams that track their work in Linear. Those norms need to sit where the team hits them: on the thread. An internal note is where a promise gets checked before it goes out, and it stays with the thread.

Press i to link, create or search a Linear issue, so a decision that changes the product is on the record rather than in a call. When every linked issue is Done or Canceled, the thread reopens with a drafted reply that names the issue, and the Issues view (g i) sorts linked issues by how many customers are waiting.

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. Gmail, Google Workspace and IMAP mailboxes connect, and the mailbox stays the source of record.

Next step

A norm that keeps breaking is often the wrong shape rather than the wrong people. If your team keeps missing the promise it wrote down, shared inbox versus help desk works through whether a queue would fix it.

FAQ

Who should be allowed to reply from a shared address?

Everyone who reads it, for the questions they can answer alone. Anything that commits the team to a date, a price or a feature starts as an internal note.

How do you keep the tone consistent when several people answer?

Fix the greeting, the way you say no, the promise line and the sign-off. Leave the rest to whoever is writing it.

When should a thread move off email?

When the replies stop adding information. If the latest reply repeats the one before it, move to a call and put the decision back in the thread in one line.