Creator Playbook: Story Replies and Mentions into DMs

Manish 30 October 2026 7 min read

Basics already published: Story reply automation, Story mention thank-you DMs, and booking from Story replies. This playbook is campaign sequencing for creators, not a fourth setup guide. One job per Story. Different keywords. Turn rules off when the Story expires if the offer expired.

Stories die in 24 hours. Feed rules do not. If you leave last month’s drop URL on a mention automation, you will thank people with a 404. Sequence the week so merch, thanks, and booking do not share a word and do not share a live rule after the sticker is gone.

A week of Stories that does not collide

Mon: merch LINK on a reply sticker, rule story-mon-merch, UTM campaign story-mon-merch. Pause Tuesday morning if the SKU can sell out overnight.
Wed: mention thank-you with a code (disclose the relationship). Different word than LINK — CODE or THANKS. Do not send merch checkout on a mention of your conference photo.
Fri: booking — BOOK or DATES, never LINK. Scheduler must be the live week, not last Friday’s leftover.

If Monday and Friday both listen for LINK, Friday’s booking audience gets a hoodie. If Wednesday’s mention rule is still on in October, conference leftovers get a summer code. Name rules with the date. Calendar the pause. Auto reply is the product surface; the playbook is the calendar.

When the Story dies, the rule should die

Do not leave last month’s drop URL on a mention automation. Do not leave a sold-out mini-session scheduler on a reply sticker from last weekend. Pause is part of the creative, not admin trivia. If the offer is evergreen (newsletter), you may leave a reply keyword on, but then every Story that uses that sticker must still be the newsletter — not a mixed week.

Mentions are not comments. A mention thank-you should not include a hard sell unless that Story asked for it. “Thanks for the tag — here’s the lookbook if you want it, reply NO and I’ll stop” is optional. A looping checkout on every mention is how you train friends not to tag you.

Reply stickers versus mentions versus feed comments

Reply sticker: they typed a word you invited. Match that word. Mention: they tagged you; your job is thanks, maybe a code, maybe nothing but thanks. Feed comment: a Reel keyword. Do not point all three at one graph with one URL. The private-reply limit still applies per comment; Story replies are a different trigger. Do not expect a Story sticker to “also catch” feed comments.

If you use a follow-gate on a Story, remember non-followers and Request placement. Teach “check Requests” on the Story card too. Gates do not teleport the first bubble into Primary.

Launch week: Story plus Reel without double-sending

Reel teaches LINK. Stories that day should not also teach LINK unless you want two rules competing for the same person on two surfaces with two UTM campaigns (that can be fine if you want to know which surface clicked). If you do not want two DMs, pick one surface for the keyword that day. Many creators: Reel owns LINK, Stories own behind-the-scenes with no keyword, plus one booking Story on Friday with BOOK only.

Write the three jobs on paper before you film.
Create three rules with three names and three pause alarms.
Test each with a second account while the Story is live — after expiry you cannot test the sticker.
After 24 hours, pause anything whose URL should die. Leave only evergreen list rules if they are truly evergreen.

Close friends and tests

A Close Friends Story is a fine test channel if those people know they might get a test DM. Do not test a paid CODE on Close Friends and then forget the disclosure when you post public. The copy should match the audience you will actually run.

Handoff on Stories

Angry replies to a Story, “remove this photo of me,” and brand-deal replies to a mention are human. Do not attach merch. Accessibility questions about an event Story (stairs, captions, refunds) go to a human or a real policy URL, not a ticket LINK. If you are an event promoter that day, use the event article’s sold-out discipline — pause when the show is gone.

Creators who also consult should not put SCOPE on a merch Story. Different day, different word, or different highlight. Collision is the failure mode this playbook exists to prevent.

Friday BOOK must not inherit Monday’s LINK

Monday merch Story: reply sticker LINK, rule story-mon-merch, UTM story-mon-merch. Pause Tuesday morning if the SKU can sell out overnight. Friday booking Story: BOOK or DATES, never LINK. If both listen for LINK, Friday’s booking audience gets a hoodie. Name rules with the date. Calendar the pause. Stories die in 24 hours. Feed rules do not — but a leftover Story keyword on a mention automation is how October still sends a summer code.

Launch day: Reel owns LINK. Stories that day should not also teach LINK unless you want two DMs and two UTM campaigns on purpose. Many creators: Reel owns LINK, Stories are behind-the-scenes with no keyword, Friday owns BOOK only.

Mention thank-you is not a checkout loop

Wednesday they tagged your conference photo. First DM: “Thanks for the tag. If you want the lookbook, here it is — reply NO and I’ll stop.” A looping merch checkout on every mention trains friends not to tag you. CODE on a mention of a sponsored Story needs disclosure. Do not test a paid CODE on Close Friends and then forget the disclosure when you post public. The copy should match the audience you will actually run.

Mentions are not comments. A mention thank-you should not include a hard sell unless that Story asked for it. Reply sticker: they typed a word you invited. Match that word. Do not point sticker, mention, and feed comment at one graph with one URL. After expiry you cannot test the sticker — test with a second account while it is live.

When the Story dies, leftover rules still fire on mentions

Pause mention automations whose URL should die. Mention rules do not expire with the Story unless you pause them.
Sold-out mini-session scheduler from last weekend: pause. A leftover sending “book Saturday” on Monday is a fight.
Evergreen newsletter sticker may stay only if every Story that uses that sticker is still the newsletter — not a mixed week.
Door-time event Story: pause at start time. A 2am leftover “buy tickets” for a show that ended wastes the cap and the friendship.

Angry replies, “remove this photo of me,” and brand-deal replies to a mention are human. Do not attach merch. Accessibility on an event Story (stairs, captions, refunds) goes to a human or a real policy URL. Consultants: do not put SCOPE on a merch Story.

Playbook checklist before you film

Write three jobs on paper: merch, thanks, booking — not three words that collide.
Create three rules with three names and three pause alarms.
Test each with a second account while the Story is live.
Follow-gate on a Story still lands non-followers in Requests. Teach that on the card.
CommentLink does not publish the Story. You do. There is no Live trigger if you go live from Stories. There is no Broadcast Channel post from this product.

FAQ

How should creators combine Story automations?

One job per Story. Different keywords. Turn rules off when the Story expires if the offer expired.

Can I use the same keyword on Stories and Reels?

You can if you want both surfaces measured separately. If you do not want two DMs, pick one surface per day.

Should mention thank-yous include a link?

Optional and light. A looping checkout on every tag trains people to stop tagging you.

When do I pause a Story rule?

When the Story expires if the offer expired, sold out, or the URL changed. Calendar it when you publish.

Do I test after the Story expires?

Too late for that sticker. Test while it is live with a second account.

Can CommentLink post the Story for me?

No. You publish the Story. The automation listens for replies or mentions you configured.

I left Monday’s LINK rule on and Friday’s BOOK did not fire. Why?

If both Stories invited LINK, you trained Friday’s audience onto merch. Different word, or pause Monday’s rule.

Can I test the sticker after the Story expires?

No. Test while it is live. After expiry, only leftover mention rules still matter — pause those separately.

Should every mention get a code?