Every creator automates post comments. Almost nobody automates story replies — which is strange, because story replies are the higher-intent signal.
Why story replies are technically easier
Here is the part most people get wrong: a story reply is a direct message.
That means the user has messaged you first, which opens the standard **24-hour messaging window** automatically. You do not need the Private Reply API. You do not need a message tag. You just reply.
Compare that to comment automation, where a cold commenter has no open window and you must use Private Reply addressed by comment ID or the message silently fails.
Story replies are the easy case that everyone skips.
Replies vs mentions — two different webhooks
Two distinct events, and they need different handling:
- Story reply — someone messages you back from your story. Arrives on the messages webhook, with a reference to which story they replied to.
- Story mention — someone reshares your post or tags you in their story. Arrives on the mentions webhook.
The reply already has an open window. The mention does not necessarily, so check the standard messaging rules before you send.
A useful pattern: treat mentions as a thank-you trigger (someone just gave you free distribution) and replies as a sales trigger (someone is asking about the thing).
Why the intent is higher
Three reasons story-triggered conversations run further than comment-triggered ones:
- It is already private. No audience, no performance, no self-consciousness.
- Full context. They watched the story, so they know exactly what the offer is.
- It is time-boxed. Stories expire in 24 hours, so replies cluster tightly around the moment of interest.
That third point matters operationally: story replies come in bursts and go cold fast. Automation that answers in seconds captures value that a reply eight hours later does not.
What to actually send back
The most common mistake is a generic greeting. Someone replied to a *specific* story about a *specific* thing — a generic "hey, thanks for reaching out!" throws that context away.
A story reply automation should:
- Reference what the story was about
- Answer the likely question directly
- Give exactly one next step with the link
- Stop — no menu, no five options
For a story mention (a reshare), the shape is different: thank them, and reward the share. A discount code for people who reshared is one of the cheapest loyalty mechanics on the platform, and it costs you nothing when nobody shares.
Setting it up in StackPicks AutoDM
In the rule builder, pick the trigger "shares or replies to your story". Keywords are optional here — unlike comments, where you usually want to match "LINK" or "PRICE", story replies often warrant a catch-all because the story itself did the qualifying.
Then write the DM, add your link, and go live. The live preview shows exactly what the recipient sees before you publish.
The 24-hour discipline
One caveat worth stating: the window is 24 hours from their last message, not from your story going up. If someone replies and you take two days to follow up, the conversation is closed unless they message again.
This is why automated first response plus a human follow-up inside the window beats a purely manual process. The automation holds the door open; you walk through it.
Related reading
- Instagram Private Reply API — the harder case, comment triggers
- Auto-DM During Instagram Live — the third trigger most people miss
- Instagram Auto-DM Compliance 2026 — staying inside Meta's rules