tag automations for stage changes with multiple services

​@MoonlitPMU I’d use User Fields for this instead of tags.

For example, create an User Field called ‘status’ and change it’s value to the most current value (

Service A Unqualified,  Service A Qualified Plus, etc).

You can keep the tags if you want to keep the entire history of the stages that person went through.

Hope this helps!

Hi there! So my dav figured out a way to make it work with tags..

If a cell in Sheets reads a tag as “true” it copies in the name of the column which is the tag name. Seems liker it will work

The reason I like tags is it’s easy to manually change in live chat or on the contact. I dont want the stage history tho, itll be way too many tags. ideally ill have an automation to review tag for Service A Qualified once Service A Qualified Plus is tagged and then send the update to a Sheet.

What benefit does having user fields give over tags in your suggestion?

The main issue tho is still how to best report in sheets when the look up doesnt cross reference multiple cells

i.e. someone could be in the sheet on a row for qualified with service A but then end up converted for service B. i would not want this to affect the status for the row on service A

With that many services and stages, I honestly wouldn’t manage this with tags alone if you can avoid it.

The cleaner setup is usually:

one custom field per service
So instead of stacking tags like:

• Service A Qualified

• Service A Qualified Plus

• Service A Converted

you’d have a field like:

• Service A Stage = Unqualified / Qualified / Qualified Plus / Booked / Converted

Same for Service B, Service C, etc.

Why this works better:

• it always shows the current stage for that service

• you don’t have to remove old stage tags every time

• it’s much easier to update manually or with automations

• reporting to Sheets becomes cleaner too

Then if you still want tags, use them only for:

• important actions

• automation triggers

• temporary flags

For your case, I’d do this:

• keep one stage field per service

• update that field whenever the person moves stages

• let Service A, B, and C each keep their own stage separately

• only use tags when you specifically need to trigger something

That way someone can be:

• Service A = Qualified Plus

• Service B = Unqualified

• Service C = Converted

without creating a giant tag mess.

So the best setup is really: use custom fields for stage tracking, not tags for every stage.