Tag-triggered automation: five flows that start when a customer gets or loses a tag

A tag-triggered automation is a flow that starts when a customer gets or loses a tag. An agent tags a chat vip, and a follow-up goes out and the right team is assigned. A lead moves to stage:qualified, and the old stage tag disappears and sales is notified. A customer loses consent:marketing, and every nurture tag comes off with it. In MonoChat you build these with two event nodes, Customer Tag Added and Customer Tag Removed, released in version 3.8.41.

This guide shows how the trigger behaves, then gives five recipes you can rebuild in a few minutes, with the messages they send.

Why start a flow from a tag

Most automations start from something the customer does: a new message, a new conversation, a payment. Tags are different. They record a decision someone made, often an agent who just read the chat and knows something no keyword rule could guess: this caller is a wholesale buyer, this lead is ready for a quote, this complaint needs a manager.

Until now that decision stopped at the label. The agent still had to remember what comes next. A tag trigger turns the label into the next step, so the knowledge of one agent becomes a process the whole team follows.

If your tags are not tidy yet, start with our guide to segmenting customers with tags. A short scheme with one prefix per type (interest:, stage:, consent:) is what makes the recipes below reliable.

How the trigger works in MonoChat

Add Customer Tag Added or Customer Tag Removed from the customer events in the flow designer. The rules, as the help center describes them:

Rule	What it means for your flow
Tags listed in the node	The node listens only for those tags, separated by commas. Leave it empty and any tag starts it.
Who can change the tag	Added: an agent, a flow, a bulk message or an ad referral. Removed: an agent or the Remove Customer Tags node.
No change, no run	Adding a tag the customer already has, or removing one they do not have, starts nothing.
One run per change	When several tags change at once, one run starts and carries every tag that changed.
No self-trigger	A flow does not react to a tag change made by its own node.

Placed at the start, the node starts a new run. Placed further down a flow, it makes that run wait until the tag changes, so a flow can, for example, send a quote and then continue only when an agent adds stage:won.

The nodes you will combine it with:

• Set Customer Tag adds one tag, and Remove Customer Tags removes several, separated by commas.
• If with the Customer Tag condition checks whether the customer has any of the listed tags (includes) or none of them (not-includes).
• Assign Session, Send Message, Send Template Message and Wait.
• Set Flow Variable with Increase by, plus the Flow Variable Value condition, for counters.

Recipe 1: VIP follow-up

Goal: when an agent marks a customer as a VIP, a senior agent takes over and the customer hears from you the same day.

1. Customer Tag Added, listening for vip.
2. Assign Session to your senior team or account manager.
3. Send Message while the customer service window is open:

Hi Sara, thank you for choosing us again. From today Omar is your personal
contact here. You can reach him in this chat for orders, changes or anything else.

4. Optionally Wait two days, then send a short check-in.

Meta’s rule decides the message type: a 24-hour customer service window opens when the customer messages you, and once it closes you can only send an approved template. If the tag is often added long after the last chat, use Send Template Message with a utility template instead.

Recipe 2: Lead stage changes

Goal: a customer is always in exactly one stage, and each stage change does its own job.

Use one flow per stage you care about. For stage:qualified:

1. Customer Tag Added, listening for stage:qualified.
2. Remove Customer Tags: stage:new, stage:contacted.
3. Assign Session to the sales team.
4. Send Message:

Thanks, Daniel. Based on what you told us, our sales team will prepare
an offer for the 40-seat plan. Liam will send it here by tomorrow noon.

The removal in step 2 does not restart this flow, but it can start another flow that listens for the removal of stage:new. That is useful, for example to stop a welcome series, but it is also how loops start: flow A adds a tag that starts flow B, and flow B removes the tag flow A watches. Draw your stage flows on paper first and give each tag one owner.

For lead capture itself, see WhatsApp lead generation.

Recipe 3: Hand the chat to the right team

Goal: a bot or an agent recognises the topic, tags it, and the chat lands with the right people without anyone forwarding it by hand.

1. Customer Tag Added, listening for team:wholesale, team:returns, team:billing.
2. One If node per team with the Customer Tag condition, for example includes team:wholesale; its “no” branch leads to the next If.
3. Assign Session to the matching team on each branch.
4. Send Message to set expectations:

You're now with our wholesale team. They answer Monday to Friday, 9:00-18:00,
and usually reply within an hour.

The tag stays on the customer after the conversation, so next time you can filter the inbox or a broadcast by it. For how teams and workloads are split, read routing WhatsApp conversations to workgroups; for passing a chat from an AI agent to a person, read AI-to-human handoff.

Recipe 4: Stop a nurture sequence when a tag is removed

Goal: a sequence runs only while the customer still belongs in it, and it stops the moment that changes: they bought, they asked to stop, or an agent decided it no longer fits.

The sequence flow:

1. Customer Tag Added, listening for nurture:course.
2. Wait 2 days.
3. If with Customer Tag includes nurture:course. Yes: Send Template Message with the next lesson. No: end.
4. Wait 3 days, then the same check before the next template.

The check before each message is what stops the sequence: when the tag is gone, the next step finds nothing to send.

The clean-up flow:

1. Customer Tag Removed, listening for consent:marketing.
2. Remove Customer Tags: nurture:course, nurture:webinar, nurture:winback.

One opt-out now takes the customer out of every sequence. WhatsApp’s Business Messaging Policy requires opt-in permission before you message people and that you respect every request to block, discontinue or opt out, so this is a flow worth having before you start any sequence. Our guides to WhatsApp opt-in and drip campaigns cover the consent wording and how to pace the messages.

Recipe 5: A retry counter that hands over after three tries

Goal: when a tag asks the customer for something, the bot asks a limited number of times, then gives the chat to a person instead of looping.

Say an agent adds docs:needed when a customer must send a photo of their ID:

1. Customer Tag Added, listening for docs:needed.
2. Set Flow Variable: attempts, Increase by 1. A variable that does not exist yet counts as 0, so the first pass makes it 1.
3. Question Answer: “Please send a clear photo of the front of your ID.”
4. If the message type is an image: Remove Customer Tags docs:needed, Set Customer Tag docs:received, thank the customer.
5. Otherwise, If with Flow Variable Value: attempts Greater Than or Equal 3. Yes: Assign Session to a person and Set Customer Tag docs:stuck. No: back to step 2.

Thanks, that photo didn't come through clearly. Could you try once more
in good light, with all four corners of the card visible?

The counter lives in the run, so every new docs:needed starts again from zero. If an increase fails, for example because the variable is not a number, the node takes its On Fail output and leaves the variable as it was.

Mistakes to avoid

• Free-form tags. VIP, vip and vip-customer are three different triggers. Fix the spelling before you build.
• Two flows that feed each other. A flow ignores its own changes, not those of other flows. Every tag should have one flow that reacts to it.
• Assuming the window is open. A tag can be added days after the last message. Plan a template for that case.
• Sequences without a check. Without the Customer Tag condition before each message, removing the tag stops nothing.
• Tags that replace consent. A tag records consent; it never creates it.

When to use a tag, a webhook or a timer

Tags fit decisions made inside MonoChat: by an agent, a bot, an ad or a bulk message. When the decision happens in another system, such as a paid order in your store, start the flow from a webhook instead. When nothing happens and that is the signal, use the timeouts in our guide to following up when a customer doesn’t reply.

To try the recipes, create a free account at app.monochat.ai, open Flows and start with Recipe 3: it is the one most teams feel the next morning.

Sources

• WhatsApp Business Messaging Policy (whatsappbusiness.com) (opened 2 November 2026)
• Meta for Developers: Send messages and the customer service window (opened 2 November 2026)
• MonoChat help center: Flows (opened 2 November 2026)
• MonoChat changelog: Version 3.8.41 (opened 2 November 2026)