Instagram Hidden Requests: Why Auto DMs Disappear

Message Requests at least shows a badge. Hidden Requests can look like the automated DM never existed: no notification, no Primary thread, API still reports success. If you already ruled out a keyword miss, start here — not by cloning the same first line ten times. Hidden Requests is Instagram’s quieter filter for requests it treats as unwanted, spam-like, or matched by Hidden Words. You cannot open that folder from the sending professional account. You need a test recipient.

Pair this with why automated DMs go to Message Requests. Requests is the common non-follower folder. Hidden Requests is the extra hide. Neither is the hourly cap. Overflow is “later comments have not got a DM yet.” Hidden Requests is “the DM exists where nobody looks.” Queueing: how CommentLink paces DMs. Mixing those two diagnoses is how teams rebuild a working keyword.

What Hidden Requests actually is

Instagram describes Hidden Requests as a place it may put potentially offensive, unwanted, or spam-like message requests, and requests that match the recipient’s Hidden Words list — often without notifying them. You cannot open that folder from the sending professional account. You need a test recipient.

How a successful send can still vanish

1. They comment the keyword. CommentLink sends a private reply. The message id exists.
2. Instagram places the thread: Primary, Requests, or Hidden Requests.
3. If Hidden Requests, they get no badge. They swear you never wrote.
4. Your dashboard still looks fine. That is placement, not a silent API failure.
5. If instead the hourly ceiling is hit, later matches wait in a queue (product ceiling around 200 Instagram DMs per hour in our copy — not a Meta SLA). Those people never got a message id yet.
6. Do not treat queue wait and Hidden Requests as one bug. They need different fixes.

Sample test comments and which folder you open

Test account A does not follow you. Comments LINK on the live Reel. Open Primary (probably empty), then Requests, then Hidden Requests. If the thread is only in Hidden, copy and Hidden Words are the suspects — see spam triggers to avoid.

Test account B follows you. Same comment. Contrast placement. Following helps Primary; it does not guarantee it.

Test account C comments after you fire a burst of identical URL-only DMs. If C is hidden and A was not, volume-plus-identical copy is a clue, not a court verdict. Instagram does not publish a complete classifier.

Diagnosing placement without guessing

1. Confirm the send in CommentLink (message id). If none, this is not Hidden Requests — it is a miss, pause, or queue.
2. Use a second account that is not the connected professional account. Test comment-to-DM.
3. Check Primary, Requests, Hidden Requests in that order.
4. Search the recipient’s Hidden Words for your CTA (LINK, FREE, a brand slur they blocked).
5. Change the first line and pacing; retest. Do not change vendors first.
6. If only viral non-followers hide, teach Requests in the caption and vary the opener. Deliverability checklist: improve automated DM deliverability.

Mistakes that confuse Hidden Requests with the hourly cap

• Rebuilding the keyword because one friend saw nothing. Instead: they check Hidden Requests.
• Assuming queue overflow hid the message. Instead: overflow means no send yet; Hidden means sent and filed away.
• Blasting the same URL-only line harder. Instead: that pattern is spam-shaped.
• Calling it a CommentLink bug when the id exists. Instead: placement is Instagram’s.
• Using a scraper to “force Primary.” Instead: that is a different, unsafe product.
• Ignoring Hidden Words. Instead: your cute CTA may be on their block list.
• Skipping the follower vs non-follower test. Instead: always both.

Copy and pacing habits that look less like spam

• User-initiated only: they commented, replied to a Story, or wrote you. CommentLink does not cold-DM.
• Name what they commented for in the first line, then the URL.
• Vary the opener if volume is high.
• Do not stack four tracking links and a manifesto.
• Pace: respect the queue; do not run unofficial parallel senders.

Copyable second-account test protocol

1. Non-follower test account comments the live keyword.

2. Wait until CommentLink shows a send.

3. On that phone: Primary → Requests → Hidden Requests.

4. Repeat with a follower account.

5. Record folder + whether a notification appeared.

6. If Hidden: change first line, remove raw-URL-only shape, retest once — then stop cloning.

What to put in the caption so people look in the right folder

You cannot notify Hidden Requests. You can teach Message Requests. Caption: “Comment LINK. If you don’t follow us, the DM is often under Requests — not a red badge.” That sentence saves more tickets than a second identical send. It does not fix Hidden Requests, but it stops you from treating every silent thread as a product outage.

If your CTA word is FREE, WIN, or a phrase people put in Hidden Words, expect hides. Rename the keyword to the asset (PRESET, SETLIST, MENU) and put that word on screen. Cute spam-shaped CTAs fight your own deliverability. More on patterns: spam triggers to avoid.

Following you helps Primary. It does not disable Hidden Words. A follower who blocked “promo” may still hide a DM that says “promo code inside.”

What a message id tells you that a friend cannot

If CommentLink stored a message id, the API accepted the send. The remaining question is folder. If there is no id, look at paused rules, keyword mismatch, comments from the connected account, or queue wait — not Hidden Requests. Friends who “got nothing” are not a diagnostic unless they opened Hidden Requests on their phone.

Do not stack unofficial senders to “retry Primary.” Parallel unofficial tools are how you earn restrictions. Pace with the official queue. Vary the first line if volume is high. Put the promised asset early. That is the deliverability work you actually control — improve automated DM deliverability.

When to stop sending identical first messages

If Hidden Requests is where non-followers land, more identical sends will not educate Instagram. Change the copy, teach the folder in the caption, and take high-stakes threads (payments, abuse) human. If the send never happened, fix the queue and the keyword — that is not this folder.

You cannot inspect Hidden Requests from the business side. Without a test account you are guessing. Guessing is how people buy unofficial tools.

What to tell support when they swear you never messaged

Do not reopen the keyword. Ask them, in one sentence, to open Instagram → Messages → Requests → Hidden Requests, then search your handle. If the card is there, the API succeeded and Instagram hid it. If it is not there and your dashboard has a message id, they are looking at a different account. If there is no message id, you have a queue, a keyword miss, or a paused rule — not Hidden Requests.

Write that diagnosis in the caption once: “If you don’t see the DM, check Requests and Hidden Requests.” Support then copies a line instead of rebuilding LINK.

FAQ

Why did my auto DM disappear with no notification?

Check Hidden Requests on a test account. Instagram may hide requests it treats as spam-like or that match Hidden Words, without notifying the recipient.

Is Hidden Requests a CommentLink bug?

Not if the send succeeded. Placement is Instagram’s. Confirm the message id exists, then inspect the recipient folders.

Does following me prevent Hidden Requests?

It helps Primary placement. It does not guarantee visibility. Filters still apply.

Is this the same as the hourly cap?

No. Cap/queue means the DM may not have sent yet. Hidden Requests means it sent and Instagram filed it quietly.

Can CommentLink force Primary?

No. There is no placement toggle. You can improve copy and pacing; you cannot override Instagram’s folders.

What should I change first if we are hidden?

First line and identical URL-only volume. Then Hidden Words. Then vendor shopping.

Can CommentLink open Hidden Requests on their phone?

No. Only the recipient can. You need a second test account to see that folder.

Related reading

• Automated DMs and Message Requests
• Improve automated DM deliverability
• Test with a second account