When a story reply asks for something you can send

A story reply never becomes a public comment. It arrives as a direct message, straight into your inbox thread with that person, the moment they tap reply. A story reply trigger watches those messages, and when one matches the configured keyword mode, it can answer in the same thread with the file or link you attached.

That's the real difference from a feed post. A comment on a post is public, so the automation posts a public reply first, then a DM. A story reply is already private, so there is nothing to answer publicly, and the automation goes straight to the DM thread the person opened by replying.

A story might show the books discussed in a podcast and say, ‘Reply BOOKS for the reading list.’ The viewer's reply is the specific request; watching the story without replying is not.

Keep the invitation readable and name the resource. A vague ‘DM me’ leaves someone to guess what to ask for, when you could just tell them.

Set up the resource in ReplyMagnet before publishing the invitation.

A feed campaign can be scoped to selected posts. ReplyMagnet’s Story trigger is account-wide, so choose a keyword that identifies the intended resource across the account’s Stories. This describes ReplyMagnet’s campaign scope, not a restriction on every Instagram automation tool.

Setting one up takes a few steps:

1. Connect a Business or Creator Instagram account; personal accounts can't run automation.
2. Choose the story-reply trigger, which applies account-wide rather than to one story.
3. Set the keyword to watch for in story replies.
4. Attach the file or link to deliver and write the DM text.
5. Save, review and launch the campaign, then publish a Story naming the keyword and test with a text reply from a second account.

Before you publish the story, check:

• The account is a Business or Creator account, connected in ReplyMagnet.
• The keyword is short and easy to type from a phone.
• The file or link is attached and the DM text is written.
• The engagement allowance has room for the story's expected reply volume.

It runs on Instagram's official Graph API, the same interface Meta reviews through App Review, not a script that logs into the app on your behalf. Instagram's terms don't allow the latter.

The current plan catalogue lists Story triggers under Basic and higher. Confirm the trigger is available for your workspace before publishing the offer. The 30-day no-card trial previews eligible Pro features with a 1,000-engagement allowance; it is separate from the ongoing Starter plan. Check plans and billing before promoting an ongoing Story campaign. A free PDF comment campaign is a different plan-fit decision.

For the BOOKS example: ‘Here's the reading list from today's episode, including the two titles mentioned at the end.’

Make the document title recognisable even after the story disappears. A file named only ‘Today's picks’ becomes confusing in an older conversation. Include the episode name or date where useful.

If the link opens a form, explain the requirement in the story or reply. For a public reading list, direct delivery may be enough.

If the resource sits behind an email gate, say so in the reply so the extra step isn't a surprise. A public reading list can skip the gate entirely.

Keep the DM short enough to read on a phone in one glance. A long paragraph delays the moment the file or link actually appears.

Every trigger type has a window set by Meta, not by ReplyMagnet, and a story reply gets 24 hours from the moment it's sent. A feed comment gets 7 days, because it rides a longer private-reply window instead of the standard messaging window a story reply uses.

The gap matters most when a campaign is over its monthly engagement allowance and a reply is parked in the overflow queue. The queue holds the request and releases it oldest first as headroom opens, on every plan, but it can't extend the platform's window.

If the wait runs past 24 hours, the send is marked expired instead of attempted, because a late one would be rejected regardless. The clock only restarts if the person replies again, so an expired request needs a fresh reply to try again.

Queued replies also release in the order they arrived, not by campaign type, so a story reply can sit behind older parked feed replies if the same workspace is over its allowance.

Check your allowance before a time-sensitive story. ReplyMagnet's plans range from 1,000 engagements on the free plan up to 400,000 on the $79 plan, and a queue can absorb a burst of replies, just not a closed window.

The two routes share resource-delivery concepts, but their incoming events and timing differ. A configured keyword can select a campaign, the DM still carries a tracked link served from ReplyMagnet's own domain, and every step is still logged as its own event.

If you already run a feed campaign, a story campaign is the same tool pointed at a different surface. For an Instagram Live, the Live resource guide uses an incoming-message keyword instead. The table below lines up where the two diverge.

1. Configure the intended story-reply trigger and resource.
2. Publish the story invitation with the matching keyword.
3. Reply to the story from a separate account.
4. Open the delivered resource and check that any captured contact appears where expected.
5. Confirm the DM lands in the same thread the story reply opened, not a separate conversation, which is what tells you the automation matched the right event.

Test the configured keyword mode as well. Contains can accept BOOKS inside a longer request; Exact requires the trimmed reply to equal BOOKS, ignoring case. Turn smart matching off for this isolated keyword test, then evaluate it separately if needed. A Story reaction, Story mention and text reply are different events; test the text-reply workflow described here rather than assuming every event starts the same campaign. See the keyword matching examples.

When the offer expires, pause or revise the campaign and resource. Older conversations may still hold the link, so keep the destination's availability accurate.