How to Add Read Receipts in Outlook (And What to Know Before You Do)

Read receipts in Outlook sound simple — send a message, get confirmation when it's opened. In practice, there's more going on under the surface, and understanding the full picture helps you use this feature in a way that actually works for your setup.

What a Read Receipt Actually Does

A read receipt is a notification request sent alongside your email. When the recipient opens your message, their email client generates a return notification — a separate email — that lands in your inbox confirming the message was read, along with a timestamp.

The key word there is request. Unlike delivery receipts (which confirm the message reached the mail server), read receipts depend on the recipient's client cooperating. More on that shortly.

How to Request a Read Receipt in Outlook 📬

The steps differ slightly depending on which version of Outlook you're using.

Outlook for Windows (Desktop App)

1. Open a new email message
2. Go to the Options tab in the message ribbon
3. Check the box labeled Request a Read Receipt
4. You can also check Request a Delivery Receipt if you want server-level confirmation separately
5. Send your message as normal

Outlook on the Web (Outlook.com / Microsoft 365 in Browser)

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

Outlook for Mac

1. Open a new message
2. Go to Options in the message toolbar
3. Click Request Receipts
4. Choose Read Receipt from the dropdown

Setting Read Receipts for All Outgoing Messages (Windows)

If you want receipts on every email without toggling manually:

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

This applies globally to all outgoing messages, which is worth thinking through before enabling — not everyone finds blanket receipt requests appropriate in casual or collaborative environments.

The Variables That Affect Whether This Works

Here's where it gets nuanced. Several factors determine whether a read receipt is actually useful for you.

Recipient's Email Client

This is the biggest variable. Read receipts use a standard called MDN (Message Disposition Notification). Most major clients support it — but support doesn't mean automatic compliance. The recipient's client may:

• Prompt the user asking whether to send a receipt (Gmail, many corporate clients)
• Silently ignore the request (some mobile apps, certain privacy-focused clients)
• Automatically decline based on organization policy

You have no control over this. A missing receipt doesn't necessarily mean the email wasn't opened.

Exchange vs. Non-Exchange Environments

Microsoft Exchange and Microsoft 365 environments tend to handle receipts more reliably when both sender and recipient are on the same server or organization. Internal emails within a company often yield more consistent results.

Sending to external recipients — Gmail, Yahoo, personal accounts, other corporate domains — introduces more unpredictability. Those servers set their own rules.

Mobile vs. Desktop Reading

Even if a recipient has Outlook on their desktop and mobile, receipts can behave differently. Some mobile apps either don't trigger the receipt request or prompt the user separately. If someone reads your email on their phone first, receipt behavior may differ from what you'd see if they opened it on desktop.

Recipient Privacy Settings and Policies

Many organizations configure Exchange server policies that automatically suppress or deny read receipt requests for all inbound messages. If your recipient works at a large company, IT policy may prevent receipts entirely — regardless of what their individual Outlook settings say.

Individual users can also configure Outlook to never send read receipts, which overrides your request completely.

Delivery Receipts vs. Read Receipts: A Quick Comparison

How Recipients Experience Read Receipt Requests 🔍

Worth understanding the other side of this. When your email arrives with a read receipt request, many clients — including Outlook itself — will show a dialog box asking the recipient: "The sender has requested a read receipt. Do you want to notify the sender?"

They can click Yes or No. Or their settings may answer that question automatically without them ever seeing the prompt.

This means read receipts are visible to recipients. They know you've requested one, and they can choose not to comply. In professional or formal contexts this is generally accepted. In less formal settings, some recipients find the practice intrusive — something worth factoring into how and when you use it.

What Tracking Covers and What It Doesn't

Outlook's built-in tracking tools go a bit further in group environments. For emails sent to multiple recipients, Outlook tracks receipt responses individually — useful for team communications or project follow-ups where you need to know who has seen a message.

You can check tracking status by:

1. Opening your Sent Items
2. Opening the sent message
3. Clicking the Tracking button in the ribbon (available in desktop Outlook with Exchange accounts)

This only shows responses for recipients who actively returned a receipt — not a complete open log.

The Setup-Dependent Reality

Whether read receipts are worth using — and how reliably they'll work — depends heavily on where you're sending, who you're sending to, what account type you're running, and what policies exist on both ends. An internal Microsoft 365 environment behaves very differently from a mixed setup where some recipients are on Gmail and others on legacy corporate mail servers. Your specific combination of those factors determines how much signal read receipts actually give you.