SLA-Aware Triage Scoring

also known as SLA-Deadline-Aware Triage Scoring, Deadline-Aware Ticket Prioritisation, Business-Impact Triage Score

Order the work queue by a single fused score that blends each ticket's time-to-SLA-breach, the requester's entitlement tier, and sentiment trajectory, and surface items predicted to breach before they do.

Context

A support or operations team runs a shared queue under contractual service-level agreements that promise a response or resolution within a fixed window per account tier. Tickets arrive faster than they can be worked, so the order in which an agent picks the next item decides which commitments hold and which slip. A first-in-first-out queue ignores deadlines and tier; ordering by the requester's stated urgency is gameable, since every requester marks their own ticket urgent.

Problem

No single field on a ticket captures its true priority. Time-to-breach matters, but a distant deadline on a top-tier account can still outrank a near deadline on a free-tier one, and a customer whose tone is deteriorating may need attention before either. Sorting by any one of these axes alone mis-orders the queue, and the breach risk is only visible once the deadline is already close, which is too late to act. The queue needs one comparable score that fuses the axes and looks ahead to predicted breaches.

Forces

A deadline-only sort starves high-value accounts whose breach window is further out; an entitlement-only sort lets cheap, urgent tickets breach unattended.
Stated urgency is self-reported and gameable, so it cannot be the ordering key, yet the genuine signal it sometimes carries should not be discarded entirely.
Acting on a breach only once the deadline is near leaves no slack to work the ticket, so the score must predict the breach early enough to matter.
A fused score is only as trustworthy as its weights; opaque weighting makes the ordering impossible to audit when a commitment slips.

Example

A support queue holds two open tickets. One is a free-tier user whose SLA breaches in twenty minutes; the other is an enterprise account whose SLA breaches in two hours but whose last three messages have turned sharply angry. A pure deadline sort works the free-tier ticket first; the fused score weights the enterprise account's tier and souring sentiment high enough to surface it now, while a breach alert still flags the free-tier ticket so neither is forgotten.

Diagram

flowchart TD T[Open tickets] --> C[SLA clock: time to breach] T --> E[Entitlement tier lookup] T --> S[Sentiment trajectory] C --> F[Fused triage scorer] E --> F S --> F F --> Q[Queue sorted by fused score] T --> P[Breach predictor] P -->|predicted breach| A[Early-alert lane] A --> Q

Solution

Therefore:

Define a scoring function over each open ticket. Read its SLA clock to compute time remaining to breach, look up the requester's contractual entitlement or account tier, and estimate a sentiment trajectory from the conversation so far. Normalise each axis and combine them with explicit, reviewable weights into one fused triage score; sort the queue by that score so the next item an agent picks is the one with the most at stake. In parallel, run a breach predictor that compares each ticket's expected time-to-completion against its deadline and emits an early alert for those on track to breach, so they can be expedited or escalated before the window closes rather than after. Keep the weights and the per-ticket score contributions visible so a slipped commitment can be traced to the inputs that ranked it.

What it gives you

One comparable number replaces ad-hoc per-axis sorts, so the next-picked ticket reflects deadline, contract value, and customer state together.
Early breach alerts convert deadline slips from after-the-fact incidents into items expedited while slack remains.
Explicit weights make the ordering auditable: a slipped commitment can be traced to the score inputs that ranked it.

What it costs you

Mis-set weights systematically starve one axis — for example a low sentiment weight that lets a deteriorating top-tier account sit behind routine work.
A wrong breach prediction either floods the alert lane with false positives that get ignored or misses a real breach by under-estimating completion time.
Sentiment trajectory estimated from text is noisy and can be gamed or misread, skewing the fused score.

What this pattern forbids. An agent must not pull the next ticket by arrival order or self-reported urgency alone; the queue ordering is read only from the fused triage score, and breach-predicted tickets cannot be left in the normal lane.

And the patterns that stand alongside it, or against it —

alternative-toComplexity-Based Routing★— Estimate a request's difficulty up front and bind it to the cheapest model tier that can answer well, using an explicit complexity classifier as the routing key.
alternative-toCost-Aware Action Delegation★— Classify every agent action by risk/cost and route each tier to a different approval policy, bounding the autonomy surface per-action instead of by one global flag.
complementsMandatory Red-Flag Escalation★★— Maintain a deterministic set of high-risk triggers so that on any match the agent immediately aborts its workflow and hands off to a human, without weighing whether to escalate.
complementsConversation Handoff to Human★★— Transfer the entire conversation thread from agent to human operator, with state transfer and return primitive.