Why two people answer the same email, and five fixes

Five fixes, ranked by effort#

Fix 1: Write a precedence rule#

Decide which rule wins when rota and specialty overlap. A common choice: the rota person owns every new thread and pulls in the specialist, rather than the specialist grabbing billing emails directly. Or the reverse: specialist topics go straight to the specialist, and the rota person leaves them alone. Either works. What doesn't work is both.

Fix 2: Claim before you write#

Make "this is mine" visible before you start writing, not when you send. Depending on your tools, that might be a label with your name, a quick note in the team channel with the thread link, or a feature built for it. On mobile, the rule is: if you open it and intend to handle it, claim it right then, or leave it unclaimed for someone else.

Fix 3: Look at the thread before sending#

A two-second habit: before you press send on a shared-inbox reply, scroll to the bottom of the thread and check that nothing new has arrived from a teammate or the customer. This alone would have caught the incident above.

Fix 4: Route specialist topics at triage#

If billing emails go to Marcus, have the triager label them Billing as they arrive, so they leave the general queue. Auto-label rules can do some of this based on keywords or senders, with the triager catching the rest.

Fix 5: Pull cc'd conversations into the shared inbox#

When a customer emails people directly, the first person to reply should add or move the conversation into the shared address, so everyone sees one thread. Coaching beats rules here: explain why, and the habit spreads.

When it happens anyway: how to apologize#

Even with good process, duplicates will occasionally slip through. A short, clear correction is better than silence or a long explanation. Have the person whose reply was more accurate send it:

Hi [name],

Apologies for the two replies earlier — two of us picked this up at the same time.
To confirm: the duplicate charge has been refunded. It can take a few business
days to show on your statement, depending on your bank.

I'll be your contact on this from here. Let me know if anything else looks off.

Marcus

Three elements matter: acknowledge it briefly, state the correct answer clearly, and name one person as the contact from here on. Don't blame a colleague or the tools.

Running a lightweight review#

After a duplicate, a five-minute conversation is enough. Ask:

• What did each person see, and when?
• Which rule did each person think they were following?
• Which of the five causes was involved?
• What one change would have prevented it?

Write the change into your ownership rules. If the same cause shows up twice, move up the effort ladder.

Bottom line#

• Duplicate replies are process failures: invisible claims, stale views and conflicting rules.
• The cheapest fixes are a precedence rule and claiming before writing.
• Checking the thread right before sending catches most remaining overlaps.
• When it happens, the more accurate replier sends one brief correction and becomes the single contact.
• Review each incident in five minutes and update the rules, not the people.