Smart. Focused. Email.
Fast, cross-platform email designed to filter out the noise - so you can focus on what's important.
Definition
💡 Read receipt: A notification that tells you when someone opened your email. Think of it like the "seen" indicator in messaging apps, but for email.
Most email clients let you request these, but here's the catch: the recipient has to agree to send one back. It's not automatic.
Why do people request read receipts?
You send an important email. Did they get it? Did they read it? Are they ignoring you, or is it sitting in spam?
Read receipts answer that question. For time-sensitive stuff (contract deadlines, event confirmations, urgent requests), knowing someone actually opened your message matters. It eliminates the "I never got it" excuse.
But they're not foolproof. Someone can open your email and decline to send the receipt. Or their email client might not support receipts at all. Mobile apps often don't send them. Litmus research found that only about 30% of requested read receipts actually get returned. That's not great odds.
The bigger issue? They can feel pushy. Requesting a read receipt on every email signals "I'm tracking you," which most people find annoying. Use them sparingly.
How read receipts work
When you request a read receipt, your email includes a special header that asks the recipient's email client to send a confirmation back.
If the recipient agrees, their email client automatically sends you a reply saying "Yes, [Name] opened your email at [Time]." That confirmation lands in your inbox like a regular email.
If they decline (or their client doesn't support it), you get nothing. Radio silence. You can't tell if they read it and declined, or if the request never worked in the first place.
Some email clients offer a third option: ignore the request entirely without asking the user. From your perspective, it looks exactly the same as a declined receipt.
There are also tracking pixels (a different technology entirely). Those work without permission by embedding a tiny invisible image in your email. When someone opens it, the image loads from a server, which logs the open. More reliable than read receipts, but also more invasive. Most email tracking tools use pixels instead of formal receipts.
Requesting a read receipt
The process varies by email client, and honestly, it's not always obvious where to find it.
In Gmail:
You can find information on Google’s help page on requesting read receipts:
- Only available for Google Workspace (work/school) accounts, NOT personal Gmail accounts
- Recipient must approve sending the receipt (it's not automatic)
- Located under "More options" (three dots icon) in compose window
Steps:
- Compose your email
- Click the three dots icon (More options) at the bottom right
- Select "Request read receipt"
- Send your email normally
Important caveat: The recipient will see a prompt asking if they want to send a receipt. They can choose "Send receipts" or "Not now" - so you're not guaranteed to get one back.
In Outlook:
You can find up to date information on their help page for read receipts
Steps to request a read receipt:
- Click Message at the top of the compose pane
- Select More options from the ribbon
- Check Request a read receipt (or Request a delivery receipt, or both)
- Send your email
Note: This is specifically for Outlook on the web. The desktop version might have slightly different menu locations.
In Spark:
Spark doesn't support traditional read receipt requests through standard email protocols. Instead, Spark Pro offers a Read Statuses feature that uses tracking pixels to show when emails have been opened.
How it works:
- Open Spark Settings
- Go to Composer
- Enable the Read Statuses toggle
- Under Notifications, choose which recipients to track
Once enabled, you'll see an eye icon next to sent emails:
- Eye with strikethrough: not opened yet
- Grey eye: opened by some recipients
- Blue eye: opened by all recipients
Click the eye icon to see which recipients opened the email and when.
Important: This feature requires Spark Pro and only works when recipients load images in their email client. If they block remote images or use privacy-focused settings, you won't get open notifications. Read Statuses use tracking pixels, not formal read receipts, so recipients aren't prompted to approve anything.
Using read receipts wisely
Should I request read receipts on every email?
No. Reserve them for genuinely important messages where you need confirmation. Contracts, legal notices, urgent business requests. Not routine check-ins. Requesting receipts on everything makes you look paranoid and annoys recipients.
What if someone declines my read receipt?
Respect it and move on. If someone consistently declines your read receipts, stop requesting them. They're making their preference clear. Have a backup plan for critical communication: follow up with a phone call or text if you truly need confirmation.
Are there better alternatives to read receipts?
Yes. For marketing emails or campaigns, use proper email tracking tools with analytics dashboards. For personal accountability, just ask people to reply confirming they got it. A simple "Please confirm receipt" in your email works better than a formal read receipt and feels less intrusive.
How do I explain why I'm requesting a receipt?
Add a line in your email: "I've requested a read receipt to confirm you received this before the Friday deadline." Transparency reduces the creep factor. People are more understanding when they know why you're tracking them.
Related content
Related terms