How To Recall An Email In Outlook
Learn how to recall an email in Outlook, when it actually works, why it often fails, and what follow-up message to send if the recall does not succeed.
How to recall an email in Outlook
Outlook recall attempts to delete or replace a sent message in the recipient’s mailbox. It works only in specific Microsoft Exchange or Microsoft 365 conditions.
Most people hear “recall” and picture a magic eraser. That is not what Outlook does. Outlook sends a second instruction message that asks the recipient’s mailbox to remove the first one. If the stars align, the original disappears. If they do not, the recipient gets a recall notice that politely announces your mistake.
I have watched recalls save someone from sending a spreadsheet to the wrong internal distro. I have also watched recalls make a situation worse, because the recipient noticed the recall before they noticed the original. The difference is almost always environment and timing, not how “fast” you click.

Before you try: the recall checklist that actually predicts success
If you only remember one thing: recall is mostly an internal Exchange feature. It is not built for Gmail addresses, external clients, or messages already read. Here is what I check before I even open the Sent Items folder.
- You and the recipient are in the same org: Both mailboxes are on Microsoft Exchange (usually Microsoft 365 in the same tenant). Recalls against external recipients almost always fail.
- You are using classic Outlook for Windows: The most consistent recall controls live in the desktop app. “New Outlook” and Outlook on the web have different behavior.
- The recipient has not opened the email: Once it is read, recall usually fails. Even “preview pane read” can count depending on settings.
- The email is still in the Inbox: If rules moved it to a folder, recall success drops. I have seen rules that auto-file invoices, and the recall never touches them.
- No protected message restrictions: Sensitivity labels, encryption, or some compliance policies can block recall or replacement.
Users should verify the recipient type (internal vs external) before relying on recall for sensitive content.
Step-by-step: recall in classic Outlook for Windows (the one people mean)
This is the path I use when someone pings me with “I sent it to the wrong Alex, help.” It is fast once you have done it a few times, but the options matter.
- Open Outlook (classic) for Windows.
- Go to Sent Items.
- Double-click the sent email to open it in its own window (do not use the reading pane).
- On the ribbon, select File.
- Select Info.
- Click Resend or Recall.
- Choose Recall This Message….
- Select one option:
- Delete unread copies of this message (use this when you just want it gone).
- Delete unread copies and replace with a new message (use this when you need to correct something).
- Optional but useful: check Tell me if recall succeeds or fails for each recipient.
- Click OK.
If you pick “replace,” Outlook opens a draft. This is where people accidentally make things worse by writing an apology novel in the first line. Keep it clean and procedural. A replacement message that has worked for me in internal settings looks like this:
Subject: Updated: Q2 Headcount file (correct version)
Body: Please disregard my previous email. Attaching the corrected file. Thanks.
Short. No theatrics. It reduces the chance someone forwards your first email “for visibility.”
How to check if the recall worked
When you tick “Tell me,” Outlook sends you a status message per recipient. In practice, those receipts can arrive staggered, especially if the recipient is offline or on a slow connection. I have seen a recall show “Succeeded” for five people and “Failed” for one because they opened it on mobile the second it arrived.
If the message was sent to a group, do not assume uniform results. One person reading it can turn a small error into a meeting agenda item.
Why recalls fail (the reasons people do not want to hear)
Most recall failures are not user error. They are environment reality.
- External recipients: If you sent it to a vendor, client, or personal address, recall is effectively a no. Plan for damage control instead.
- Recipient already read it: Outlook cannot unsee what a person already opened. It can only attempt deletion of unread copies.
- Rules and filters: If the message moved out of Inbox, recall often misses it. This is common in orgs where people auto-file anything from “Finance,” “HR,” or specific senders.
- Public folders, shared mailboxes, or delegates: I have seen recalls behave unpredictably when mail is accessed via delegation or shared mailbox workflows.
- Mobile and different clients: If the recipient reads mail in a non-Outlook client or certain mobile scenarios, recall success drops.
- Modern compliance controls: Encryption, sensitivity labels, and retention policies can prevent removal or replacement.
If your recall fails, act like the email is already screenshotted. Because sometimes it is.

New Outlook and Outlook on the web: what you can do instead
I get asked this weekly: “Where is recall in the new Outlook?” The answer depends on what Microsoft has rolled out in your tenant, but the reliable tool in Outlook on the web is usually Undo send, not recall.
Enable “Undo send” (prevention, not recall)
Undo send is a short delay that holds the message before it leaves. It is not retroactive. It is the closest thing to a true safety net for the “wrong attachment” moment.
- Open Outlook on the web.
- Go to Settings (gear icon).
- Search for Undo send.
- Set the cancel period (often up to 10 seconds, depending on your environment).
- Save.
I have watched that 10 seconds save someone who pasted confidential notes into the wrong thread. Not once. Multiple times. It only helps if you notice instantly, but people often do.
My “recall failed” playbook (what I send next)
If recall fails, you need a follow-up that is calm and specific. The worst follow-up is vague (“Please ignore my previous email”), because it invites curiosity. The second worst is over-explaining, because it turns your mistake into a narrative.
Here are two templates I have used in real workplace situations.
1) Wrong recipient (internal)
Subject: Please delete: sent in error
Body: Hi [Name], I mistakenly sent you an email intended for someone else. Please delete it and do not forward. Thank you.
That is it. If the content is sensitive, you may also need to alert your security or compliance team, but the recipient message stays simple.
2) Wrong attachment (internal or external)
Subject: Correction: updated attachment
Body: Please use the attached file and disregard the previous attachment. The body of my earlier email is unchanged.
Notice what I did not write: “Sorry!!!” three times, or “I was rushing,” or “Please don’t judge me.” Those lines feel human, but they also encourage replies.
Preventing the need to recall (the boring habits that actually stick)
I keep three safeguards in place because recall is too unreliable to bet your day on.
- Delay Send rule (desktop): I set a 1 to 2 minute delay for outbound messages to large groups or external domains. It creates a personal buffer. If you often email clients, this is worth it.
- Attachment sanity check: If the email mentions an attachment, I add it last. I also scan the filename out loud before sending. It feels silly until it prevents “final_FINAL2.xlsx” going to the CEO.
- Proofread the riskiest line: The greeting and the ask. That is where the harm happens. If you want a quick quality gate, tools like an Email Proofreader can catch tone mismatches and missing context before you hit send.
If you are writing high-stakes messages under time pressure, I have found that drafting in a separate window helps. Even better, use an AI Email Assistant to generate a clean first pass and then you edit for accuracy and policy compliance. For more structured drafting workflows, the AI Email Writer pages are useful as a starting point, especially when you need consistent phrasing across a team.
A realistic expectation: recall is a tool, not an eraser
If you are on Exchange, using classic Outlook for Windows, and the recipient has not read the message, recall can quietly solve your problem. When those conditions are not true, treat recall as a courtesy attempt and move straight to containment: follow-up, clarification, and if needed, escalation through your organization’s process.
The good news is that most “recall moments” are preventable with small workflow changes. The better news is that the fix is usually a 2-line email, not a career-ending event.