KoltrixWriting replies together in a shared inbox without double sends
Two people answer the same customer, or one sends over another's edit. Simple rules for claiming, drafting and reviewing replies so a shared inbox speaks once.
On this page(9 sections)
- Why double sends happen
- Rule 1: claim before you write
- Rule 2: one writer per draft
- Rule 3: separate "ready for review" from "send"
- Rule 4: check the recipients before you send
- Rule 5: send windows are for catching mistakes
- A lightweight workflow you can adopt this week
- When to use a rota instead
- Key takeaways
Every team that shares an inbox eventually sends the same customer two answers. They arrive a few minutes apart, they disagree on a detail, and the customer replies to the one that was wrong.
It is not a software problem or a character flaw. It happens when two people can both see an open message and neither can see that the other has started. This post lays out a small set of habits that stop it, and shows how to make a reply a team effort when one person should not write it alone.
Why double sends happen
There are four common causes:
- Silent starts. Someone opens a thread, begins drafting and says nothing. A colleague sees the unanswered message and starts too.
- Edits that overwrite. Two people change the same draft, and the later save wins.
- Sending someone else's draft. A person sees a half-finished draft, finishes it, and sends it before the writer does.
- Replying to the wrong message. With several people in a long thread, a reply goes to an earlier message, or to everyone when it should have gone to one person.
Each one is solved by making the state of a reply visible: who has it, what stage it is in, who may send it.
Rule 1: claim before you write
Before you start a reply, make it obvious that you have it. The exact mechanism matters less than the habit.
- Assign the conversation to yourself, if your inbox supports assignment.
- If it does not, add a label such as
mine-sam, or leave a short internal note. - Claim on the way in, not after you have written half the answer.
The first claim wins. If you open a thread that already has an owner, ask them instead of starting your own. Ownership rules for shared inboxes covers how to write the policy down.
Rule 2: one writer per draft
A reply has one author at a time. Everyone else contributes through comments, not edits.
- Put suggestions in an internal note, not in the draft, and keep it clearly separate from what the customer will see. See discussing customer email internally.
- If two people really must write together, share the draft in a document the team uses for editing, and paste the final text into the reply when you are done. One person still does the pasting and the sending.
- Never edit a colleague's draft without saying so first.
Rule 3: separate "ready for review" from "send"
For anything with risk, such as a refund, a legal question, a security report or an unhappy customer, split the work into two roles:
- Writer: drafts the reply and marks it ready.
- Approver: reads it, edits only for clear mistakes, and sends it.
A simple convention is enough: a label like needs-review that the writer adds and the approver removes when the reply is sent. Anyone who sees a draft without that label leaves it alone.
This is also the right shape for AI drafts. An assistant can write the first version; a person owns the review and the click. Who owns an AI-drafted reply goes deeper, and the review checklist takes thirty seconds.
Rule 4: check the recipients before you send
Most embarrassing sends are recipient mistakes, not wording mistakes.
- Look at the To and Cc lines every time. Do not rely on a pre-filled list in a long thread.
- Prefer replying to the sender over replying to everyone. Add people on purpose.
- If a thread mixes the customer and internal colleagues, take the internal discussion out of the thread entirely and use notes or chat.
- Pause on anything that includes a new external address you did not type yourself.
Rule 5: send windows are for catching mistakes
An undo window of a few seconds after clicking send catches a surprising number of errors: wrong recipient, missing attachment, a draft that was not finished. If your tool offers one, turn it on and use the pause.
The same idea works at team level. For high-stakes replies, agree on a second look before sending, even if it only takes a minute.
A lightweight workflow you can adopt this week
- A new message arrives and is unclaimed.
- Someone claims it (assign or label). Others leave it alone.
- The owner writes the reply and, if it needs a second pair of eyes, adds
needs-review. - The approver reads, edits only what is wrong, sends, and removes the label.
- The owner or approver archives the thread when the customer is done.
At the end of each week, look for threads where two people replied, or where a reply sat unclaimed for a day. Those tell you which rule is missing. A weekly review of the shared inbox is a good place to do it.
When to use a rota instead
If claiming costs more attention than it saves, because the volume is high and the work is routine, assign ownership by rota instead of by choice. Each person gets a time slot or a category and is the default owner. Building an email triage rota shows how.
Key takeaways
- Double sends come from invisible state: nobody can see who has started a reply.
- Claim first, write second, and treat the first claim as final.
- One writer per draft; everyone else uses internal notes.
- Separate "ready for review" from "send" for risky replies, including AI-written ones.
- Check recipients every time, and use any undo window you have.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
