What Is Undo Send and How Does It Actually Work?

Undo send in email is a delayed submission window. When you click Send, your email client holds the message and does not transmit it until a short timer counts down. If you click undo during that window, the message is cancelled — it never left. Message recall is a different mechanism: it tries to retract a message the recipient has already received.

Those two things are often confused because both result in a message not reaching the recipient. The mechanism and the likelihood of success are completely different. Undo send works because the message was never delivered. Recall attempts to work despite the message already being in the recipient's mailbox — a far harder problem with a far lower success rate.

This guide explains the undo send mechanism in detail, covers how it is implemented in Gmail and Outlook, clarifies when message recall succeeds and when it fails, and shows how the undo concept extends to AI-generated email actions — where an agent taking steps on your behalf needs reversible operations, not just a send delay.

How does undo send actually work?#

Undo send is an intentional delivery delay built into your email client. When you click Send, the client does not immediately hand the message to the SMTP relay for transmission. Instead, it holds the message and starts a visible countdown — typically 5, 10, 20, or 30 seconds. Clicking undo within that window cancels the queue entry and returns the message to draft state. The message was never transmitted.

The reliability of undo send comes from one simple fact: the message has not reached the recipient's mail server. There is nothing to retract. If you cancel within the window, the send is reversed without any involvement from the recipient's server, client, or settings. It works regardless of which provider the recipient uses.

Gmail lets you configure the undo window under Settings, then See all settings, then the General tab, under Undo Send — choose 5, 10, 20, or 30 seconds. A longer window gives more time to catch a mistake at the cost of a short subjective delay before the message feels sent. Outlook does not have a native undo-send control in the same form; the comparable mechanism is a delayed-delivery rule that holds outbound messages in the Outbox for a set number of minutes. Deleting a message from the Outbox before the rule fires achieves the same result — the message is cancelled before it transmits. Verify the current interface steps against Microsoft Learn or Gmail Help, as product interfaces change between updates.

What breaks when there is no undo window?#

Without a send delay, a message is handed to the SMTP relay the instant you click Send and is in transit within milliseconds. At that point your only recourse is message recall — a different and far less reliable mechanism covered in the next section. The cost depends on the mistake: a draft sent before revision, a reply-all that should have been a reply, a message to the wrong person, a note written in the wrong moment. All of them are permanent the instant the recipient's server accepts delivery.

The undo window length is a tradeoff. A longer window gives more time to catch errors; a shorter one makes the send feel immediate. What the window cannot do is protect you after it expires: once the timer runs out and the message transmits, undo send no longer applies. Anything after that point is a recall problem, not an undo problem — and that distinction matters, because the two have completely different success rates.

How does undo send differ from message recall?#

Message recall — sometimes called retract or unsend depending on the client — operates on messages already accepted by the recipient's mail server. It is a fundamentally harder problem than undo send, and its success rate reflects that. Where undo send is a local cancellation before transmission, recall is a request sent to the recipient's server asking it to delete or replace the original message.

The table below shows the key differences across the dimensions that matter most when you are deciding which to rely on.

The failure mode row deserves attention. When a message recall fails in Outlook — which it will for most external recipients — the failure is not silent. The recipient receives a notification that you attempted to retract the message, which in many situations draws more attention to the original than leaving it alone would have done.

Common misconceptions about undo send#

The most persistent misconception is that undo send can retract a message after delivery. It cannot. The feature only operates during the delay window, before transmission. Once the timer expires and the message transmits, undo send no longer applies. Anything after that point requires recall, which is a different mechanism with different constraints.

The second misconception is that message recall works reliably across organisations. It does not. Microsoft 365 recall functions only when both sender and recipient are on the same Exchange or Microsoft 365 tenant, the recipient has not yet opened the message, and no third-party client has downloaded it via IMAP or POP. Recipients using Gmail, Apple Mail, or another provider will not see the recall succeed — they keep the original, and in most versions also receive the recall notification as a separate email.

A third misconception concerns performance. Undo send does introduce a real delay equal to the window you set. In Gmail, the message is submitted to the relay after the timer, not before. Gmail timestamps the message at the moment you clicked Send, so the recipient sees the correct sent time — but actual transmission is delayed by the window length. This is the mechanism that makes cancellation possible: the message has not left yet.

How undo send applies to AI-generated email actions#

Undo send solves one narrow problem: cancelling a message during the submission delay before it transmits. An AI agent that takes actions on your behalf — drafting, sending, filing, following up — needs a broader conception of reversibility. Every action the agent takes should have an undo, not just outbound sends. That means reversing a label change, restoring an archived thread, or pulling back a send that went out in a delegated-autonomy mode — not just stopping a message that has not yet transmitted.

AI Emaily is an AI-native email client built around this broader model of reversibility. We build AI Emaily. In Copilot mode, the agent drafts and queues every send, but nothing transmits until you approve it explicitly — the undo window is replaced by an approval gate, which is a stronger guarantee than a countdown. In Autopilot mode for the specific low-stakes categories you have deliberately delegated, sends happen automatically and an undo window plus a full audit trail cover any misstep. The audit log records every action the agent took, when it took it, and under what approval — so the question of what the AI did to your inbox always has a readable answer. You can start a 7-day free trial at aiemaily.com, or review plan options at aiemaily.com/pricing.