How to recall an email in Outlook (new Outlook and classic)

Can you actually recall an email in Outlook?

You hit Send, and the regret arrives a half-second behind it. The wrong attachment. A figure that should have read 15, not 50. A reply that went to the entire distribution list instead of one person. The name of the client spelled wrong in the very first line. The reflex is immediate and universal — get it back before they see it — and it sends most people straight to a search box, typing "how to recall an email in Outlook" and hoping there's a single button that reaches into someone else's mailbox and makes the mistake disappear.

Here is the honest answer, up front, because it saves you a great deal of frantic clicking: whether you can recall an Outlook email at all depends entirely on which Outlook you're using and what kind of account you're on, and even in the best case it's a coin flip rather than a guarantee. There are essentially two different Outlooks living under the same name in 2026, and they behave completely differently on this one question. Classic Outlook — the long-standing desktop application for Windows — has a genuine "Recall This Message" command. New Outlook (the redesigned app that Microsoft is rolling everyone toward) and Outlook on the web do not have it at all. They replaced it with Undo Send, which is a different mechanism with a different promise.

That single fork is the most important thing to understand here, and it's what nearly every quick tutorial glosses over. If someone tells you to click "Actions" then "Recall This Message" and you can't find it, you're almost certainly in new Outlook or on the web, where that menu doesn't exist. And if you do find it — because you're in classic Outlook on a work account — the command only attempts a recall under narrow conditions, and outside them it fails, sometimes after tipping off the very recipient you wanted to keep in the dark.

The deeper reason comes down to how email works as a system, and it explains why recall is fragile everywhere it's offered, not just in Outlook. Email is open and decentralized: when you send a message, it leaves your control, travels through servers you don't own, and lands in a mailbox you can't touch — often on an entirely different provider. There's no central switchboard that can reach across all those independent systems and pull a message back. The one exception is when both sender and recipient live inside the same closed system — the same Microsoft 365 or Exchange organization — because then a single server controls both ends. That's exactly the condition classic Outlook's recall depends on, and exactly why it stops working the moment your recipient is anywhere else.

So the practical version of "how to recall an email in Outlook" is really several questions stacked on top of each other. Which Outlook am I using? Is my account the kind that even supports recall? If it does, how do I run it and what are the odds it works? If it doesn't, what's the Undo Send alternative and how do I turn it on? And — the question most people eventually need — what do I do when none of it helps and the email is simply gone? This guide answers all of them, plainly, then shows you a way to think about the whole problem so you stop betting your reputation on a feature that fails more often than it works.

Which version of Outlook are you using?

Before you can recall anything, you have to know which Outlook is on your screen, because the answer changes everything that follows. Microsoft has spent the last few years moving people from the old, feature-rich desktop application to a rebuilt, lighter one — and confusingly, both are called "Outlook." They look similar at a glance but differ sharply on recall, so this is the first fork in the road, not a detail to skim past.

Classic Outlook is the traditional Windows desktop program, the one that has shipped with Microsoft Office and Microsoft 365 for years. It has a dense ribbon across the top with tabs like File, Home, Send / Receive, and View, and it stores a local copy of your mail. This is the only version of Outlook that has a real "Recall This Message" command — and even then, only on the right kind of account. If your ribbon is busy and you can open a sent message into its own window with a Message tab full of options, you're very likely in classic Outlook.

New Outlook for Windows is the redesigned app Microsoft is steadily making the default. It's visually cleaner, faster to load, and built on much of the same technology as Outlook on the web. There's usually a "New Outlook" toggle in the top-right corner of the window that flips between the two. Critically, new Outlook does not have the classic recall command at all. It offers Undo Send instead — a short delay you can configure — and that's the only retraction tool it provides.

Outlook on the web (sometimes still called Outlook Web App or OWA) is what you use in a browser at outlook.office.com for work accounts or outlook.com for personal ones. Like new Outlook, it has no "Recall This Message" feature — only Undo Send. Because new Outlook and the web share the same foundation, they behave almost identically on this topic: no recall, just a configurable send delay.

Then there's the account question, which sits on top of the version question. Recall — where it exists, in classic Outlook — only functions on a Microsoft Exchange or Microsoft 365 work or school account, and only when your recipient is on the same one. A personal Outlook.com, Hotmail, Live, or MSN account cannot recall at all, regardless of which app you open it in. So the real question is two-part: not just "which app?" but "which app, and what kind of account?" The table below maps every common combination to what you can actually do.

How do you recall a message in classic Outlook?

If you're in classic Outlook on a work Microsoft 365 or Exchange account, you have access to the genuine recall command — the one that actually tries to delete a message from a recipient's mailbox after it's been delivered. It's worth setting expectations before you start: this works only inside your own organization, only while the message is still unread, and it fails often. But when the conditions line up — an internal email to a colleague who hasn't opened it yet — it can quietly pull the message back, and that's worth knowing how to do.

The first thing to understand is where the command lives, because this trips people up. You don't recall a message from the inbox or the reading pane; you recall it from your Sent Items folder, and you have to open the message into its own window first. The recall option does not appear in the side preview pane — you must double-click the sent message so it opens in a full window of its own. Only then does the Message tab with the Actions menu appear. Miss that step and you'll swear the feature is missing when it's one click away.

Once the message is open in its own window, you head to the Message tab on the ribbon. In the Move group, you click "Actions" — it may show as a small dropdown — and then choose "Recall This Message." If your Outlook uses the Simplified Ribbon (a more compact toolbar), the path is slightly different: click the three-dot "More" menu, then Actions, then "Recall This Message." The destination is the same; only the route changes depending on how your ribbon is configured.

Outlook then offers you two choices, and the difference matters. The first, "Delete unread copies of this message," attempts to remove the email from the recipient's inbox entirely. The second, "Delete unread copies and replace with a new message," removes the original and lets you compose a corrected version to send in its place — useful when you sent the wrong figure or attachment and want to follow up immediately with the right one. There's also a checkbox to be told whether the recall succeeded or failed for each recipient; leave it ticked, because without it you're flying blind on whether the recall actually worked.

After you confirm, Outlook fires off the recall request and, if you asked for it, sends you a report on each recipient. Here's the part to brace for: the recall is an attempt, not a result. It races against the recipient opening the message, and depends on conditions you can't see from your side. The steps below walk through the exact sequence, but read the next section on when recall works and fails before you pin any hopes on it.

1. 1

   Open your Sent Items folder

   In classic Outlook, go to the folder pane on the left and click Sent Items. Recall starts from the copy of the message you sent, not from your inbox or the reading pane.

2. 2

   Open the message in its own window

   Double-click the email you want to recall so it opens in a full, separate window. This step is required — the recall command does not appear when the message is only shown in the side preview pane.

3. 3

   Open the Actions menu

   On the Message tab, find the Move group and click "Actions." On the Simplified Ribbon, click the three-dot "More" menu first, then Actions. Choose "Recall This Message."

4. 4

   Choose delete or replace

   Select "Delete unread copies of this message" to remove it, or "Delete unread copies and replace with a new message" to send a correction in its place. Keep the box that reports success or failure ticked.

5. 5

   Confirm and watch for the report

   Click OK (and send your replacement if you chose that option). Outlook attempts the recall and, if requested, emails you a per-recipient report telling you whether each one succeeded or failed.

When does Outlook recall actually work — and when does it fail?

This is the section that separates a useful answer from a misleading one, because "yes, Outlook can recall email" is technically true and practically deceptive. The classic recall command works inside a narrow box of conditions, and the moment any one of them is violated, it fails. Understanding the box matters more than knowing the clicks, because it tells you in advance whether you're wasting the precious seconds you could be spending on damage control instead.

The first and most important condition is that you and your recipient must be on the same Microsoft 365 or Exchange organization. Recall is a server-side trick: a single mail server controls both your mailbox and theirs, so it can reach into the recipient's inbox and delete the message. The instant the recipient is outside your organization — a client, a vendor, anyone with a different email domain — there's no shared server, nothing to issue the command, and the recall can't happen. This alone rules out most real-world recall attempts, since most regrettable emails go to people outside our own company.

The second condition is that the message must still be unread. Recall works by deleting an unopened message before the recipient sees it. If they've already opened it — even in a preview pane, even for a second — the recall of that copy fails. This is a race you often lose without knowing it, since you have no way to tell whether the recipient happened to be looking at their inbox the moment your email landed.

Beyond those two, a string of smaller conditions can quietly break a recall even within your own organization. If the recipient has a rule that automatically moved your message to another folder, the recall may miss it. If they're reading on a phone, on the web, or in a non-Outlook client, the recall can fail. If the message was protected by sensitivity labels or information-protection policies, recall is blocked. If your IT administrator has disabled or restricted recall, it won't run at all. And the recall has a time limit — if it can't complete within roughly a day, it's marked as failed. The table below lays out the conditions side by side so you can read your own odds at a glance.

How do you set up Undo Send in new Outlook and on the web?

If you're in new Outlook for Windows or Outlook on the web, the classic recall command isn't hiding from you — it genuinely doesn't exist in these apps. What you get instead is Undo Send, and the good news is that it's both more reliable than recall and entirely within your control. The catch is that the window is short — a maximum of 10 seconds — and on some accounts it isn't switched on by default, so the single most useful thing you can do right now is open Settings and turn it on at its longest setting.

Undo Send works on a completely different principle from recall, and that difference is exactly why it's dependable. Rather than chasing a delivered message into someone else's inbox, it holds your outgoing email on Microsoft's side for a few seconds before it's actually sent. During that buffer, the message hasn't gone anywhere — so when you click "Undo," you're not retracting anything, you're aborting a send that hadn't happened yet. There's no race against the recipient, no dependency on their client, no shared-organization requirement. Inside the window it works every time, for any recipient on any provider. Outside it, the email is gone — but the window is yours to set.

Ten seconds is shorter than Gmail's 30, which is a real limitation worth naming, but it's still long enough to catch the most common mistakes: a wrong recipient you spot the instant the message leaves, an attachment you suddenly remember you forgot, a subject line with the wrong client's name. The steps below set it to the maximum in new Outlook and on the web; the path is nearly identical in both because they share the same settings engine. Do this once and it applies to that account from then on.

1. 1

   Open Settings

   In new Outlook or Outlook on the web, click the gear icon in the top-right corner to open Settings. In new Outlook you may need to choose "View all Outlook settings" at the bottom of the quick panel.

2. 2

   Go to Mail, then Compose and reply

   In the Settings window, select "Mail" in the left column, then choose "Compose and reply." This is where the send behavior options live.

3. 3

   Find the Undo send slider

   Scroll to the "Undo send" section. You'll see a slider that sets the cancellation period in seconds, from 0 up to a maximum of 10.

4. 4

   Set it to 10 seconds

   Drag the slider all the way to 10 — there is no downside to the maximum beyond your email taking a few extra seconds to leave, a trade almost everyone is glad to make.

5. 5

   Save

   Click Save to apply the change. From now on, every email you send shows an "Undo" option for the full 10 seconds before it actually goes out.

How do you actually undo a send in new Outlook?

With the window set, using it is the easy part — but it relies on speed and on knowing precisely where to look, because the opportunity vanishes the moment your timer expires. After you click Send in new Outlook or on the web, a small notification appears, usually at the bottom of the screen, confirming the message was sent and offering an "Undo" link. Clicking "Undo" within your window is the entire trick — it cancels the send and reopens the message as a draft you can fix or discard.

The notification only lingers for the length of the window you configured. If you set 10 seconds, you get 10 seconds; if it's still at a lower default, you get less. When you click "Undo," the message you just "sent" reopens in the compose window exactly as it was, and as far as your recipient is concerned it never existed. From there you correct the recipient, fix the typo, attach the file you forgot, and send again — or simply close and delete it. There's no recall report to wait for and no recipient to notify, because nothing was ever delivered.

The mental model here is the opposite of recall. With recall, even a perfectly timed click can fail, because the outcome depends on conditions outside your control — the recipient's read status, their client, your shared organization. With Undo Send, the only variable is you: whether your hand reaches the "Undo" link before the clock runs out. If you click in time, it works, full stop. That's why the 10-second cap matters so much — the feature's only weakness is the clock, so the less clock you have, the less it can save you.

1. 1

   Send your email

   Compose and click Send as usual. Stay on the screen — the undo notification lives there and disappears if you navigate away or close the window.

2. 2

   Spot the notification

   Look to the bottom of the screen for the "Sending…" or "Message sent" notification with an "Undo" link. It appears the instant you send.

3. 3

   Click Undo before the timer ends

   Click "Undo" within your window (up to 10 seconds). The faster you react, the safer you are — treat it as a short countdown, not a comfortable buffer.

4. 4

   Fix or discard the draft

   The message reopens as a draft. Correct whatever went wrong — recipient, subject, body, attachment — then send again, or delete it entirely if you've thought better of it.

Is there cloud-based message recall in Microsoft 365?

There's an important wrinkle for work and school accounts that most consumer guides miss entirely, and it's genuinely better news than the classic-recall story: Microsoft rebuilt message recall for Exchange Online into a cloud-based system, and it's meaningfully more effective than the old desktop version. If your organization runs on Exchange Online, the recall you trigger from classic Outlook may be using this newer engine under the hood, which changes the odds in your favor — though it's still bounded by the same organizational walls.

The key difference is where the recall happens. The old classic recall worked client-to-client: it sent a special message that the recipient's Outlook had to process, which is why it broke whenever the recipient was on a phone, on the web, or in a different app. Cloud-based recall, by contrast, runs in the recipient's mailbox in the cloud itself. When you initiate it, an Exchange Online agent works to delete the original message directly from each recipient's mailbox, and the next time their email client syncs, the message is simply gone — no matter which client they use. Microsoft has said the cloud-based version is more than twice as effective at successfully recalling messages as the old one.

It also lifts two of the old limitations that caused the most failures. Cloud-based recall can pull back messages that have already been read — a significant change, since read status was the single most common reason classic recall failed (though administrators can choose to disable recall of already-read mail). And it can reach messages that rules moved into sub-folders, rather than only catching mail still sitting in the inbox. Both of these close gaps that doomed countless classic recalls.

You also get far better visibility. After you initiate a recall, Exchange Online sends the initiating mailbox a link to a web-based message recall report showing the status for every recipient — succeeded, failed, or pending — instead of the old trickle of per-recipient emails. If the recall can't complete within about 24 hours, it's marked as failed. The crucial limit remains, though: cloud-based recall still only works within your own Microsoft 365 organization. The moment a recipient is external, you're back to no recall at all, because the cloud agent has no authority over a mailbox your company doesn't own.

Can you recall an Outlook email on your phone?

Most regrettable emails are sent from a phone, in a hurry, with a thumb — which makes mobile the place you most need a quick way out, and also the place Outlook gives you the least. The short answer is that the Outlook mobile apps for iOS and Android have no "Recall This Message" feature at all. There's no Actions menu, no recall command, no cloud-recall trigger from the phone. If you're hunting for recall in the mobile app, you can stop — it isn't there.

What the mobile apps do offer is a brief, built-in undo at the moment of sending, similar in spirit to new Outlook's Undo Send. After you tap the send arrow, a short notification typically appears at the bottom of the screen giving you a moment to tap "Undo" and pull the message back before it leaves. It's quick — a handful of seconds at most — and you can't extend it the way you can nudge the desktop slider to 10. So mobile gives you a real, dependable undo, but a fleeting one, and you have to be fast on the draw.

There's a useful nuance for work accounts. Because cloud-based recall in Exchange Online happens in the mailbox rather than the client, the recipient's device no longer matters — if your colleague reads on their phone, a cloud recall you triggered from your desktop can still reach the message once their mailbox syncs. But that's about the recipient's phone, not yours: you still can't initiate a recall from the Outlook mobile app. The practical playbook is simple — react instantly to the undo notification when you can, and for anything that matters, compose it on the desktop where you have the 10-second buffer or a real send delay.

What do you do when recall fails or the window has passed?

This is the scenario that brought a lot of people to this page, and it deserves a straight answer rather than false hope. If your recall failed, if the recipient was external, or if the Undo Send window has already closed, the email has been delivered and you cannot get it back. There is no hidden setting, no support ticket, and no third-party tool that will pull a delivered message out of an external inbox. The faster you accept that, the faster you can do the thing that actually helps: damage control.

The right move depends entirely on what went wrong, so diagnose it honestly before you act. The worst instinct is to fire off a flurry of panicked follow-ups, which usually draws far more attention to the mistake than the mistake itself would have on its own. Take a breath, decide which of the situations below you're in, and respond once, calmly, in a way that fits the severity.

If you sent to the wrong person, a brief, polite note is almost always the cleanest fix: "Apologies — that last email wasn't meant for you; please disregard and delete it." Most people will, without a second thought. If the email carried sensitive or confidential information to the wrong recipient, the stakes are higher: contact them directly, ask them to delete it, and if it involves regulated data or your workplace, loop in your IT or security team immediately, because this may need to be handled as a data-exposure incident rather than a matter of etiquette. On a work Microsoft 365 account, your administrators have tools you don't — they can sometimes search for and purge a message across internal mailboxes — so a fast call to IT beats anything you can do from your own settings.

If the problem was a typo, a wrong figure, a broken link, or a missing attachment, the best response is usually a short, low-drama follow-up in the same thread that corrects the record: "Quick correction — the link in my previous email was wrong; here's the right one," or "Please use the attached version; the file I sent a moment ago was an earlier draft." Keeping the correction in the same thread puts everything in one place and signals that you're on top of it. There's no need to grovel for a small slip — just fix it and move on.

If you sent something in anger or wrote something you genuinely regret, this is where a real apology matters and where it pays to slow down. Don't dash off a defensive explanation. Write a clear, accountable message that owns what you said, acknowledges its effect, and skips the excuses — and say it once. A well-handled apology can leave a relationship stronger than before the slip, whereas a delivered email left unaddressed tends to fester. And if the mistake was a reply-all, your goal shifts from retraction to containment: a single brief "Apologies for the noise — replying off-thread now" beats five separate corrections.

It's also worth resisting two temptations, because both make things worse. The first is silence — hoping the recipient won't notice. Sometimes they won't, but if the error matters, an uncorrected mistake reads as careless once spotted, whereas a prompt correction reads as conscientious. The second is over-explaining: three paragraphs about how the mistake happened and why it wasn't really your fault. Recipients almost never want the backstory; they want the corrected information or a clean acknowledgment. Keep the follow-up shorter than your instinct says, fix the substance, and let it go.

How does Outlook recall compare to Gmail's undo send?

Because Outlook is the one major email client that advertises a true recall feature, it's often held up as the gold standard Gmail lacks. The reality is more nuanced, and comparing the two directly shows why "Outlook can recall and Gmail can't" is misleading. The two approaches solve the same problem from opposite ends, with very different odds of success.

Outlook's classic "Recall This Message" is a true post-delivery recall: it tries to reach into a recipient's mailbox and remove a message that's already there. That sounds more powerful than Gmail's approach, and in the narrow case of an unread internal email it can be. But it works only inside a tightly fenced set of conditions — same organization, message unread, compatible setup — and outside them it fails, often while notifying the recipient that you tried. It's a best-effort tool that succeeds some of the time and embarrasses you the rest. The cloud-based version on Exchange Online improves the odds, but only for internal recipients.

Gmail makes no attempt at any of that, and that's precisely its strength. Gmail's Undo Send is a pre-delivery delay: it holds the message for up to 30 seconds before sending, so the "undo" cancels a send that hasn't happened yet. It works for every recipient, on every provider, every single time — within its window. New Outlook and the web copied this model, though they cap it at 10 seconds rather than Gmail's 30. So the honest comparison isn't about which client is more powerful; it's that Outlook offers a fragile, conditional retrieval after sending, while the Undo Send model offers a dependable cancellation before sending. For most real-world mistakes — caught in the first few seconds — the pre-delivery model wins. For the rarer case of realizing an hour later, neither helps, and you're back to a follow-up.

Why is Outlook recall not working — and how do you fix it?

If you tried to recall a message and it didn't work — or you can't even find the command — the cause is almost always one of a handful of ordinary things rather than a bug. Run through this list before assuming something's broken; in most cases recall is behaving as designed, and the issue is a condition you didn't realize applied.

• You're in new Outlook or on the web. Neither has a recall command at all — only Undo Send. Fix: toggle off "New Outlook" to use classic (if your account supports it), or rely on the Undo Send delay instead.
• Your recipient is external. Recall only works inside your own Microsoft 365 or Exchange organization. If you emailed anyone on a different domain, recall can't reach them. Fix: there's no fix — pivot to a follow-up.
• The message was already read. Classic recall only deletes unread copies. If the recipient opened it before the recall ran, it fails for that copy. (Cloud-based recall on Exchange Online can reach read mail, if your org has it.)
• You're on a personal account. Outlook.com, Hotmail, Live, and MSN accounts can't recall — recall needs an Exchange/Microsoft 365 organizational mailbox. Fix: use the Undo Send delay on the web instead.
• You opened the message in the preview pane. In classic Outlook, the recall command only appears when you double-click the sent message into its own window. Fix: open it fully, then use Message → Actions.
• Your admin disabled recall. Some organizations turn recall off or restrict it by policy. Fix: ask your IT team whether recall is enabled and under what conditions.
• The recipient used a non-Outlook or mobile client. Classic client-side recall can fail when the recipient reads in a different app. Fix: nothing from your side — this is one of the gaps cloud-based recall was built to close.

What are the limits and best habits for unsending in Outlook?

Recall and Undo Send are useful safety nets, but both are narrow, and treating either as a catch-all leads straight back to the panicked "how do I recall this?" moment. The healthier approach is to understand their hard limits and then build a couple of habits that stop most mistakes from ever needing a retraction in the first place. These tools should be your last line of defense, not your only one.

State the limits plainly. Classic recall only works inside your organization, only on unread mail, and fails often — and can tip off the recipient when it does. Undo Send caps at 10 seconds in new Outlook and the web, lives only on the screen where you sent, and is gone the instant the window closes. Mobile gives you only a brief undo and no recall. None of that makes these tools worthless; it just means you should know their edges and not bet anything important on them.

The habits below cost almost nothing and dramatically reduce how often you'll ever reach for recall. Most sent-email disasters come from sending too fast, and a few small frictions catch the overwhelming majority of them before they leave your outbox.

• Turn Undo Send on and max it. In new Outlook or the web, set the slider to 10 seconds today — it's the single highest-value change here, and you only do it once.
• Add recipients last. Write and proofread with the "To" field empty, then add addresses just before sending. You can't send to the wrong person too early if no one's in the field.
• Attach files before you write "attached." The classic "please find attached" with nothing attached is avoidable: attach first, reference second.
• Reread the first line and the recipient before clicking. A two-second glance at who it's going to and how it opens catches most embarrassing sends.
• Be deliberate with Reply All. Pause and confirm whether the whole thread really needs your reply — reply-all regret is one of the most common reasons people search for recall.
• Use Schedule Send for anything sensitive or late-night. Scheduling a message for the morning gives you hours, not seconds, to reconsider — see our guide on how to schedule send an email in Outlook.
• Set up a delay rule in classic Outlook. Classic Outlook can hold all outgoing mail for a few minutes via a rule, giving you a far longer window than recall ever could — covered in the scheduling guide above.

How does AI Emaily give you a real send-delay, undo, and audit across every account?

Everything above is the best you can do inside Outlook's own walls: try a recall that probably won't work, or lean on a 10-second Undo Send and react fast. But notice the shape of the problem — you're either gambling on a conditional, often-embarrassing recall, or relying on a brief manual reflex that a smarter setup could turn into real breathing room. That gap is part of what AI Emaily is built to close. AI Emaily is an AI-native email client that connects to every provider — Outlook, Gmail, iCloud, Fastmail, Proton, and any IMAP inbox — so it works on top of the email you already use rather than asking you to switch addresses.

The most relevant piece for this topic is the send model. AI Emaily gives you a configurable send-delay that you control — not a fixed 10-second cap and a notification you have to catch, but a buffer you set to match how you actually work, paired with a genuine undo and a full audit trail of what was sent and when. Because the client mediates your sending, the "oops" window stops being a frantic few seconds in the corner of the screen and becomes a deliberate safety layer you can lean on. You get back the thing both Outlook's recall and its short undo can't quite offer: enough time to catch the wrong recipient or the missing attachment without racing a countdown or praying the recall lands.

The bigger shift comes from how AI Emaily handles drafting and sending as an agent rather than a dumb pipe. In Copilot mode, the agent can draft replies in your voice from a short prompt, but every message waits for your explicit approval before it sends — so the most common cause of regret, firing off something half-finished, simply can't happen by accident. For routine, low-stakes mail you can let Autopilot do more, and the send-delay, undo, and audit log mean even the automated path is reversible and accountable. It's the opposite of Outlook's all-or-nothing Send button, where your only insurance is a recall that fails the moment the recipient is external: with AI Emaily, nothing leaves without either your sign-off or a delay you can interrupt, and everything is logged so you're never guessing what went out.

AI Emaily is free to start at $0, with a Pro plan at $17.99 per month billed annually for higher volume and the full agent, send-delay, and automation toolkit. If you've ever stared at a recall report hoping it succeeded — or sent something from your phone with no real chance to undo — it's a more forgiving way to run your email, on the exact same Outlook inbox you have now. You can create an account at app.aiemaily.com/signup and connect your mailbox in a few minutes.

Putting it all together

The honest answer to "how to recall an email in Outlook" starts with a question of your own: which Outlook are you using? In classic Outlook on a work Microsoft 365 or Exchange account, you can attempt a real recall via Message → Actions → Recall This Message — but only for internal recipients, only while the message is unread, and with a real chance of failure and an awkward notification. On Exchange Online, the cloud-based version improves your odds and can even reach already-read mail, though it still can't touch anyone outside your organization.

In new Outlook and on the web, there's no recall at all — just Undo Send. So the practical setup is short: open Settings → Mail → Compose and reply, drag the Undo send slider to 10 seconds, and from now on watch for the notification after you click Send and hit "Undo" the moment something feels wrong. Inside that window it works every time, for any recipient. On a phone, you get only a brief built-in undo and no recall, so react fast and write anything important on the desktop.

When recall fails or the window has passed, accept it quickly and pivot to damage control: diagnose what went wrong, respond once and calmly — a brief "please disregard," a low-key correction in the same thread, or a proper apology — and on a work account, call IT fast if the content was sensitive. And if the scramble is a recurring source of stress, question the setup rather than your reflexes. Better habits prevent most mistakes, and an AI-native client like AI Emaily replaces the coin-flip recall and the 10-second countdown with a send-delay you control, a real undo, and an agent that waits for your approval before anything leaves. Recall was never really the answer. A little more time, a little more friction, and a calmer way to send is.