You’ve noticed this if you run an inbox for a brand: a message request lands, you open it to see whether it’s a real inquiry or another crypto pitch, and then you sit there wondering whether the sender just watched “Seen” appear. They didn’t. Opening a message request doesn’t send a read receipt on Instagram. The receipt only starts once you accept the thread, and accepting is a deliberate action that never happens on its own.
The mechanic behind it
Instagram treats an unaccepted request as a different object from a conversation. Until you accept, the thread is in a holding state: you can read it, the sender can see nothing about your behavior, and no receipt is generated. Accepting flips the thread into a normal conversation, and normal conversations carry receipts. Adam Mosseri, Instagram’s Head, put it plainly in a July 2026 Q&A, saying “we don’t actually send read receipts until you accept the thread overall,” and acceptance isn’t a default state.
The switch is one-directional and it’s retroactive from the moment you flip it, not before it. Nothing you read during the holding state gets reported after the fact.
What happens after you accept
This is the part people get wrong. Accepting doesn’t just send one receipt for the message you were looking at. It turns receipts on for that thread going forward, so every message you open in that conversation from then on will show as read.
So the sequence looks like this:
- Request arrives. You open it. Nothing is sent.
- You accept. The thread becomes a normal conversation.
- Every message you read after that point sends a receipt.
If you’d rather not send receipts at all, Instagram has a setting for it, and managing read receipts for your chats is account-wide rather than per-thread.
Why this matters for brand inboxes
Anyone triaging DMs for a client is making a judgment call dozens of times a day: is this worth a reply, is it spam, is it a complaint that needs escalating. The holding state is what lets you triage without committing, and knowing that means you can read every request before deciding which ones become conversations.
The cost of getting it wrong runs in one direction. Accept a thread you didn’t mean to and you’ve told someone you’re paying attention, which sets an expectation about response time you might not want to set. Read without accepting and you’ve told them nothing.
This is the same design philosophy that governs whether anyone can see you viewing their profile, and the same instinct behind how Instagram handled the recording light on Meta glasses: observation stays quiet until you choose to make it visible.
Instagram’s own guidance on managing message requests covers the mechanics of accepting, deleting and blocking, and it’s worth a skim if your team shares an inbox.
The practical lever
Build the habit around the accept button rather than the open action. Read freely, accept deliberately. For teams, that usually means one person triages and only escalates threads that need a real answer, so acceptance maps to intent instead of curiosity.
It’s the same discipline that makes shared approval workflows work anywhere else: separate the looking from the committing, and the commitment stays meaningful.
FAQ
If I read a message request but don’t accept it, will the person know? No. No read receipt is sent while a request sits unaccepted, no matter how many times you open it.
When does Instagram start sending read receipts? After you accept the thread. From that point on, receipts fire for every message you read in that conversation.
Does accepting a request send a receipt for the original message? Yes. Once the thread is accepted it behaves like any normal conversation, including for messages already sitting in it.
Can you turn off Instagram read receipts entirely? Yes. Instagram has a read receipts setting that applies across your chats rather than per conversation.
