Key takeaways
- A DM from an account the recipient does not follow and has never messaged lands in their Requests folder, so the automation worked even when nobody noticed.
- Instagram sorts messages by the relationship between the two accounts, and no API parameter lets a tool choose the main inbox instead.
- Naming the message requests folder in the public reply and the caption tells people where to look and costs only four words.
- Asking for a reply before sending the link turns a request into a real thread and opens the standard 24-hour messaging window.
In this article
"Comment-to-DM doesn't work for non-followers" is one of the most repeated false conclusions in Instagram automation, and it spreads because the symptom is real. You run a campaign, the public replies post, your tool shows sends going out, and half the audience swears they got nothing.
They did get something. It went to Instagram message requests, the holding folder for messages from accounts you do not follow, where it sits without a notification badge next to a dozen other unread strangers. Nothing is broken, no setting is wrong, and no tool on the market can route around it, because the folder is a recipient-side privacy feature rather than a sender-side option. What you can do is tell people where to look, write a first message that survives the trip, and work out whether a follow gate is worth its cost.
Short answer: a DM from an account the recipient does not follow, and has never messaged, lands in their Requests folder rather than their main inbox. The automation worked. Instagram filters by relationship, not by tool, so the fix is copy and expectations: say "check your requests" in the public reply.
Why automated DMs land in Instagram message requests
Instagram sorts incoming messages by the relationship between the two accounts, and automation does not change that relationship.
When a business DMs somebody who follows it, or who has messaged it before, the message goes to their main inbox. When the recipient has neither followed nor messaged, Instagram treats the message as a request. It goes to a separate list, usually without a push notification, and the recipient has to accept it before a normal thread exists. Some accounts have request filtering turned up further, which pushes messages into a hidden-requests list almost nobody opens. Instagram's help centre documents the folder and the controls behind it.
Comment-to-DM campaigns hit this constantly, because a private reply is the one mechanism that reaches somebody with no prior relationship at all. Meta allows one reply per comment within 7 days so a business can answer people it has never met. The feature working as designed is what puts the message in Requests.
The automation worked. Here is how to tell.
Before you change anything, separate "not delivered" from "not noticed". The fixes have nothing in common.
Three signals say the send happened. The public reply under the comment is the first, though it only proves the DM went out in tools that post the reply after delivery (in HyperDM that is a flow; a standard comment automation posts the reply first). The conversation appearing in your own tool's inbox is the second, with a timestamp attached. Link taps arriving hours later are the third, and they often do arrive late, because people clear their Requests folder in batches on a Sunday.
If all three are present and the recipient insists nothing arrived, ask them to open Instagram, tap the inbox, then tap requests at the top. That resolves it most of the time. If none of the three are present, you have a different problem, and our nine-step guide to comment-to-DM not working walks through it. If the send happened but nobody ever opens it, why “sent” doesn't mean “seen” covers the other reasons, and every rule a first DM runs under is in our Instagram DM automation guide.
Five steps to get those DMs seen
Step 1: Name the folder in your public reply
The public reply under the comment gets read by the person who commented and by everybody else scrolling. Use it. "Sent! Check your DMs, or your message requests" costs four words and lifts open rates more than any message rewrite will. It also sets the next commenter's expectations before they comment. Rotate two or three variations so the thread does not read copy-pasted, which most tools support.
Step 2: Say it in the caption too
Put the instruction where the call to action already is. A caption reading "Comment GUIDE and I'll DM it, check your requests if you don't see it" has pre-answered the only question anybody will have. That one line also cuts the "it doesn't work" comments that otherwise pile up under a viral post and make the campaign look broken to everyone reading.
Step 3: Make the first DM short, specific and tappable
A message viewed in the Requests folder gets a glance, not a read. Lead with the thing they asked for, keep it to two or three sentences, and put the link on a button rather than in the text. The button matters mechanically too: on Instagram for Android, a link typed into message text often is not tappable, while a button always is. HyperDM's comment-to-DM feature sends link fields as buttons under the message for that reason.
Step 4: Ask for a reply, and hold the link until it comes
Their reply is what turns a request into a real thread and opens the standard 24-hour messaging window. Sending the promise first and the link after they answer sounds like friction, and on cold traffic it usually performs better: the person has engaged, the thread sits in their main inbox, and the link lands somewhere they will see it. Most builders expose this as a delivery setting, documented for HyperDM in the comment-to-DM guide.
Step 5: Give the second message somewhere to go
Once they reply, you have 24 hours of normal messaging. That is the moment for the follow-up, the upsell or the email ask, not day three. Plan the sequence around their replies rather than around the clock, because a scheduled step sent into a closed window just fails. Our DM templates that convert collection has openers built this way.
The follow-gate trade-off
A follow gate asks people to follow you before the link is released, which also moves the conversation out of Requests. It is a real option with a real cost.
The upside is mechanical. A follower gets your messages in their main inbox from then on, and you gain a follower you would otherwise not have. The downside is drop-off, and on cold traffic it is substantial, because most people commenting on a gated campaign do not follow you yet. The gate also has to run after the person has replied to your first message, since Instagram does not tell apps whether a fresh commenter follows you. In practice the first DM asks them to follow and tap a confirmation, and everybody who ignores it is lost. Use a gate when the offer is strong enough to carry the ask, and skip it when you are testing a new lead magnet. HyperDM's follow-gate walkthrough covers the flow and the timeout branch for people who never follow.
What you cannot fix
Three things sit outside anybody's control, and knowing them stops you buying a tool that promises otherwise.
- 1You cannot send to the main inbox on demand. No API parameter chooses the folder. The relationship chooses it.
- 2You cannot bypass a recipient's message controls. Accounts set to restrict messages from people they do not follow will filter yours, and that is their setting to make.
- 3You cannot retry into the same comment. The one private reply per comment has been spent whether or not they saw it. A new comment creates a new allowance.
Getting out of Instagram message requests and into the inbox
Instagram message requests are the price of reaching people who have never interacted with you, and the private-reply mechanism that makes that reach possible is the reason the folder is involved at all. The fixes are cheap: four words in the public reply, the same four in the caption, a first DM short enough to read in the preview, a button instead of a bare link, and a request for a reply that opens a real thread. Follow gates move people to the main inbox at a measurable cost in volume, so test before committing. To see the delivery options and the public-reply variations that make this work, start with HyperDM's comment-to-DM documentation.
Frequently asked questions
HyperDMRun the automations. Add AI when you’re ready.
Comment-to-DM, keyword replies and follow gates — set them up, test them, then add optional AI answers from your real catalog. Free on one DM channel, 50 conversations a month, no card.



