Routing rules run the moment a conversation is created, before anyone has looked at it, so work arrives where it belongs.
How a rule is built
A rule is a set of conditions and the actions to take when they all match.
Conditions can test:
- Channel — live chat or email.
- Priority
- Contact tag — a tag on the customer's contact record.
- Keyword — matched against the customer's first message.
All conditions on a rule must match. Rules are evaluated in order and the first match wins, so put your most specific rule at the top.
What a rule can do
A matching rule assigns the conversation and can set its priority. You can assign it to one teammate, or choose Round robin (available teammates).
With round robin, each new conversation goes to the available teammate who has gone longest without one. Anyone who has set themselves away (account menu → Set yourself away) and anyone with the Viewer role is skipped. If everyone is away, the conversation stays unassigned and your usual team alerts still go out. A rule with no conditions applies round robin to every new conversation.
A fixed assignee is verified as a member of your workspace when the rule runs — if that person has since been removed, the rule does not misfire.
Shown with our demo workspace.
Ordering matters
Because the first match wins, a broad catch-all rule at the top will swallow everything below it. If a rule seems not to fire, check what sits above it before checking the rule itself.
Rules versus workflows
Routing rules are deliberately narrow: they answer "who should own this". For anything richer — tagging, auto-replies, enrolling someone in a follow-up sequence, acting on replies and resolutions rather than only on creation — use Workflows, which run on more triggers and can take an ordered list of actions.
Who can change them
Routing rules are owner and admin only, and changes are recorded in the audit log.
