My welcome automation is answering every single inbound message, including replies to other flows. I did set it up with keywords, or at least I thought I did. What would cause that?
Anh N. ·
We want to run comment 🔥 for the link because typing a word gets fewer comments. Before I promise that in a Reel caption, does an emoji actually work as a trigger?
Wei C. ·
Customers paste an order reference like AB 4821 and I want the flow to recognise it and look it up. A keyword list obviously will not work for that. Is there a pattern option?
Imran Q. ·
Black Friday is coming and we want to post "comment SAVE for the code". I can build the reply, but I do not know how to stop the same person getting the code five times, or how to see how many codes actually went out.
Tomás N. ·
Half our audience writes in Turkish and they spell things three different ways, with and without the dotted i. Do I need to list every variant or does the matcher handle near misses?
We put a poll and a question sticker on stories and get a lot of replies, but they land in the DM inbox mixed with everything else. Can you auto reply to a story reply specifically, or is it just a normal DM?
I have three automations listening for info because different teams built them at different times. Customers get one reply, sometimes seemingly at random. How does it decide, and can I see which one is live?
We sell during Instagram Lives and the comments move too fast to read. Half of them are just asking the price. Can an automation answer those while we keep talking?
I keep seeing accounts where you comment a word and instantly get a DM with a link. I have my account connected but I cannot work out which trigger does that. Is it the DM trigger or the comment trigger?
Diego P. ·
Our price keyword automation is firing on messages that have nothing to do with price. One of them was somebody saying they appreciate the fast replies. I assume I picked the wrong mode but which one is right?
Ivan P. ·
Use one automation on the keyword, then branch with a condition step, and send each branch to its own flow with a start flow step. One entry point, three maintainable flows, instead of three automations fighting over the same keyword. The reason not to build three automations on…