How to Get a Read Receipt in Outlook (And What to Expect)
Read receipts in Outlook sound simple — send an email, get notified when it's opened. In practice, they're more nuanced than most people expect. Whether they work, and how reliably, depends on your version of Outlook, how your email is set up, and what the recipient's mail client does with the request.
Here's a clear breakdown of how read receipts work in Outlook, how to turn them on, and the variables that affect whether you'll actually get confirmation.
What Is a Read Receipt in Outlook?
A read receipt is an automatic notification sent back to you when a recipient opens your email. Outlook can request this by embedding a small flag in the email header. When the recipient's email client detects that flag and the recipient agrees to send confirmation, you receive a follow-up message stating the email was read, along with a timestamp.
This is different from a delivery receipt, which only confirms the message reached the recipient's mail server — not that anyone actually opened it.
| Receipt Type | What It Confirms |
|---|---|
| Delivery Receipt | Email reached the server |
| Read Receipt | Email was opened by the recipient |
Both are useful, but they answer different questions.
How to Request a Read Receipt in Outlook
For a Single Email
The most common approach is enabling a read receipt on a per-message basis:
- Open a new email in Outlook (desktop app).
- Go to the Options tab in the ribbon.
- Check Request a Read Receipt (and optionally Request a Delivery Receipt).
- Send your email as normal.
That's it. The request travels with the email and the recipient's client handles the rest.
For All Emails by Default
If you want read receipts on every outgoing message:
- Go to File → Options → Mail.
- Scroll to the Tracking section.
- Under For all messages sent, check Read receipt confirming the recipient viewed the message.
This applies globally, so every outgoing email will carry the request — which can feel intrusive to some recipients if overused.
In Outlook on the Web (OWA)
The web version of Outlook has a slightly different path:
- Compose a new email.
- Click the three-dot menu (More options) at the top of the compose window.
- Select Show message options.
- Toggle on Request a read receipt.
The option availability here can depend on your organization's Microsoft 365 configuration.
In Outlook Mobile (iOS/Android) 📱
As of recent versions, the Outlook mobile app has limited native support for requesting read receipts directly. Some Microsoft 365 accounts may show the option under message settings before sending; others don't. This is one area where the experience varies based on account type and app version.
Why Read Receipts Don't Always Work
This is where many people get confused. You request a read receipt, the email is opened, and you hear nothing. Several variables explain why:
The recipient's email client is the gatekeeper. When your email arrives, the recipient's mail client — whether Outlook, Gmail, Apple Mail, or something else — decides what to do with the read receipt request. Most modern clients prompt the user with a pop-up: "The sender has requested a read receipt. Do you want to send one?" The recipient can simply click No or dismiss it.
Many clients block or ignore the request automatically. Gmail, for example, does not send read receipts to external senders by default. Apple Mail typically ignores read receipt requests entirely unless configured otherwise. If your recipient uses one of these, you may never get a response no matter what you do in Outlook.
Corporate mail servers can strip or block them. In enterprise environments, IT policies sometimes prevent read receipt data from leaving or entering the organization. This is common in regulated industries.
Privacy-focused email services opt out. Some services and users disable read receipts on principle, treating them as a tracking mechanism — which, technically, they are.
Factors That Affect Whether Your Read Receipt Works 🔍
| Variable | Impact |
|---|---|
| Recipient's email client | High — Gmail and Apple Mail rarely send receipts |
| Recipient's personal settings | High — most clients let users decline |
| Corporate IT policy | High — can block receipts at server level |
| Your account type | Medium — Microsoft 365 vs. standalone Outlook differs |
| Outlook version | Medium — older versions may have different menu paths |
| Email sent internally vs. externally | Medium — internal (same org) receipts tend to be more reliable |
Read receipts work most reliably when both sender and recipient are on the same Microsoft Exchange or Microsoft 365 organization. In that closed environment, your IT admin may have configured automatic receipt responses, and the whole system is consistent.
When sending externally — to Gmail, Yahoo, personal domains, or other providers — reliability drops significantly.
A Note on Alternatives
Because read receipt support is inconsistent, some people turn to other tools for email tracking. Third-party plugins and services (like those used in sales and marketing tools) embed a tiny tracking pixel in the email body. When the email is loaded, the pixel fires and the sender gets a notification. This approach has its own limitations — image blocking, privacy filters, and email client behavior all affect it — but it operates independently of whether the recipient's client supports the official read receipt standard.
These tools exist outside of Outlook's built-in feature set and vary widely in how they work and what they require.
The Part That Depends on Your Situation
Whether read receipts will actually be useful to you comes down to specifics that aren't visible from the outside. Who are you emailing — internal colleagues on the same Exchange server, or a mix of Gmail users and external contacts? Are you on a personal Microsoft account or a managed Microsoft 365 tenant? Does your IT department have policies in place that affect receipt handling?
The mechanics of enabling the feature in Outlook are straightforward. Whether that feature delivers the confirmation you're expecting is a different question — one that your specific email environment, recipient base, and organizational setup will answer differently.