Start with Activity, then compare it with the recipient's inbox. No match, waiting for Yes, failed delivery, and no link click are different problems.
First, name the step that is missing
An Instagram comment-to-DM workflow has several separate steps: a comment becomes available, the keyword matches, the private reply is sent, the recipient responds when required, and the promised content is delivered. Saying ‘the DM did not work’ can describe a failure at any one of them. Fixing the wrong step usually creates more tests and fewer answers.
Open Activity in Triggered and find the relevant comment or approximate time. Compare the receipt with what the recipient actually sees in Instagram. A connection badge establishes that an account is linked; it does not verify every future delivery. Before changing settings, record whether there is no match, an opening question, a waiting state, a failed action, or a completed send.
No match in Activity: check the trigger
- Confirm the automation is active and belongs to the intended connected Instagram account.
- Check whether it targets the specific post you tested or eligible all-content monitoring. A keyword on the wrong post is still the wrong test.
- Compare the comment with the keyword and Match style. New keyword rules saved through the builder ignore letter case, but punctuation still matters for an exact-match test.
- Confirm the fresh comment is visible on Instagram from a different account. Do not assume a filtered or unavailable comment reached the integration.
- Inspect Accounts for a connection warning and follow its instructions when permissions need attention.
Triggered's contains matching is substring matching, not whole-word matching. ARM can match CHARM. Exact matching compares the normalized full comment instead. Use a distinctive keyword such as WORKSHOPGUIDE for diagnosis, then decide deliberately whether a more flexible contains rule is appropriate for your real caption.
Opening question sent: check Requests and the Yes response
Ask First intentionally separates the opening question from the final content. If Activity says Waiting for reply, confirm that the recipient found the question and tapped Yes. The resource should not arrive just because a person commented, and choosing No should not send the final content. That is the workflow doing its job, not developing commitment issues.
Look in Message Requests as well as the main inbox. Triggered cannot choose the recipient's inbox folder or force a read. The first private reply does not itself open an ongoing messaging window; a relevant recipient interaction is needed. An ordinary website-link click is not equivalent to the quick-reply response used by Ask First.
Sent you a DM about the guide. If it is not in your inbox, check Message Requests.
Yes was received, but delivery failed: inspect the action
- Connection or permission error: follow the specific account prompt, then perform a fresh test.
- Resource error: correct the destination and verify anonymous access before sending more people to it.
- Waiting for email or SKIP: complete that optional step in the test; do not mistake it for missing delivery.
Read the delivery receipt and recorded error before editing the trigger. Verify that the saved message and delivery URL are still correct. Open the destination without your own signed-in session to confirm it does not require your private access. If the campaign uses a file URL, make sure the recipient can open the file rather than a restricted editor or owner-only preview.
Keep the finished delivery message, including links, within the builder's stated limit. If optional email collection is enabled, there may be a separate step waiting for an email reply or SKIP before content delivery. That email step has its own receipt. A conversation can also become ineligible for further messaging, so do not assume an old Yes authorizes unlimited retries later.
Delivered is not the same as read, clicked, or purchased
If the reply is visible and the resource arrived, the delivery part worked. A person can still ignore it, postpone opening it, or decide the offer is not relevant. Check whether the caption promised the same resource the DM delivers. A mismatch between ‘free checklist’ and an unexpected sales page will not be repaired by a new keyword.
Link tracking can record opens on configured delivery links and file URLs when enabled. Those raw opens can include automated previews, and plain links typed into message text are not automatically rewritten. Do not treat zero recorded opens as proof that every message failed, or one recorded open as proof of a human lead or sale. Keep technical delivery and campaign performance separate.
Run one clean retest, then ask for targeted help
Use one specific post, one distinctive exact keyword, and a fresh matching comment from a different account. Avoid rapid repeat comments from the same tester as proof of broad reliability. If other automation providers are connected, check that they are not responding to the same production keyword. Do not delete a working campaign or disconnect every account just to make the settings look freshly laundered.
For support, provide the post link, approximate comment time and time zone, tested keyword, expected step, and observed Activity result. Redact unrelated private messages from screenshots. Do not send passwords, access tokens, or verification codes. A reproducible example lets support investigate the missing step without guessing which of six nearly identical tests you meant.
Sources and platform guidance
The setup examples above describe Triggered. These publisher documents explain relevant platform behavior; another tool’s features are not automatically available here.
Written for Triggered’s current workflow. Platform permissions and capabilities can change. ManyChat is an independent product; this guide is not affiliated with or endorsed by ManyChat.