Outcome. Every ticket carries a running count of how many times it has been escalated, so reporting can flag tickets bouncing between escalation tiers instead of being resolved on first escalation.
flowchart TD
A[escalated changes to true] --> B[Increment escalation_count by 1]

When to use it, when not to
- UseUse it on service teams that have a defined escalation signal on the ticket, a priority bump, a pipeline move to a Tier 2 or Escalated stage, or a dedicated checkbox an agent toggles.
- UseUse it as an input to a recurring-escalation report, distinguishing tickets that get escalated once and resolve from ones that ping back and forth between support tiers.
- SkipDo not use it if this portal has no consistent, single signal for a ticket just being escalated. Building the counter on an ambiguous or inconsistently used property will undercount silently. Fix the escalation signal first.
- SkipDo not confuse this with SLA breach tracking. Escalation and SLA breach are related but distinct. A ticket can escalate without ever breaching an SLA, and vice versa.
or the reporting and alerts pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





