Playbooks · 4 min read

Choosing a Trigger Word People Will Actually Type

The PostEngage teamEngineering and support ·
The comment-to-DM flow: a keyword comment, a public reply, and the private thread it opens.

Everything downstream depends on one decision: which word. Get it right and the rest of the setup is straightforward. Get it wrong and you have a beautifully configured automation that never fires, which is indistinguishable from having no automation at all.

Two kinds of trigger, and they behave differently

The invited word. You asked for it in the caption. "Comment GUIDE and I'll send it." The person types it deliberately, spelled the way you spelled it, because they are copying you.

The natural word. Nobody asked. They typed price because they wanted the price, and they typed it however they type things.

The invited word is easy — it is your word, and people mostly copy it correctly. The natural word is where the work is, because you are trying to predict strangers.

What makes an invited word work

  1. One word, not a phrase. "Comment I WANT THE GUIDE" gets typed four different ways. GUIDE gets typed one way.
  2. Not a word that appears naturally in your comments. If you ask for YES under a post that also gets "yes love this", you cannot tell the two apart.
  3. Easy to spell on a phone. RECIPE is fine. AESTHETIC is not.
  4. Say what arrives. "and I'll send the list" makes the word worth typing. "DM me" does not.

Case does not matter — GUIDE, Guide and guide are one keyword — so write it in caps in the caption because it reads as an instruction, and stop worrying about how they capitalise it.

What makes a natural word work

Harvest it. Do not invent it.

Open your notifications, read the last fifty comments and DMs as strings, and write down the exact words people used. That is your list. It will look nothing like the one you would have written from imagination, because your version is the formal one and theirs is thumb-typed at a bus stop.

A harvested price list for one Indian clothing account: price, pric, rate, kitna, kitne, kitne ka, daam, dam, कीमत. Nine entries for one question, every one from a real comment.

The automation builder: the trigger and its keywords, the public reply, the private reply, the test button, and the preview panel replaying real comments.
The preview replays comments you already received against the list you are writing, which finds the spelling you forgot faster than thinking does.

Trigger on the easy word in the sentence

When the same question can be asked many ways, look for the word that survives all of them.

"Is this available in blue?", "do you have this in blue", "blue available?" — three sentences, one shared word: available. Trigger on that, not on the sentence.

In a mixed-language inbox the surviving word is often the English loanword — size, delivery, book, price — because those get typed in Latin script even by people writing the rest in Hindi.

The four ways trigger words fail

  1. Too narrow. price alone, when half your audience types kitna. The automation works perfectly for the half you thought of.
  2. Too broad. link matches "link in bio please" and also "the link doesn't work", which is a complaint receiving a sales template.
  3. Wrong assumption about matching. price does not match pricing; matching is whole-word. kitna does not match kitne. दाम does not match दम — a matra is a vowel, not an accent, so those stay different words.
  4. Colliding with punctuation you forgot about. A hash is punctuation, so #price matches price. Under a giveaway post stuffed with #contest #giveaway #free, any of those words in your list will fire on tag-spam.

Any-of and all-of are different questions

Any-of means one word from the list is enough. That is what most rules want, and it is how you cover eleven spellings of the same question.

All-of requires every listed word in the same comment. It is a narrowing tool, not a stricter version of the same thing — size and blue together, when size alone is too noisy on a post about a whole collection.

Reaching for all-of because any-of "fires too much" is usually the wrong fix. The right fix is scoping the automation to specific posts.

When two automations could both match

It happens, and it is handled rather than dramatic: dedupe means one reply per comment, and cooldown means one person does not get two messages in a minute.

The clean fix is scoping. One automation per product post, each with its own words, rather than several account-wide rules competing over the same comment section.

Re-harvest occasionally

New spellings arrive constantly, and especially after a post travels beyond your usual audience — those people write differently because they are not your regulars.

Once a month, read fifty comments again and add what is new. Ten minutes, and it is the single highest-return maintenance task in this whole product.

If you want the full builder reference, the comment automation guide covers it. For a multilingual audience, the language post goes deeper.

One email when we publish.

No drip sequence, no “quick question” follow-up. Unsubscribe is one click and we honour it immediately.

Try it on your own posts

Free forever. Three minutes to set up.

Start free