How do you route one keyword into three different flows?

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 the same keyword: only one answers a given message, so two of the three would never fire. Priority is not a router.

The shape that works:

1. Trigger: the keyword, once.
2. Condition: the thing that actually differs between the three paths. Tag,

custom field, business hours, or which channel the message arrived on.

1. Start flow on each branch, pointing at a separate published flow.

The reason to split into separate flows rather than one large graph is maintenance, not performance. A flow with three long branches is a flow nobody wants to edit, and the person editing it six months from now will be you. Three named flows show up in the list with their own titles and their own history.

Where to put the condition is the real decision. If the branches differ by who the contact is, condition on a tag or field. If they differ by when the message arrived, condition on business hours. If they differ by what the person wants, you do not have one keyword, you have three, and the cleaner answer is three specific keyword automations.