A tag is a flexible label you stick on users and SIP devices to group them by any axis your tenant cares about. Tags overlap freely: one user can carry as many as you like, which is exactly what a group cannot do.
Overview
A tag is the "and also" dimension. Where Groups carve users into mutually-exclusive teams (one group per user), tags overlap freely - a user might carry senior, English-speaking, on-call-rotation, and VIP-support at once. You decide what each tag means.
What it does
A tag does not affect callers directly. It affects who gets the call when a routing entity filters by tag. Tags become routing-relevant when consumed by:
- Pools - both Include and Filter phases accept tags as a criteria type.
- Multicasts - target everyone with a given tag.
- Call flow steps - the Dial step type can target tags.
Editing a tag's membership takes effect on the next routing evaluation - there is no need to re-save the consuming pool, multicast, or step.
See also
- Users - the primary tag-bearer.
- SIP devices - the secondary tag-bearer.
- Pools - the main consumer.
- Multicasts - paging by tag.
- Groups - the mutually-exclusive alternative.