Playbooks · 4 min read
Story Replies Are Already DMs, and That Changes Everything
Most automation advice is written about comments, because comments are public and easy to demonstrate. Story replies work differently enough that applying comment thinking to them produces a setup that quietly underperforms.
The difference in one line: a story reply is not a thing you convert into a DM. It is a DM, and its clock started the moment they sent it.
What you gain
No public middle step. With a comment you write a receipt everybody reads, then the real answer in DM. With a story reply there is no receipt, no shopfront, and no one else watching. The whole exchange is private from the first word.
Lower friction to start. Replying to a story is one tap and a sentence, done without leaving the thing they were already looking at. Commenting is a more deliberate, more public act.
Better context. You know exactly what they were looking at when they wrote, because a story is one frame. A comment on a carousel could be about any of ten images.
What you lose
Compounding. A comment section with forty answered questions advertises to everyone that this account replies. A story reply is invisible to everyone except you and the sender, so nothing accumulates.
The seven-day cushion. A comment can sit for six days and still be convertible. A story reply that arrives at 11pm and gets no answer by 11pm the next day is finished, and no tool can reopen it.
Reach. Stories go to people who already follow you. Comments arrive from whoever the algorithm showed the post to, which is where new people come from.
Stories are the better conversation and the worse advertisement. Most accounts need both, for different reasons.
Polls give you nothing to trigger on
Worth being explicit, because a lot of published advice implies otherwise.
A poll vote is a tap. It is recorded in your story insights and it produces no message, so there is no event, nothing arrives in your inbox, and there is nothing for an automation to fire on. The same is true of quiz taps, slider reactions, and someone screenshotting your story.
Triggering is weaker here, and that is the design problem
A comment on a post asking "comment PRICE" produces the word price. A story
reply produces whatever the person felt like typing, which is frequently a single
emoji, a reaction to the content rather than a question, or four words with no
punctuation.
Two consequences.
- Keep the keyword list narrow and the fallback silent. A broad any-of list on a surface this freeform will fire on messages that were not questions, and answering "😍" with a price list is worse than not answering.
- Ask for something typeable. A question sticker reading "which size are you after?" produces answers containing size words. A story saying "DM me" produces "hi".
Quiet hours matter more, not less
Stories are watched late. A large share of story replies arrive after 10pm, which is exactly the window most accounts have switched off.
That is usually still the right call — nobody wants a business messaging them at 1am — but it has a cost you should look at rather than assume. A reply held until morning has spent nine hours of a twenty-four hour budget. If your blocked list next morning shows a stack of closed windows behind quiet-hours holds, the hours are eating the conversations rather than protecting them.
A setup that works
- Post a story with a question sticker, phrased so the answer contains a word you can trigger on.
- One automation, narrow keyword list, scoped to nothing else.
- A private reply that answers and asks one closed question, because their answer is the only thing that restarts the clock.
- Negative keywords as usual — a story reply saying "not interested" or describing a problem should never receive a template.
- Check the blocked list after two days and see whether quiet hours are helping or costing.
The honest limit
Stories expire in twenty-four hours; the thread does not. So a week later you may have a conversation open with somebody whose original context has vanished from your own account. You cannot see what they were replying to any more, and neither can they.
That is an argument for answering story replies fast rather than for automating more of them. The automation buys you the first answer. Everything after that is a conversation, and it is better if it happens while both of you still remember what it is about.
If you want the funnel mechanics rather than the surface differences, the story to DM funnel post covers them. For triggers in general, the keyword guide is here.
