Quick answer: To automate Instagram comments to DM, connect an Instagram professional account to a tool or Meta app holding a comments permission, subscribe to the comments webhook, and send a private reply using the comment ID. Meta allows one private reply per comment, within 7 days (Live: only during the broadcast). The 24-hour chat window opens only when the commenter replies.
If you are asking “how do I automate my Instagram comments to DM” or “how do I send a DM when someone comments on my reel”, the rules come from one place: Meta’s Private Replies feature on the Instagram Platform, the API Meta documents for messaging a commenter. Its limits shape what third-party tools such as ManyChat, Inrō and LinkDM can do, and what any app you build yourself can do. Meta Business Suite also has its own Comment to message automation. This guide covers the limits first, then the no-code build, then the API build with the exact permissions (instagram_business_manage_comments on Business Login for Instagram, instagram_manage_comments and pages_messaging on Facebook Login for Business), the comments and live_comments webhooks, Meta’s rate limits and the real error codes. Every Meta fact below was read on Meta for Developers on 22 October 2026. developers.facebook.com returns HTTP 400 to direct requests from our server, so we read the current pages through the r.jina.ai text reader.
This page is about the comment trigger. For the broader job of answering DMs, read our guide to automating Instagram DM replies, which covers the 24-hour window, the human_agent tag and the disclosure rules in full.
Where Zian fits after the commenter replies
Zian fits at the moment a commenter answers your private reply: from there, Zian’s AI agents run the Instagram DM conversation, qualify the lead and book the appointment. Zian is an AI sales and reception agents platform, inbound and outbound, in partnership-application beta, and zian.ai lists 50,769+ qualified sales appointments set.
Use your comment tool for the trigger and the single private reply, because that is what Meta’s Private Replies feature covers. Once the person replies, a 24-hour window opens and the job becomes a sales conversation. Zian handles that conversation in Instagram DMs and Facebook Messenger, books from inbound and outbound conversations, and follows up by voice call, SMS, email or WhatsApp when the Instagram window has closed. It connects to HubSpot, Salesforce, HighLevel and Zapier, works in 30+ languages, and its AI receptionist answers inbound phone calls 24/7. zian.ai does not say it fires the comment-triggered private reply itself, so ask about that during your partnership application. If you are adding Messenger at the same time, our Facebook Messenger AI agent setup guide covers the Page permissions. If you would rather not run any of it, LeadsNow.ai is the done-for-you option built on Zian, paid per result.
What Meta actually allows: the comment-to-DM limits table
The comment-to-DM limits table puts each rule Meta publishes for comment-triggered messages next to Meta’s own wording, the page it comes from, and what goes wrong in a live campaign if your automation ignores it. The last column is our reading of the consequence, not Meta’s text.
| Rule | Meta’s exact wording | Meta source | What breaks if you ignore it |
|---|---|---|---|
| One message per comment | “Only one message can be sent to the commenter” | Send a Private Reply to a Commenter (updated 30 June 2026) | A three-message “welcome sequence” fired from a comment cannot run; only the first message is a private reply |
| 7-day limit | “The message must be sent within 7 days of the comment was made on the post or reel” | Same page | A backlog or a paused automation cannot catch up on comments older than 7 days |
| Instagram Live | “private replies can only be sent during the live broadcast. Once the broadcast ends, private replies cannot be sent” | Same page | A queue that drains after the Live ends sends nothing |
| Follow-ups need a reply | “Follow-up messages can only be sent if the recipient responds, and must be sent within 24 hours of the response” | Same page | A link-only first message with no reason to answer ends the conversation there |
| Where it lands | The reply appears in the person’s Inbox “if the person follows the Instagram professional account, or to the Request folder, if they do not” | Same page | Non-followers may not see your DM for days, which is why tools offer follow gates |
| Post link attached | “The private reply message includes a link to the commented post” | Same page | Nothing breaks, but the commenter sees which post triggered it, so the message must match the post |
| Public accounts only | “The account that owns the media must be public. Private accounts do not receive comment or mention notifications.” | Set up Instagram Webhooks (updated 20 October 2026) | No webhook arrives at all, so the automation looks broken with no error |
| Access level for the webhook | “Advanced Access is required for comments and live_comments notifications.” Also: “Your app must be published or Live to receive notifications for app users.” |
Same page | A self-built app in development receives no comment events from real commenters |
| Rate limit | “750 calls per hour per Instagram professional account for private replies to comments on Instagram posts and reels”; 100 calls per second for Live comments | Graph API Rate Limits | A viral reel builds a queue; see the worked calculation below |
| Consent and opt-out | “Don’t contact people in Messenger or Instagram Messaging unless you … have obtained legally sufficient consent, permission, and/or opt-in”; “Immediately respect all requests … to block, discontinue, or otherwise opt out” | Meta Developer Policies, section 5 | Messaging that ignores a “stop” is a policy breach, and negative feedback can get the experience “feature limited, paused, rate-limited or removed from Platform” |
| Deliver what you promised | Spam “includes … failing to deliver promised experiences” | Meta Developer Policies, section 5 | A “comment LINK and I’ll DM you” post whose automation fails is the pattern this line describes |
| Bot disclosure | “When required by applicable law, automated chat experiences must disclose that a person is interacting with an automated service” | Messenger Platform and IG Messaging API policy (updated 28 September 2026) | Meta names California and German users; it also recommends disclosure “even where not legally required” |
Two things in that table surprise most people. First, a comment does not open the 24-hour messaging window. Meta’s Instagram Messaging private replies guide says: “Only when the Instagram user responds to the private message can you continue the conversation within the 24-hour messaging window.” Meta’s policy page gives examples of actions that do open the window (sending a message, tapping Get Started, messaging from a Click-to-Direct ad, an ig.me link with a ref parameter, reacting to a message), and a comment is not among them. Second, Meta’s own pages disagree on the access level for your own account. The Comment Moderation guide (updated 20 October 2026) says Standard Access is enough if your app serves accounts “you own or manage and have added to your app in the App Dashboard”, while the webhooks setup guide says comment notifications need Advanced Access. Meta’s Instagram Messaging private replies guide adds that “Standard Access apps can only access data for people who have a role on the app”, which would leave out commenters who have no role on your app. If you build your own app, plan for App Review and Business Verification, and test with an account that has no role on your app.
How to automate Instagram comments to DM: the setup sequence
This sequence works whichever tool you pick. Your first action on day one is step 1, because the account type and privacy setting block everything after it.
- Switch to a professional account and keep it public. Meta’s Instagram Platform overview says app users “must have an Instagram professional account”, which “can represent a business or creator”. The account that owns the post must be public or no comment webhook is sent.
- Turn on access to messages. Meta’s Instagram Messaging get-started guide gives the path: Instagram Settings, Messages and story replies, Message controls, Connected Tools, Allow Access to Messages. Our Instagram DM setup guide walks through this toggle and the login routes.
- Pick a route. A no-code tool (Route A below) or your own Meta app (Route B). If you need a Facebook Page linked to Instagram, you are on the Facebook Login route; if not, Business Login for Instagram.
- Choose the posts. One post, the next post, or every post. Start with one post so you can measure it.
- Choose the trigger words. One or two plain words (“price”, “link”, “book”) beat a phrase. Tell people the word in the caption.
- Write the private reply as a question. The one message you are allowed must earn an answer, because only an answer lets you continue. “Want the price list for your suburb? Reply YES” works; a bare link often ends the thread.
- Plan the next 24 hours. When the person replies, your automation or AI agent has 24 hours from that reply. Ask for the detail you need (email, phone, preferred time) inside that window.
- Test from a second account. Comment the trigger word from an account that does not follow you, then from one that does.
Your finish state: a comment from a non-follower test account produces one private reply in that account’s Requests folder, a reply to it produces the next message, and typing “stop” ends the flow.
Route A: comment-to-DM with a no-code tool
Every tool below says on its own pages that it sends an Instagram DM from a comment. The field names are copied from each vendor’s help or product page, read on 22 October 2026.
ManyChat: the Instagram Comments Reply trigger
ManyChat’s help article “Instagram Post and Reel Comments trigger” gives the full sequence. Open the Automation tab, click + New Automation, then + Start From Scratch and Start with a blank option. In the Flow Builder, click +New Trigger and choose User comments on your Post or Reel from the Instagram tab. Pick Specific post or reel, All post or reels or Next post or reel, then set keywords (include a list, exclude words, or Any comment). You can add public replies with several variations that ManyChat rotates. Then add an Instagram Send Message node and select Send as a Private Reply. ManyChat says that otherwise “you won’t be able to continue with the automation”. Click Set Live when done.
ManyChat lists limits on that first node: it “can contain only a single content block” (text or an image, with buttons or Quick Replies), and you cannot use User input, Instagram DM Lists, Typing delays or Dynamic blocks in it. The sentence that most weakens a comment-to-DM plan is also on that page: sending the private message “does not automatically opt the user into your Instagram channel and does not open the 24-hour messaging window”. The window opens only when the person replies or taps a regular button or quick reply. An Open website button does not count. ManyChat also says the trigger “only activates for the first comment a user leaves under a post or reel”, and calls this “a limitation on Instagram’s side” that “applies to all tools that use their API”. That is ManyChat’s statement; Meta’s page states the one-message rule but not this wording. For a simpler path, ManyChat’s Auto-DM links from comments Quick Automation sends messages in this order: Opening DM, email collection, follow request, main message with the link, follow-up reminder.
Inrō: the “Someone comments on your post” trigger
Inrō’s trigger reference describes a two-step setup. Step 1 chooses the posts: All posts, Next post only, Posts with keyword(s) in caption, Posts with URL in caption or Select posts manually. Step 2 chooses the comments: all comments, comments with a keyword, AI-detected intent, or comments that tag someone. Inrō warns that AI-detected intent “isn’t always accurate”. When you activate the scenario, Inrō offers to trigger on existing comments from the last 7 days, once per person, which matches Meta’s 7-day limit. The Live comment trigger is marked as a Pro trigger.
LinkDM: Post AutoDM and Reels AutoDM
LinkDM’s product page lists Post AutoDM and Reels AutoDM (“Add trigger keywords or respond to all comments”), Facebook AutoDM, Advertising AutoDM for sponsored-post comments, Comment Auto-Reply (“reply to comments with a comment once a DM has been sent”) and Rewind (“Backsend DMs to eligible comments”). LinkDM says it is “a member of the Meta Business Partner program”.
Meta Business Suite: Comment to message
Meta’s own option sits in Meta Business Suite on desktop. Meta’s help page says to go to Inbox, click Automations, click Create automation and choose Comment to message, described as “Send a message reply to comments on your posts that contain specific keywords or phrases”. A second Meta help page describes the same template as replying “to a comment that contains specific hashtags” and says it is “only available on Meta Business Suite desktop”. Neither page names the channels for this template, and Meta notes that “some automations may not be available for some channels”, so check the Instagram option appears for your account. Also note that turning on Meta Business Agent pauses existing automations.
Route B: build comment-to-DM on the Instagram API
The API build has four parts: permissions, a verified webhook, a handler and the private reply call. Meta runs two configurations, and the permission names differ.
| What you need | Instagram API with Instagram Login | Instagram API with Facebook Login |
|---|---|---|
| Login type | Business Login for Instagram | Facebook Login for Business (Instagram linked to a Facebook Page) |
| Token | Instagram User access token | Facebook Page access token |
| Host | graph.instagram.com | graph.facebook.com |
| Private reply permissions (Instagram Platform guide) | instagram_business_basic, instagram_business_manage_comments | instagram_basic, instagram_manage_comments, pages_read_engagement (plus ads_management and ads_read if the Page role came via Business Manager) |
| Private reply requirements (Instagram Messaging guide) | Not covered by that guide | instagram_manage_comments and pages_messaging; a Page token from someone who can perform the MESSAGING task; the Human Agent feature; Advanced Access |
| Comment webhook permissions | instagram_business_basic, instagram_business_manage_comments | instagram_basic, instagram_manage_comments, pages_manage_metadata, pages_read_engagement, pages_show_list |
| Follow-up messages after a reply | instagram_business_manage_messages (messages webhook) | instagram_manage_messages (messages webhook, which Meta lists under Instagram Messaging on the Messenger Platform) |
| Private reply endpoint | POST /<APP_USERS_IG_ID>/messages | POST /<PAGE_ID>/messages |
Meta publishes two private reply guides for the Facebook Login side, and they list different permissions. If you use Facebook Login, request the union of both rows.
Subscribe the webhook. In the App Dashboard, add a callback URL and verify token. Meta sends a GET with hub.mode, hub.challenge and hub.verify_token, and your server must return the hub.challenge value. Then enable the fields per account: POST to /<INSTAGRAM_ACCOUNT_ID>/subscribed_apps with subscribed_fields=comments (Instagram Login) or to the Page’s /subscribed_apps edge (Facebook Login). Meta signs each notification with an X-Hub-Signature-256 header, retries failed deliveries “over the next 36 hours”, and tells you to deduplicate. It also warns that a comment on a boosted or ad post “may result in duplicate webhook notifications”.
Read the payload. On Business Login for Instagram, the comment ID is value.id. On Facebook Login it is value.comment_id, with parent_id when the comment is a reply. Both carry from.id, from.username, text and media.id, and ad comments add ad_id and ad_title.
Send the private reply. Meta’s request puts the comment ID in the recipient field:
curl -i -X POST "https://graph.instagram.com/v26.0/<APP_USERS_IG_ID>/messages" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <ACCESS_TOKEN>" \
-d '{"recipient":{"comment_id":"<COMMENT_ID>"},"message":{"text":"Want the price list? Reply YES"}}'On success Meta returns a recipient_id (the commenter’s Instagram-scoped ID) and a message_id. We did not send this request to a live account. The handler logic below was run against a fixture we built: a signed sample payload with three comment events. It sent one reply, skipped a non-matching comment, skipped a duplicate delivery of the same comment ID, rejected a bad signature, and sent nothing when the event was 8 days old.
import hashlib, hmac, json, re, time
APP_SECRET = b"your-app-secret"
KEYWORDS = {"price", "link"}
SEVEN_DAYS = 7 * 24 * 3600
seen = set() # use a database table in production
def valid_signature(raw_body, header):
expected = hmac.new(APP_SECRET, raw_body, hashlib.sha256).hexdigest()
return hmac.compare_digest("sha256=" + expected, header or "")
def comments_to_reply(raw_body, header, now=None):
if not valid_signature(raw_body, header):
return []
now = now or time.time()
out = []
for entry in json.loads(raw_body).get("entry", []):
for change in entry.get("changes", []):
if change.get("field") != "comments":
continue
v = change["value"]
cid = v.get("id") or v.get("comment_id") # Instagram Login / Facebook Login
words = set(re.findall(r"\w+", v.get("text", "").lower()))
if cid in seen or not (words & KEYWORDS):
continue
if now - entry.get("time", now) > SEVEN_DAYS:
continue
seen.add(cid)
out.append({"recipient": {"comment_id": cid},
"message": {"text": "Want the price list? Reply YES"}})
return outOne caution on that code: entry.time is when Meta sent the notification, not when the comment was made. For live traffic the two are close. For a backfill, read each comment’s timestamp from GET /<IG_MEDIA_ID>/comments instead.
How many commenters can I DM in an hour?
On posts and reels, 750 an hour per Instagram professional account, the private replies limit on Meta’s rate-limits page. That is generous until a reel takes off, so do the arithmetic before you promise “DM me” in a caption. Suppose a reel draws 3,000 trigger-word comments an hour for 6 hours: 18,000 comments. At 750 an hour, sending them all takes 18,000 ÷ 750 = 24 hours. Comments stop at hour 6 and the queue clears at hour 24, so the last commenter waits about 18 hours. That is inside Meta’s 7-day limit but far from instant. A Live is different: 100 private replies a second, but only while the broadcast runs.
| Trigger-word comments per hour (steady) | Private replies Meta allows per hour | What happens to the queue |
|---|---|---|
| Up to 750 | 750 | No queue; replies go out as comments arrive |
| 1,500 for 2 hours (3,000 total) | 750 | Clears after 4 hours; last commenter waits about 2 hours |
| 3,000 for 6 hours (18,000 total) | 750 | Clears after 24 hours; last commenter waits about 18 hours |
| Live comments | 100 per second, during the broadcast only | Anything still queued when the Live ends is never sent |
Whether a given tool queues, drops or spreads replies over time is set by that tool, not Meta. ManyChat says it turns on “a special mechanism on the backend” for accounts with high comment volume. Ask your vendor how its queue behaves near the 750 limit.
Comment-to-DM troubleshooting: Meta’s error codes
These codes come from Meta’s Messenger Platform “Common Error Codes” page, which includes the Instagram Messaging errors, and from the webhook setup limits. The “likely cause” column quotes or closely follows Meta’s description. Where Meta gives no cause, we say so.
| Symptom or code | Meta’s message | Likely cause and fix |
|---|---|---|
| No webhook at all | “Private accounts do not receive comment or mention notifications” | Account is private, app is not Live, or the app lacks Advanced Access; fix the setting, publish, or complete App Review |
| 100 / 2534025 | “The comment is invalid for a private reply” | Meta says to make sure “the type of data you are sending in your private reply is allowed”; also check the comment is under 7 days old and has not had a private reply already (our inference, not Meta’s wording) |
| 10 / 2534022 | “This message is sent outside of allowed window.” | Meta gives no cause; most likely a follow-up was sent before the commenter replied, or more than 24 hours after their reply (our inference, not Meta’s wording) |
| 100 / 2534037 | “The action is invalid because your app is not the thread owner.” | Another app, including Meta Business AI, owns the conversation; wait for pass_thread_control, or ask the business to enable “Take control of conversations with your Business AI” |
| 551 | “This person isn’t receiving messages from you right now.” | The person has blocked or restricted your messages; stop and mark them as opted out |
| 613 / 2534040 | “Calls to this api have exceeded the rate limit.” | Meta says your app “has reached the rate limit”; for private replies on posts and reels that limit is 750 an hour; pause and queue |
| 200 / 2534041 | “The owner of the Instagram Professional account has revoked your app’s access.” | Reconnect the account and grant permissions again |
| 100 / 2534013 | “The page is not linked to an Instagram account” | Facebook Login route: use the Page linked to the Instagram professional account |
| 10 / 2534077 | “Cannot verify the connection between the IG account, the logged in user and the page.” | Relink the Page and Instagram account; check two-factor authentication |
| 100 / 2534029 | “The business has been blocked from sending messages via the IG Messaging API” | A policy violation must be fixed first |
| 10 / 1893063 | “You are temporarily restricted from sending messages.” | Meta found activity that does not follow its messaging policies; slow down and review your flow |
| 190 | “Invalid OAuth access token.” | Expired or wrong token; refresh it |
One symptom has no error code: the same person comments twice and gets one DM. ManyChat attributes this to Instagram, and Meta’s one-message-per-comment rule explains part of it. Treat it as expected behaviour, not a bug.
Which tool should run my comment-to-DM automation?
Disclosure: zian.ai publishes this page and Zian appears first in this table. LeadsNow.ai runs on Zian. Methodology: a tool is included if its own help or product page, read on 22 October 2026, says it sends automated Instagram DMs. Each cell states only what that tool’s own pages say. “Not stated” means we could not find it on the pages we read, not that the product cannot do it. This is the seven options we compared, not a sweep of the category.
| # | Option | Comment trigger (own pages) | After the commenter replies | Best for |
|---|---|---|---|---|
| 1 | Zian AI | Comment-triggered private replies not stated on zian.ai, as at 22 October 2026 | AI agent runs Instagram DM and Facebook Messenger conversations, qualifies and books appointments, follows up by voice call, SMS, email and WhatsApp, integrates with HubSpot, Salesforce, HighLevel and Zapier; 30+ languages | Teams that want the conversation after the comment to end in a booked appointment on any channel |
| 2 | LeadsNow.ai | Managed, done-for-you service; comment-triggered private replies not stated on leadsnow.ai, as at 22 October 2026 | Done-for-you AI appointment setting that runs on Zian; pay-per-result; 50,769+ appointments; leads answered in under 60 seconds, 24/7 | Businesses that want booked appointments without running the setup |
| 3 | ManyChat | “User comments on your Post or Reel” trigger; specific, all or next post; include or exclude keywords; public reply variations; separate Live comments trigger | Flow continues once the person replies or taps a button or quick reply | Creators and marketers building keyword flows by hand |
| 4 | Inrō | “Someone comments on your post”; keyword, AI-detected intent or tag filters; backfill of the last 7 days | Scenario continues; contacts can be filed into folders that start the next scenario | Accounts that want intent matching rather than exact keywords |
| 5 | LinkDM | Post and Reels AutoDM; keywords or all comments; sponsored-post comments; Rewind backsend | Flow Automation schedules DMs and reminders after engagement | Creators sending links from comments |
| 6 | Meta Business Suite | “Comment to message” template, desktop only | Inbox automations and manual replies | Small accounts wanting Meta’s native tool |
| 7 | Your own Meta app | Whatever you build on the comments webhook | Whatever you build; you carry App Review, tokens and the queue | Teams with a developer and a reason to own the code |
Our rule of thumb: if the private reply only has to deliver a link, a flow builder (rows 3 to 6) is enough. If a reply has to become a qualified lead and a calendar booking, with reminders on SMS or a call after Instagram’s window closes, you need an agent rather than a flow. Our guide to choosing an AI appointment setter for Instagram scores that part.
Apply For Partnership: Zian runs Instagram DM and Facebook Messenger conversations alongside AI phone calls, SMS, email and WhatsApp, and books appointments from inbound and outbound conversations. Each of Zian’s three listed plans, including Intel + Widgets (Free Forever), starts with a partnership application.
Frequently asked questions
How do I automate Instagram comments to DM?
Connect an Instagram professional account to a tool or Meta app with the comments permission (instagram_business_manage_comments on Business Login for Instagram), subscribe to the comments webhook, and send a private reply using the comment ID. Meta allows one message per comment, within 7 days, and you can continue only if the person replies.
How many DMs can I send to someone who commented on my post?
One. Meta’s Private Replies guide says “Only one message can be sent to the commenter”. Further messages are allowed only if the person responds, and they must be sent within 24 hours of that response, as Meta’s Send a Private Reply to a Commenter page states.
Does a comment open the 24-hour messaging window?
No. Meta’s Instagram Messaging guide says you can continue the conversation “within the 24-hour messaging window” only when the person responds to your private reply. ManyChat’s help centre says the same: a private reply does not open the window until the person replies or taps a button or quick reply.
Why is my Instagram comment automation not sending DMs?
Check four things in order: the account is a public professional account, Allow Access to Messages is turned on, the comment is under 7 days old, and the person has not already had a private reply for that comment. A self-built app also needs to be Live with Advanced Access before Meta sends comment webhooks for real commenters.
Can I automate Instagram Live comments to DM?
Yes, through the live_comments webhook, but only while the broadcast is running. Meta says private replies to Live comments “cannot be sent” once the broadcast ends. The rate limit is 100 calls per second per account for Live comments.
Is Instagram comment-to-DM automation allowed by Meta?
Yes, through Meta’s Private Replies feature and approved permissions. Meta’s Developer Policies still require consent under applicable law, an opt-out you honour immediately, and no spam, which Meta says includes “failing to deliver promised experiences”. Where the law requires it, the bot must say it is automated.
Apply For Partnership: turn the replies your comment automation earns into booked appointments. Zian’s AI agents run Instagram DM, Facebook Messenger, voice, SMS, email and WhatsApp conversations in 30+ languages. Zian is in partnership-application beta.
Where every figure on this page comes from
| Figure | Who published it | Link | Date read |
|---|---|---|---|
| One private reply per comment; 7 days; Live only during broadcast; follow-ups within 24 hours of a response; Inbox or Request folder; post link included; Instagram Login permissions and endpoint | Meta for Developers (Send a Private Reply to a Commenter, updated 30 June 2026) | Private Replies | 22 October 2026 (via r.jina.ai) |
| Facebook Login private replies: instagram_manage_comments, pages_messaging, MESSAGING task, Human Agent feature, Advanced Access; Standard Access limited to people with a role on the app; duplicate notifications on boosted or ad posts | Meta for Developers (Private replies, Instagram Messaging, updated 2 July 2026) | Private replies, Instagram Messaging | 22 October 2026 (via r.jina.ai) |
| Public account required; Advanced Access for comments webhooks; app must be Live; verification request; X-Hub-Signature-256; retries over 36 hours; subscribed_apps calls | Meta for Developers (Set up Instagram Webhooks, updated 20 October 2026) | Webhooks setup | 22 October 2026 (via r.jina.ai) |
| Webhook field permissions for comments, live_comments and messages | Meta for Developers (Instagram webhook fields and permissions) | Webhook fields | 22 October 2026 (via r.jina.ai) |
| Comment payload fields (value.id, comment_id, parent_id, ad_id) | Meta for Developers (Comment Moderation, updated 20 October 2026; webhook examples, updated 16 September 2026) | Comment Moderation | 22 October 2026 (via r.jina.ai) |
| Connected Tools, Allow Access to Messages toggle path | Meta for Developers (Get started with Instagram Messaging) | Get started with Instagram Messaging | 22 October 2026 (via r.jina.ai) |
| Professional account, business or creator; Standard and Advanced Access; App Review and Business Verification | Meta for Developers (Instagram Platform overview, updated 28 September 2026) | Instagram Platform overview | 22 October 2026 (via r.jina.ai) |
| 750 private replies per hour for posts and reels; 100 per second for Live comments | Meta for Developers (Graph API Rate Limits) | Rate Limits | 22 October 2026 (via r.jina.ai) |
| 24-hour standard window, up to 7 days after a Click-to-Direct ad; actions that open the window; disclosure rule, California and Germany | Meta for Developers (Messenger Platform and IG Messaging API policy, updated 28 September 2026) | Messaging policy | 22 October 2026 (via r.jina.ai) |
| Opt-in, opt-out, excessive negative feedback, “failing to deliver promised experiences” | Meta (Developer Policies) | Developer Policies | 22 October 2026 (via r.jina.ai) |
| Error codes 2534025, 2534022, 2534037, 551, 2534040, 2534041, 2534013, 2534077, 2534029, 1893063, 190 | Meta for Developers (Common Error Codes) | Common Error Codes | 22 October 2026 (via r.jina.ai) |
| Comment to message template; desktop only; Meta Business Agent pauses automations | Meta Business Help Centre | Set up Inbox Automations; About Automated Responses | 22 October 2026 (via r.jina.ai) |
| ManyChat trigger names, single content block, window opens only on reply, first comment only, high-volume mechanism; separate Live comments trigger | ManyChat Help | Instagram Post and Reel Comments trigger; Instagram Live Comments Trigger | 22 October 2026 (via r.jina.ai) |
| ManyChat Auto-DM links from comments message order | ManyChat Help | Auto-DM links from comments | 22 October 2026 (via r.jina.ai) |
| Inrō post and comment filters; 7-day backfill once per person; Live trigger is Pro | Inrō Help | Triggers: The Complete Reference | 22 October 2026 (via r.jina.ai) |
| LinkDM features; Meta Business Partner program statement | LinkDM | linkdm.com | 22 October 2026 (via r.jina.ai) |
| 18,000 ÷ 750 = 24 hours worked example | zian.ai calculation from Meta’s 750-per-hour limit | This page | 22 October 2026 |
| 50,769+ appointments (Zian and LeadsNow.ai); LeadsNow.ai pay-per-result and under-60-second response | Zian AI; LeadsNow.ai | zian.ai home page counter (unlinked: not a post); leadsnow.ai | 22 October 2026 |