How to Send a Read Receipt in Outlook (And What Actually Happens When You Do)

Read receipts sound straightforward — you send an email, you find out when it's been opened. But Outlook's read receipt system has more moving parts than most people expect, and whether it works the way you're hoping depends heavily on your setup, your recipient's settings, and which version of Outlook you're using.

Here's a clear breakdown of how the feature actually works.

What Is a Read Receipt in Outlook?

A read receipt is an automated notification sent back to you when your recipient opens your email. It's different from a delivery receipt, which only confirms the message reached the recipient's mail server — not that they actually read it.

In Outlook, you can request either or both for individual messages, or configure them globally for all outgoing mail.

How to Request a Read Receipt for a Single Email

This is the most common use case — you want confirmation on one specific message without changing your default settings.

In Outlook for Windows (desktop app):

1. Open a new email compose window
2. Click the Options tab in the ribbon
3. In the Tracking section, check Request a Read Receipt and/or Request a Delivery Receipt
4. Send your message as normal

In Outlook on the Web (OWA):

1. Compose a new message
2. Click the three-dot menu (more options) at the top of the compose window
3. Select Show message options
4. Toggle on Request a read receipt

In Outlook for Mac:

1. Compose a new email
2. Go to Options in the menu bar
3. Select Request Read Receipt

The receipt request travels with the message itself, embedded in the email headers.

How to Turn On Read Receipts for All Outgoing Emails

If you want every email you send to request a read receipt by default:

In Outlook for Windows:

1. Go to File → Options → Mail
2. Scroll to the Tracking section
3. Check Read receipt confirming the recipient viewed the message

This applies globally to all outgoing messages from that account on that device.

The Part Most People Don't Realize 📬

Here's the critical limitation: you cannot force a read receipt. Whether you actually receive one depends entirely on the recipient's mail client and their personal settings.

When someone receives an email with a read receipt request, their email client typically prompts them with a choice: "The sender has requested a read receipt. Do you want to send a receipt?" They can say no — and many people do, especially in professional environments where read receipt requests can feel intrusive.

Some email clients and server configurations are set to automatically decline all read receipt requests without ever asking the user. Others send them automatically without prompting.

What this means in practice:

Read Receipts vs. Delivery Receipts — The Real Difference

These two features are often confused:

• Delivery receipt — confirms the message arrived at the destination mail server. Has nothing to do with whether a human opened it.
• Read receipt — triggered when the message is opened in a mail client. Far more useful for confirming actual human engagement, but far less reliable.

Neither is a guarantee. A delivery receipt can succeed even if the message lands in spam. A read receipt can fail even if the person read every word.

What About Tracking in Microsoft 365 / Exchange Environments?

If both you and your recipient are on the same Microsoft 365 or Exchange organization, read receipts are considerably more reliable. Your organization's Exchange server can be configured to handle receipt responses automatically, and Outlook clients within the same domain tend to process them consistently.

In these environments, some organizations configure receipts to send automatically without prompting users. Others disable read receipts entirely at the server level for privacy reasons — so even within a corporate environment, outcomes aren't uniform.

Why Your Read Receipt Might Not Come Back 🔍

If you've sent a receipt request and heard nothing, the most common reasons include:

• The recipient is using a non-Outlook client (Gmail, Apple Mail, Thunderbird) that doesn't honor the request
• The recipient declined the prompt
• Their organization's mail policy suppresses outgoing receipts
• The email was read in a preview pane without fully "opening" it (behavior varies by client)
• The receipt notification was sent but landed in your spam or junk folder

It's worth checking your spam folder before assuming a receipt wasn't sent.

Variables That Shape Your Experience

How reliably read receipts work for you depends on several factors that vary from user to user:

• Your Outlook version — desktop, web, or mobile apps behave differently
• Your account type — Exchange/Microsoft 365 accounts have more robust tracking than IMAP/POP accounts
• Your recipient's email client and organization policies
• Whether you're in a consumer or enterprise context
• Your own Outlook settings — if you've previously dismissed receipt prompts for your own incoming mail, it affects how others experience receipts from you

Read receipts can be genuinely useful inside tightly controlled organizational environments where everyone runs the same mail stack. Outside that controlled context, their reliability drops significantly — and how much that matters depends entirely on what you're trying to accomplish and who you're emailing.