Retext

Email recall follow-up templates for Outlook

Outlook's recall only works for people in your own organisation on Microsoft 365 or Exchange. It never reaches Gmail or other outside addresses, and even inside your organisation it only removes copies that haven't been opened yet. Recipients may also see that you tried. So the reliable fix is a short, calm follow-up: which email was wrong, what to do with it, and where the correct version is. This template says it in four lines.

Template;ol-recall
Hi Name, I tried to recall an email I sent you a few minutes ago ("Subject of the wrong email"). If it's still in your inbox, please delete it: What was wrong. Where the correct version is Sorry for the extra email. [Your name]
Then type ;ol-recall in any app.

Variations

The same message for a different channel or tone. Copy the one that fits.

When the email, or its attachment, wasn't meant for them at all.

Sent to the wrong person
Hi Name, I sent you an email titled "Subject of the wrong email" by mistake; it was meant for someone else. Please delete it without opening the attachment. Thank you, and sorry for the trouble. [Your name]

For a colleague, in Teams or email, when the mistake is minor.

Short (internal)
Ignore my last email ("Subject of the wrong email"), it had What was wrong. Corrected version on its way.

When to use it

  • You sent an email with the wrong attachment, figure or date.
  • The email went to someone outside your organisation, where recall can't reach.
  • You tried a recall and aren't sure it worked.

What to avoid

  • Don't over-apologise. One "sorry" is enough; more draws attention to the mistake.
  • Don't re-send sensitive content in the follow-up while explaining what was wrong.
  • Avoid waiting to see if the recall worked. Send the follow-up straight away.

The fields in this template

Retext fills these in when the snippet expands. In plain text they become [brackets] to replace by hand.

Name{fill:Name}
The recipient's first name, or "all" for a group.
Subject of the wrong email{fill:Subject of the wrong email}
The exact subject, so they can find and delete it.
What was wrong{fill:What was wrong}
Briefly: "the attachment was last year's price list", "the meeting date was wrong".
Where the correct version is{fill:Where the correct version is}
"The corrected file is attached." or "The right date is Thursday 12 June."
More about dynamic fields

Tips

  • •Prevent the next one: new Outlook and Outlook on the web have Undo send under Settings, Mail, Compose and reply, which holds messages for a few seconds. In classic Outlook, a rule can delay every send by a minute or two.
  • •Copy the subject line of the wrong email before typing the trigger, then paste it into the subject fill-in so the recipient can find it.
  • •If the wrong email had personal data, tell your data protection contact as well. A follow-up doesn't undo a data breach.

Works in Outlook, Microsoft Teams and every other app

Retext types the snippet wherever your cursor is. To use a different version in one app, give it the same trigger and limit it to that app with per-app snippets. They go by app, not website, so every tab in your browser counts as one app.

Questions

Does recalling an email in Outlook actually work?

Only sometimes. It works for recipients in your own organisation on Microsoft 365 or Exchange, and only for copies they haven't opened yet. It never works for Gmail or other outside addresses. Outlook sends you a recall report saying whether it succeeded.

Will the recipient know I tried to recall an email?

Often, yes. Depending on their Outlook, they may see a recall notice, and if the recall fails the original stays in their inbox. Assume they'll know and send a short follow-up.

What should I say after sending an email by mistake?

Say which email it was, what to do with it, and where the correct version is. Keep the apology to one line.

Type ;ol-recall, get the whole reply

Retext expands your snippets in every Mac app and fills in names, dates and order numbers for you.

Free to start. No account required on the Mac.