The Guest Tag Added trigger fires when a tag is added to a guest's profile. This works whether the tag is added manually by a team member or automatically by another automation's "Add Tag" action.
When a tag is added to a guest, Hello Hotel checks if any automations are listening for that tag. If there's a match, the automation runs for that guest.
Add one or more tags you want to listen for. The dropdown shows your existing tags so you can select from them.
When you add multiple tags, choose how they're matched:
Any (default) — triggers when any one of the listed tags is added to a guest. Use this when you want the same automation to respond to multiple tags (e.g., "VIP" or "Returning Guest").
All — triggers only when a guest has every tag on the list. The automation fires when the last needed tag is added. Use this when you want to target a very specific segment (e.g., guests tagged both "VIP" and "Late Checkout Requested").
This is the one trigger that can be set off by another automation. If Automation A adds a tag to a guest, and Automation B is listening for that tag, Automation B will fire automatically.
To prevent infinite loops (where automations keep triggering each other), Hello Hotel limits chaining to 5 levels deep. If an automation chain reaches this limit, it stops.
A guest texts "wifi" → Automation A (Inbound Message trigger) adds the tag "WiFi Request"
Automation B (Guest Tag Added trigger, listening for "WiFi Request") sends the guest your WiFi password
VIP handling — when a guest is tagged "VIP" (manually or via a condition in another automation), trigger a special welcome message or alert your team
Workflow chaining — use tags to connect multiple automations into a sequence. One automation tags the guest, the next picks up from there.
Segment-based messaging — tag guests during their stay (e.g., "Spa Interest," "Early Checkout"), then trigger follow-up messages based on those tags
Tags are a powerful way to build modular automations. Instead of putting everything in one complex workflow, break it into pieces connected by tags.
Be thoughtful about tag names — they're the "API" between your automations. Use clear, descriptive names.
Remember the 5-level chain limit when designing tag-based automation sequences.
