Instagram DM automation rules: what you can send and when

Comment-to-DM answers a comment on the connected account’s post or Reel with a private message. In a resource campaign, that message carries the guide, menu or worksheet the person requested. The account owner authorizes the integration through Instagram’s connection screen.

The important distinction is between permission to send one initial private reply and permission to continue a conversation. Meta’s private-reply documentation describes both. A public comment does not authorize repeated reminders if its author never responds in messages.

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

A caption such as “Comment MENU for our current menu PDF” sets a narrow expectation. Send that menu, identify the link and explain any access requirement. A follower count or list of profile names is not a substitute for the interaction required by the messaging API.

Do not turn one resource request into an indefinite sales sequence. If a later email subscription is part of the offer, explain it before collecting an address. The comment-to-DM setup guide shows a complete starter campaign.

The connection lets ReplyMagnet identify the professional account and its posts, receive comment activity, and perform supported comment and message actions. Review the requested permissions and confirm the account name before connecting.

For the Instagram Login private-reply endpoint, Meta’s current requirements list instagram_business_basic and instagram_business_manage_comments. Other messaging features use their own permissions, including instagram_business_manage_messages; do not confuse a tool’s complete connection request with the minimum requirements of one endpoint.

If access is revoked, the account type changes or the connection stops working, delivery can fail. Follow the Instagram connection guide and inspect the recorded problem before reconnecting or relaunching. No tool can promise that an account will never face restrictions.

Choose the account that actually owns the post. A team member’s personal account and a similarly named brand profile are not interchangeable.

If you need to change account type, review the options in Instagram’s current settings. Check the profile’s public presentation and contact information afterward; do not assume an account-type change has no visible consequences. The connection guide covers the product-side steps.

These limits come from Meta’s private-reply documentation, checked on 4 October 2026. The seven days run from the comment, not the publication date of the post or the moment your team notices it. An older Reel can receive a new comment; evaluate that comment’s timestamp.

An illustrative timeline makes the distinction clearer. A comment arrives Monday at 10:00. Its initial private reply must be sent within seven days, before the following Monday at 10:00. If the person responds to the DM on Wednesday at 15:00, the standard 24-hour response window runs to Thursday at 15:00. Use the same timezone throughout. Sending your own message does not restart that clock.

If they never respond, the seven-day allowance does not give you seven days of reminders. Clicking an external resource link or submitting a website form should not be treated as a DM response. A new eligible interaction must be evaluated under its own rules.

Rule diagram based on Meta’s documentation. The Live limit is the broadcast itself, not a 24-hour allowance.

A queue and a messaging window solve different problems. The queue holds work waiting for capacity; the platform determines whether that message is still permitted. Treat a waiting item as unfinished, not delivered.

Check the original event time, current connection, campaign status and recorded outcome. A retry may help with a temporary error, but repeated relaunches cannot bypass Meta’s rules. A broadcast ending is especially important: a Live comment does not gain a full day merely because a tool shows it as queued.

Use plans and billing help for allowances and the delivery troubleshooting guide to locate the failed step. Avoid promising that every queued request will eventually arrive.

For a public menu, direct access may be the most useful choice. A lesson series may need an email address, while a requested callback may need a phone number. Tell the reader what happens after submission before they commit.

ReplyMagnet’s optional follow check is a technical setting, not proof that a campaign satisfies every platform policy. Leave it off for a straightforward resource request unless there is a justified, clearly explained reason to add it. An API check and permission to impose an engagement condition are different questions.

Review Meta’s current spam standard for your campaign. Avoid misleading promises, purchased audience lists and artificial engagement tactics. An official connection cannot make deceptive campaign content acceptable.

Before launch, describe the event that makes each message eligible. “They commented MENU” supports the first resource reply; “they answered our DM” explains a later response inside the applicable window. “They follow us” or “we have their email” does not establish that same messaging event.

Avoid tools that ask you to hand over your Instagram password or pretend that browser/device scripts provide the same permissions as an authorized API connection. A paid plan, a different tool or a retry button cannot increase Meta’s private-reply allowance.

When unsure which step failed, preserve the activity record and investigate. Do not manufacture another interaction or claim a send succeeded because a job was created.

Use a feed post or Reel for your first controlled test. Check the following:

• The keyword requests a named resource.
• The selected professional account owns the post.
• The DM explains the same resource and destination.
• The recipient can check Inbox and Requests and open the file on a phone.
• Any contact requirement is visible before submission.
• An unrelated comment does not trigger the campaign when broad matching is off.
• Someone will check waiting, failed and expired activity.

A sent message, an opened resource and a captured contact are separate observations. None proves a sale or ongoing permission to contact the person. Once the promise and destination are ready, set up a request-based campaign.