Find why your Instagram comment-to-DM is not working

“It did not work” can describe several different problems. A comment may never reach the tool, reach it without matching a campaign, match but wait for quota, or produce a DM the recipient has not found. The download can also fail after messaging succeeded.

In ReplyMagnet, open Delivery activity and look for the test comment. The page shows the latest 30 messages and comments across your accounts, so inspect a recent, identifiable example. It separates the received interaction, campaign match, public reply and DM. Keep those observations separate while investigating.

If you have not created a campaign yet, start with the Instagram auto-reply setup guide. This guide is for a campaign that already exists and an expected result that is missing.

Original troubleshooting diagram: investigate the first unconfirmed stage, then test the next stage after correcting it.

Choose a single request you can trace. Comparing a comment from yesterday with a different campaign edited this morning makes the evidence ambiguous. Note which account owns the post and which account wrote the comment. Record the time with its timezone; ReplyMagnet activity displays received times in UTC.

Take a private screenshot of the relevant settings if that helps your team, but remove customer messages and contact details before sharing it outside the team. Do not include passwords, access tokens or unrelated conversations in a support request.

For example, suppose a cafe offers a menu PDF with “Comment MENU.” Write down the exact post URL, the visitor's actual comment, whether the MENU campaign was live, and what the activity row says. This is an illustrative troubleshooting example, not a customer case study.

If many customers are affected, stop promoting the broken promise while you investigate. Keep the existing evidence and avoid deleting the campaign as your first move.

First check the handle. A team managing several businesses can connect the wrong profile or select a similar-looking post. Open the original post in Instagram and compare it with the account and post selected in the campaign.

Use another account for a controlled test. ReplyMagnet ignores comments written by the connected account itself, so commenting MENU as the cafe does not test a customer's path. Use a new comment after confirming the campaign is live; an old comment is poor evidence of what the current settings do.

If the account needs reconnection, follow the prompt and approve access through Instagram's own authorization screen. The connection documentation explains account type and connection errors. After reconnecting, review the campaign again: disconnecting pauses associated campaigns, so a successful connection alone does not establish that delivery is live.

An absent activity row is a clue, not proof that Instagram never sent the event. The view is limited to recent records, and a loading error is different from an empty list. Save the approximate test time and escalate if a fresh test is still missing.

Work through configuration in a fixed order. Confirm the correct account, the live status, the post scope and then the trigger. A campaign for one reel does not cover a different reel just because both captions offer the same resource.

Check which keyword mode is selected. Contains mode uses case-insensitive whole-word matching: MENU can match “send MENU please,” but GUIDE does not match guideline. Exact mode requires the entire comment, after trimming spaces, to equal the keyword without regard to case: MENU matches menu, but not “send MENU please.” Copy the configured keyword alone for your first retest instead of rewriting the entire caption.

Smart matching adds another variable because it can assess intent after keywords do not match. When diagnosing delivery, begin with an explicit configured keyword so you can isolate the ordinary matching path. A natural-language request that fails to match does not establish that the connection is broken.

Check for overlapping campaigns on the same post. Keep your test tied to one intended resource and compare the campaign name in activity with the one you expected. The campaign reference explains scope and matching modes; the keyword guide helps prevent ambiguous requests once the incident is resolved.

A visitor may see “Check your DMs” while the private-message stage is still waiting or has failed. Read that request's activity row. “Not recorded” means there is no recorded DM send in that view; it should not be rewritten as a specific permission error without evidence.

Check whether the job is processing, pending with a retry time, failed, or expired. If a reconnect prompt accompanies the incident, resolve it through the supported connection flow. Repeatedly disconnecting a healthy account changes more settings without establishing why this request stopped.

A public reply marked “Skipped: send could not be confirmed” is also an uncertainty signal. Do not tell a customer that no public reply exists just because the application could not confirm it. Inspect the original Instagram thread before taking a manual action that might duplicate a response.

For the cafe example, record “public reply: Sent; DM: Not recorded; status: failed” instead of “Instagram is down.” The narrower description gives support something it can investigate.

An allowance queue is different from a temporary processing failure. “Waiting for engagement quota” identifies the former. Check the workspace allowance and the billing reference before changing trigger rules that already matched.

If activity gives a retry time, preserve the reference and check again after that time. Do not promise an exact delivery time to customers based only on a queued status. A final failed status says processing will not automatically retry further and directs you to support.

ReplyMagnet also checks the age of the original interaction. Comment replies, direct messages and story messages have different eligibility conditions. Read the actual expiry detail rather than applying one timing rule to every interaction. Reconnecting does not make an old request newly eligible. Meta maintains the platform requirements in its Instagram messaging documentation.

The messaging rules guide provides the broader context. When activity reports expiry, investigate with a new, willing test interaction instead of attempting to force the expired delivery.

Confirm which Instagram account the person used to comment. Someone switching between personal and business profiles may be checking the inbox of a different account. Have your tester inspect Instagram directly rather than relying only on a phone notification.

Ask them to check message requests as well as the main conversation list. Do not ask them to loosen privacy controls just to make a test succeed. If they still cannot find the message, record that discrepancy alongside the accepted-send record and raise it with support.

Keep the evidence vocabulary precise. “Sent” describes acceptance by the platform. “The tester opened the DM” describes a separate observation. “The tester opened the correct menu PDF” verifies another step. The analytics guide explains why delivery and resource activity should be measured separately.

Avoid sending an extra DM simply because a read confirmation is unavailable. First establish what the person actually received and whether another response is appropriate.

Use the link your tester received, not a different URL copied from your file library. Check the destination on a phone. Confirm that the title and contents match the promise in the caption and the private message.

If an email or phone capture step appears, compare it with the campaign configuration and what the offer told the reader to expect. A required field can be working as configured while still creating confusion. The capture-gates documentation distinguishes these steps from sending the DM itself.

If the file is wrong, missing or inaccessible, review the attached item in Assets. Correct that specific destination and repeat the resource test. Reconnecting Instagram will not repair a missing file or make the wrong brochure useful.

Use a quiet post you control and a willing tester. Confirm that the campaign is live before commenting. Keep the exact keyword simple, verify the account handle and record the time. Follow the request through activity, Instagram and the resource page.

Original retest diagram: one changed setting makes the before-and-after comparison interpretable.

Copy this short worksheet into your team notes:

• Original post and comment:
• Original time and timezone:
• Account and campaign:
• Last confirmed stage:
• Setting changed and reason:
• New test comment and time:
• Match / public reply / DM status:
• Tester found message: yes or no:
• Correct resource opened: yes or no:
• Support reference and next action:

If MENU initially had no match because the wrong post was selected, change the post selection and test MENU again. Do not also change the keyword, resource, reply text and capture fields. If the result improves, you will know which change was relevant.

After the positive test, an unrelated comment can check that a keyword campaign does not respond to everything. Stop once you have enough evidence; repeated test comments add noise to your public post and activity history.

A useful request reads like this:

“Campaign: [name]. Post: [link]. A test account commented [exact keyword] at [time and timezone]. Expected: a DM containing [resource]. Activity shows [match], [public reply], [DM] and [status]. Support reference: [reference]. We changed [one setting] and tested again at [time]. The new result was [observation].”

If there is no activity entry, say so and include the test time and connected handle. Share only the information needed to investigate; keep passwords and authorization tokens out of messages and screenshots.

Once the problem is resolved, keep the successful test record with the campaign. It becomes a baseline when someone later changes a post, resource or permission. New to ReplyMagnet? Create an account, build one clear resource campaign and test the complete path before promoting it widely.