Instagram DM automation rules: what you can send and when

ReplyMagnet is built on exactly these rules, so this page also describes how our campaigns behave. Start free: comment automation is on the free plan, and the 30-day Pro trial needs no card.

Editorial illustration of two separate messaging limits, not a product screen or a platform endorsement.

Most contradictory advice about Instagram DM limits comes from mixing the two columns below. Plan around the documented column. Treat the reported column as symptoms to investigate, not as rules.

Sources: Meta private replies, Meta Messaging API and Meta's spam standard. If a number is not on a Meta page, we do not build campaign logic on it.

Searches for an Instagram DM limit per day usually find a number, such as 50 or 100 a day, quoted in a blog post or a forum thread. None of those figures appears on the Meta pages we checked, and they disagree with each other, so we treat them as user reports.

What does hold, per Meta's Messaging API page and private replies page:

• Per comment: one private reply, sent within 7 days of the comment.
• Per conversation: further messages only within the 24-hour window after the person writes back.
• Per message: text of 1,000 bytes or less, and up to 10 attachments in one request.

So the practical limit on automated DMs is how many people ask, not a daily quota. Sending only to people who commented or messaged first keeps an account inside both Meta's rules and its spam standard. Manual DMs from the Instagram app are a separate case: Instagram does not publish a number for those either.

Three pieces do the work in any official comment-to-DM tool, ours included:

1. Webhooks tell the app a comment, message or button tap arrived (the comments, messages and messaging_postbacks fields).
2. The private reply answers one comment privately. Meta's docs say it can go to a commenter on a post, Reel or story.
3. The Send API continues a conversation the person has opened, inside the messaging window.

There is no endpoint for messaging someone who has not interacted with the account. A follower list or a list of usernames does not open a conversation. The Instagram Graph API entry covers the wider platform, and our Instagram automation guide covers what else it can and cannot automate.

Meta lists only the first two as requirements for the private reply endpoint. The third lets a tool read and answer the replies, button taps and story replies that come after it. A tool asking for all three is not overreaching; one asking for publishing or ads permissions to run comment-to-DM should explain why.

Each permission must pass Meta App Review before a tool can use it for accounts it does not own. ReplyMagnet's app was approved for all three in August 2026. Approval covers the integration, not your campaign wording. You also need a Business or Creator account; a personal profile cannot connect.

An older Reel can receive a new comment; that comment gets its own 7 days. A worked example: a comment arrives Monday at 10:00. The private reply must go out before the following Monday at 10:00. If the person answers the DM on Wednesday at 15:00, follow-ups are allowed until Thursday at 15:00. Use one timezone throughout.

If they never answer, the 7 days do not give you 7 days of reminders. Opening a link or filling in a web form is not a DM response.

Rule diagram based on Meta's private reply limitations, checked 23 October 2026.

The 24-hour messaging window covers every conversation the person starts:

• Story replies arrive as messages, so the reply goes in the same thread within 24 hours. There is no public reply.
• DM keyword triggers (someone messages you GUIDE) answer inside the window that message opened.
• Click-to-Direct ads are the documented exception: the window may last up to 7 days from the first message.
• The Human Agent tag gives 7 days for replies written by a person. Meta frames it for human support, so ReplyMagnet does not request it for automation.

ReplyMagnet records the original event time and checks it again just before every send. A message processed after its window closed is marked expired, not sent late. Source: Meta Messaging API.

Meta does not define keyword triggers; each tool sets its own matching. Ours, so you can predict what fires:

A keyword campaign always beats an any-comment campaign on the same post. Comments from the connected account itself never trigger anything, so test from a second account. For words that work, see trigger keyword ideas.

A comment alone does not grant that consent, so no official tool can check a commenter's follow status at the moment they comment. Source: Meta User Profile API.

How ReplyMagnet's optional follow gate uses it:

1. The first DM asks the person to follow and tap a button.
2. The tap opens the conversation, so the follow status can be read from Meta.
3. The resource is sent only when Meta returns true.

The check is on every plan and off by default. Meta's spam standard warns against requiring follows to access content, so we recommend leaving it off for a plain resource request. The follow gate rules guide covers when it is reasonable.

The overflow queue is on every plan and holds over-limit requests instead of dropping them. When capacity returns, each one is re-checked against its original window. A flat plan makes this rare: $29 a month covers 100,000 engagements, where per-contact pricing bills every new person. See what ManyChat really costs per month for the per-contact version of the same numbers.

For a missing DM, the delivery troubleshooting guide separates a matching problem from a send failure.

• The keyword requests a named resource, and the DM delivers that resource.
• The connected professional account owns the selected post.
• The test comment comes from a different account.
• The tester checks Requests if they do not follow you (where message requests hide).
• Any email or phone ask is visible before submission.
• Follow-ups are planned only after a reply, inside 24 hours.
• Someone checks waiting, failed and expired activity weekly.

Then set up your first campaign, or follow the comment-to-DM setup guide step by step.