How do you tag a contact based on the button they tapped?

Send buttons or quick replies, then branch on which one came back and add a tag on each branch. Two steps, and it turns every conversation into segmentation you can use later.

The reason this is worth doing on almost every flow: a tap is a stated preference, and it is the cheapest data you will ever collect. Someone who tapped "pricing" and someone who tapped "support" want different things next week, and if you did not tag them at the moment they told you, you cannot tell them apart.

The build:

1. Ask with quick replies, with two to four options. More than four and

people stop reading.

1. Condition on the reply, one branch per option.
2. Add tag on each branch, named after the interest rather than the button

text, so renaming the button later does not orphan the tag.

1. Continue the conversation on each branch.

Two things that keep this clean over time. Name tags for what they mean, not where they came from: interest-pricing rather than tapped-button-2. And keep the tag vocabulary small. A workspace with two hundred tags has no segmentation, it has a mess.

Once the tags exist they are audience conditions on other automations and segment rules for broadcasts, which is where the value actually shows up.