# Sent an email to the wrong person: the first-hour checklist

> You sent a message to the wrong recipient. What to check, who to tell, whether to ask for deletion, and how to write the note, in order, for the first hour.

- Published: 2026-10-17
- Author: Koltrix Team
- Category: Team inbox
- Source: https://koltrix.com/blog/sent-an-email-to-the-wrong-person-the-first-hour-checklist

It happens to everyone who handles mail: a reply goes to the wrong Maya, an autocomplete picks the wrong address, or a quote for one customer lands in another customer's inbox. The send button cannot be undone once the short undo window has passed, so what matters next is a calm, ordered response.

This checklist is for the first hour. It assumes a small team with a shared inbox, but the steps work for one person too.

## Minute 0 to 5: stop and look

Do not write to anyone yet. First answer four questions:

1. **Who received it?** Read the To, Cc and Bcc lines of the sent message, not what you meant to type. Open the sent copy.
2. **What was in it?** Text, attachments, links, and anything quoted lower in the thread. People forget the quoted history.
3. **How sensitive is it?** Sort it into one of three levels (see below).
4. **Is anything still live?** A link that gives access to a document, a one-time code, a price, or a login detail may still work. That is the part you can often fix right away.

## Three levels of seriousness

| Level | Examples | Typical response |
|---|---|---|
| Low | A friendly reply, a scheduling note, a generic answer | Tell your team; a short note to the recipient is optional |
| Medium | A quote, a customer's name and order, an internal opinion | Ask the recipient to delete it, tell the affected person if it concerns them |
| High | Personal data about someone, contract terms, credentials, health or financial details | Act on the live items first, tell your lead at once, follow your data-incident rules |

Judge by what the recipient could do with it, not by how embarrassed you feel.

## Minute 5 to 15: close what is still open

If the message contained anything that still works, deal with it before you write a single apology:

- **A shared link:** change its sharing setting or revoke it, then create a new one for the right person.
- **A password or code:** change or expire it.
- **An attachment with data about a person:** note what it contained; you will need this for the next steps.
- **A price or offer:** decide whether you will honor it or withdraw it, and say which in your note.

Do this even if you plan to ask the recipient to delete the message. Asking is a request; revoking is a fix.

## Minute 15 to 30: tell your own side first

Tell a teammate or whoever leads the team before telling the customer. Say what was sent, to whom, when, and what is still live. Keep it factual and short. If you work in a shared inbox, add an internal note on the thread so everyone sees the same facts. Our post on [discussing a customer email internally](/blog/discussing-customer-email-internally) explains how to keep that note out of the customer's view.

If the message touched personal data about someone, check what your policy says about reporting it. Our [one-page email policy](/blog/a-one-page-email-policy-for-a-company-of-five) and [personal data rules](/blog/personal-data-in-email-plain-rules-for-small-teams) are good starting points, and [email and GDPR basics](/blog/email-and-gdpr-for-a-small-company-the-practical-basics) covers the legal side in plain words. Some rules have deadlines measured in days, so decide early, not late.

## Minute 30 to 45: write to the recipient

Write a short, plain note. Do not blame the recipient and do not over-explain. A good one has four parts:

1. **What happened:** "I sent you a message a few minutes ago by mistake."
2. **What to do:** "Please delete it and do not forward it."
3. **What is not needed:** "There is nothing you need to do about its contents."
4. **Thanks:** one line.

Example:

> Subject: Please delete my earlier message
>
> Hello, I sent you an email at 10:42 that was meant for someone else. Please delete it without reading further and do not forward it. I am sorry for the confusion, and thank you for your help.

Send it as a new message or a reply, whichever keeps it visible. Do not copy more people on it than needed, since each extra recipient is one more person who has now seen the mistake.

If the recipient is a customer and the content was about another customer, do not name the other customer in your note. Say only that the message was not meant for them.

## Minute 45 to 60: tell the person it was about

If the wrong message exposed someone else's details, that person usually deserves to hear it from you, not later from someone else. Say what was shared, with whom, what you did about it, and what they can do. Offer a way to reach you. Our post on [apology emails that rebuild trust](/blog/apology-emails-that-rebuild-trust) shows how to keep that note honest and short.

For a low-level slip that only affected a teammate or a vendor, a one-line heads-up is enough.

## What not to do

- **Do not send a "recall" request and hope.** Most mail systems cannot pull a message back from another organization, and a recall notice can draw attention to it.
- **Do not edit or delete the sent copy.** You need it as a record of what went out.
- **Do not reply all** to the thread to apologize.
- **Do not hide it.** A mistake reported in the first hour is usually forgotten by the next day. One discovered later looks worse.

## Make the next one less likely

After the hour, spend ten minutes on prevention:

- **Slow the send for external mail.** A short delay before sending gives you a window to catch a wrong recipient. Check whether your tool offers an undo period and how long it lasts.
- **Read the To line out loud** before sending anything with prices, personal data or attachments.
- **Be careful with autocomplete** when two contacts share a first name. Use the full address for sensitive mail.
- **Keep Cc and Bcc deliberate.** Our [rules for Cc and Bcc](/blog/team-cc-bcc-rules) cover when each is the right choice.
- **Remove old attachments** from long threads before replying.

Write down what happened in a few lines: the cause, what you did, and what you changed. That note is your evidence if a customer or regulator asks.

## Key takeaways

- Look first: who received it, what was in it, and what still works.
- Fix live items (links, codes, offers) before you apologize.
- Tell your own team, then the recipient with a short note, then anyone whose data was exposed.
- Do not hide it, delete the sent copy, or rely on a recall.
- Add one small safeguard afterwards, such as a short send delay.