The short answer.
Yes, LinkedIn has read receipts. They are on by default, they are bundled with typing indicators in a single toggle, and when someone reads your message their profile photo appears next to it. There is no checkmark. The setting is under Data privacy, not Communications, and it was recently renamed to Delivery and typing indicators, which is why most guides you will find send you to the wrong place.
See how Occura runs outreach on dedicated accountsThe three states, and the one that does not exist.
LinkedIn documents exactly three states for a message you have sent.
| State | What it means |
|---|---|
| Sending | In transit. |
| Sent | Delivered to LinkedIn. Says nothing about whether it was seen. |
| Read | The recipient opened it. Their profile photo appears next to the message. |
If you have read elsewhere that LinkedIn has a WhatsApp-style system where one grey tick means sent and two ticks mean delivered, that is wrong, and it is repeated on several of the most visible pages about this subject. LinkedIn has no delivered tier. A message sits at Sent until it is read, and Sent tells you nothing at all.
If you believe there is a delivered state, you will read a stalled Sent as “it arrived, they are ignoring me”. There is no such information in it.
Where the setting actually is.
LinkedIn renamed this control, and the rename has not propagated to a single one of the guides currently ranking for it. All of them still call it “read receipts and typing indicators”. LinkedIn's own toggle now reads Delivery and typing indicators.
- On desktop: Me → Settings & Privacy → Data privacy → Messaging experience → Delivery and typing indicators.
- On mobile: your profile photo → Settings → Data privacy → Messaging experience → same toggle.
Several widely-read guides, including the one currently ranking near the top for this term, tell you to go to the Communications tab. It is not there. If you have gone looking and given up, that is why.
One toggle governs both read receipts and typing indicators. You cannot keep one and disable the other.
You cannot be invisible and observant.
This is the part that turns a privacy setting into a business decision. LinkedIn's documentation is unambiguous:
If they are turned off, no one in the conversation, including you, can see whether messages have been read or if someone is typing a response.
And from the other direction:
If a recipient has turned off read receipts and typing indicators, you won't see when they've read your message... the message status indicator will show as Sent.
So the toggle is not a shield you hold in front of yourself. It is a light switch for the whole room. Turn it off and you stop leaking your own read behaviour, and in the same movement you lose the read signal on every conversation you are running.
For an individual professional that trade is often fine. For a team running outbound it is expensive, and nobody writing about this setting has bothered to say what it costs. We will get to the price further down.
Where read receipts simply do not work.
Three blind spots, and the second one is the one that catches outbound teams.
InMail: never. LinkedIn states plainly that read receipts and typing indicators do not appear to InMail senders. If your motion is Sales Navigator InMail, you are operating with zero read data, permanently. That is a real argument for sequencing connection requests ahead of InMail rather than the reverse.
Message requests: only after acceptance. For messages sent to people who are not yet connections, receipts appear only once the recipient accepts the request. This is the rule that matters most in cold outreach, and across the pages currently ranking for this keyword it appears, when it appears at all, as a single clause.
Think about what it means operationally. For every cold prospect who has not yet accepted, the absence of a receipt is uninterpretable. It may mean they have not read the message. It may mean the request is still sitting unaccepted so no receipt can physically fire. Those are different problems with different responses, and the interface gives you no way to tell them apart.
In our own campaigns, roughly half of connection requests are accepted, on our core segment of B2B SaaS founders at companies with more than 20 employees. Which means that at any given moment, about half of an active campaign sits inside that receipt-blind zone. Any follow-up logic built on “no receipt means unread” is wrong for half the book.
Groups and Sales Navigator inbox: undocumented. LinkedIn's help pages do not state whether the toggle behaves identically there. We are not going to assert that it does.
The badge that lies: unseen is not unread.
A quiet one, and it is the source of a lot of “they definitely read it, the receipt never showed” confusion.
LinkedIn tracks unseen messages, meaning the little number on your Messaging icon, separately from unread messages. Their documentation notes that clicking the Messaging icon clears the unseen count even when messages inside are still unread.
So a prospect can glance at their inbox, clear the badge, never open your thread, and nothing fires. From your side it looks identical to complete silence. From theirs, they have technically “seen” that something arrived. This is worth knowing before you build a mental model where a missing receipt means a missing message.
Read but no reply, versus unread and no reply.
Here is the section the rest of the internet skips.
Every guide on this subject treats a non-reply as one thing and prescribes one remedy: send a follow-up. But a message that shows Read and a message still sitting at Sent are two different failure modes, and they call for opposite responses.
| Sent, never read | Read, no reply | |
|---|---|---|
| What failed | Distribution | The message itself |
| Likely cause | Request not accepted yet, bad timing, buried inbox, dormant account | Weak hook, wrong offer, no reason to answer, bad timing on their side |
| Wrong move | Rewriting the message | Sending the same message again |
| Right move | Change the delivery: different channel, different hour, or wait for acceptance | Change the substance: new angle, sharper relevance, a reason that did not exist before |
| Follow-up value | High. They probably never saw it. | Low if identical. A person who read it and passed will pass again. |
The single most common mistake we see is teams sending a “just bumping this up” follow-up into a thread that shows Read. That person made a decision. Repeating yourself asks them to make the same decision twice, and they will.
Conversely, teams often rewrite a perfectly good message that was never opened. The message was not the problem. It never got a hearing. When the substance genuinely does need to change, that is a question of new angle, sharper relevance, not of volume.
What read-but-no-reply usually means
We cannot give you a clean number on this one, and pages that do are guessing, so here is the reasoning instead.
Across published datasets, reply rates from accepted connections cluster far below acceptance rates: Reachium reports 27.55% of accepted connections producing an inbound message, Belkins 7.2% of contacts replying, Expandi 10.4% on messages. Reachium's year-on-year comparison is the one worth noting, because reply-of-accepted fell from 32.2% to 22.0% between 2025 and 2026 while acceptance held steady.
The read receipt is the only free signal that tells you which half of that drop you are in. A message that shows Read and gets no answer failed on substance. A message still sitting at Sent failed on distribution. Sending the same follow-up into both is why follow-up sequences perform so poorly.
Should an outbound team leave read receipts on?
Now the decision, with the price attached.
What you give up by turning them off: the read signal on your entire pipeline. No ability to separate the two failure modes in the table above. Every non-reply collapses into one undifferentiated bucket, and your follow-ups become guesses. For a team whose whole job is knowing which conversations to push and which to drop, this is a significant loss.
What you gain: your own reading behaviour stops being visible. Prospects cannot see that you opened their reply at 11pm and did not answer. Competitors cannot infer your activity from typing indicators.
Leave them on. The read signal is one of the very few pieces of behavioural feedback LinkedIn gives you for free, and the privacy you buy by switching it off is worth far less than the diagnostic you lose. If a specific account has a reason to go dark, that is a per-account decision, and it should be made deliberately rather than as a default.
That last point is worth stating because the setting is per account. A team running several branded accounts makes this call once per account, and if nobody has written down the house rule, different accounts will drift into different states and your read data will be inconsistent across the book without anyone noticing.
Reading a message without triggering a receipt.
The other half of the search intent, answered honestly and briefly.
The reliable method: turn the setting off. It works, it is documented, and it costs you the reciprocity described above. There is no way to keep your own visibility while hiding.
The method we will not vouch for: several guides suggest opening the message in airplane mode and closing the app before reconnecting. LinkedIn plausibly syncs read state when the device reconnects, and this behaviour is not documented anywhere. We have not tested it at a scale that would let us say either way, so we are not going to tell you it works.
What does work reliably: the message preview in your inbox list shows the opening of a message without opening the thread. No receipt fires for a preview.
Frequently asked questions.
Does LinkedIn tell you if someone read your message?
Yes, if both parties have delivery and typing indicators enabled. The recipient's profile photo appears next to the message once they open it.
What does the grey checkmark mean on LinkedIn?
LinkedIn does not use a checkmark system for read status the way WhatsApp does. The documented states are Sending, Sent and Read, and the read indicator is the recipient's profile photo.
Can I turn off read receipts but still see when others read my messages?
No. The setting is reciprocal. Turning it off blinds you to everyone else's read status as well.
Do read receipts work on InMail?
No. LinkedIn states that read receipts and typing indicators do not appear to InMail senders.
Why can I not see a read receipt on someone who is not a connection?
For message requests, receipts appear only after the recipient accepts the request. Until then, no receipt can appear regardless of whether they read it.
Does the other person know if I turn read receipts off?
There is no notification. They will see your messages stay at Sent, which is the same thing they would see if you simply had not read them.
Does clearing my Messaging badge mark messages as read?
No. LinkedIn counts unseen and unread separately, and clicking the Messaging icon clears the unseen count without marking the messages inside as read.
Does this setting apply in group conversations and the Sales Navigator inbox?
LinkedIn's help documentation does not state this either way, so we are not going to claim it does.
The short version.
Read receipts are not really a privacy control. They are the only free behavioural signal LinkedIn hands an outbound team, and the toggle that hides you also blinds you. Leave them on unless a specific account has a specific reason not to.
And when a message goes unanswered, look at the state before you write the follow-up. Sent and Read are two different problems, and the same follow-up cannot fix both.
For the wider picture this sits inside, see our complete guide to LinkedIn outreach.