## TL;DR
Routing reads fields, and enterprise tickets get misrouted when the field it trusts is wrong: the organisation's tier lives in the CRM but the helpdesk copy is stale, or topic keywords outrank account tier. Trace misrouted tickets through the rule order and find which rule claimed them and why.

```text
ticket routing misassigned enterprise tickets to tier 1: config error
```

## Use this when
- Enterprise tickets are repeatedly assigned to tier 1 or a general queue
- Routing rules exist but tier data may be synced poorly
- Misrouting delays SLAs and frustrates named accounts

## Not for this skill when
- Policy is tier-1 triage for all tickets, and these were handled within it
- Only one agent's manual assignments are wrong

## Steps
1. Collect 20 misrouted enterprise tickets with their field values at creation time. Verify: the evidence set is fixed before fields change
2. Walk each ticket through the routing rules in evaluation order. Verify: the rule that claimed each ticket is identified
3. Check the tier field's sync from CRM to helpdesk for those organisations. Verify: stale or missing tier values are confirmed or cleared
4. Reorder or repair the rules so verified account tier outranks keyword guesses, and backfill tier data. Verify: a test enterprise ticket routes straight to the enterprise queue
5. Add a misroute audit sampling enterprise tickets weekly for correct first assignment. Verify: routing quality is measured continuously, not by complaint

## Variant phrasings
### enterprise tickets routed to tier 1
A related phrasing for the same underlying problem.
### routing rule order wrong
A related phrasing for the same underlying problem.
### helpdesk tier field stale
A related phrasing for the same underlying problem.

Compatibility: Compatibility: helpdesk routing (Zendesk organisation fields and triggers, Intercom assignment rules, Service Cloud omni-channel), current versions.

## Why it happens
Routers evaluate in order and trust their fields completely, so misrouting is always legible: some rule fired on some value. Reading the rule order against creation-time values turns a complaint pattern into a specific rule and a specific stale field.

## Edge cases / pitfalls
- Creation-time values matter because organisations get edited after routing. Audit with snapshots or logs, not current field values.
- Keyword rules for topics like billing often outrank tier because they were written first. Rule order is policy; review it as such.
- A catch-all queue with fast human triage softens every routing bug. Staff it while the rules are repaired.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_7PK9D-coOXC0LLDwEcQrkA