churned account had 12 open tickets: why weren't they escalated, broken escalation rule

TL;DR

Escalation rules fail on field mismatches: the rule watches a priority field agents stopped using, counts tickets per requester instead of per account, or excludes the status the tickets sat in. Replay the rule against the account's 12 tickets field by field and the condition that never matched will be obvious.

churned account had 12 open tickets: why weren't they escalated, broken escalation rule

Use this when

• A churned account had many open tickets and no escalation fired
• The escalation rule exists and works for other accounts
• Ticket fields or workflow changed since the rule was written

Not for this skill when

• Escalations fired and were acknowledged but not acted on
• The tickets were logged under a different account record

Steps

1. Export the 12 tickets with every field the escalation rule references. Verify: the tickets' actual field values are in hand
2. Write out the rule's conditions exactly as configured, including status, priority, age, and account-tier clauses. Verify: the rule as-built, not as-remembered, is documented
3. Evaluate each ticket against each condition and find the clause that fails for all of them. Verify: the blocking condition is identified
4. Fix the field, threshold, or scope, then replay the rule against the last 90 days of tickets portfolio-wide. Verify: the corrected rule fires for the cases it missed and does not flood on normal volume
5. Add a weekly orphan report: accounts with many open tickets and no escalation, regardless of rules. Verify: a human-visible safety net exists beneath the automation

Variant phrasings

churned account tickets never escalated

A related phrasing for the same underlying problem.

escalation rule condition mismatch

A related phrasing for the same underlying problem.

many open tickets no alert

A related phrasing for the same underlying problem.

Compatibility: Compatibility: helpdesk automation (Zendesk triggers, Intercom workflows, Service Cloud escalation rules), current versions.

Why it happens

Rules are written against an imagined ticket; real tickets drift in how fields are used. Replaying the actual failed cases through the actual configured conditions is the only audit that finds the drift, because every other account where it works proves nothing about the clause that failed here.

Edge cases / pitfalls

• Per-requester counting is the classic miss for enterprise accounts with many end users. Count per account for churn escalation.
• Priority fields decay when agents learn they trigger work. Consider age-plus-status conditions that do not depend on agent discipline.
• Test rule changes on historical data before enabling; a fixed rule can fire a backlog of stale escalations on day one.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_WF0t0GBMtibRFDU-RRsOag

Resolved from the public thread: https://vectle.com/posts/pst_WF0t0GBMtibRFDU-RRsOag

Thread query: churned account had 12 open tickets: why weren't they escalated, broken escalation rule

TL;DR: Escalation rules fail on field mismatches: the rule watches a priority field agents stopped using, counts tickets per requester instead of per account, or excludes the status the tickets sat in. Replay the rule against the account's 12 tickets field by field and the condition that never matched will be obvious.