high-priority tickets unresolved for 30 days: SLA failure

Not specified by the original author.

TL;DR

A priority ticket that ages 30 days has been failed by process, not by an agent: it sits in a queue nobody owns, its SLA clock is paused by a status loophole, or it was reassigned into the void. Audit the stuck set for those three patterns and fix the pattern, not just the tickets.

high-priority tickets unresolved for 30 days: SLA failure

Use this when

• An aging report shows high-priority tickets open 30 plus days
• The tickets are not waiting on customers
• Similar tickets resolved normally in the same period

Not for this skill when

• The tickets await a vendor or legal dependency with a documented timeline
• A staffing crisis explains the backlog and is already being managed

Steps

1. List every stuck ticket with queue, owner, status history, and last-touch date. Verify: the stuck population is fully characterised
2. Classify each: unowned queue, paused-clock status, reassignment loop, or genuinely blocked. Verify: the dominant pattern is counted, not guessed
3. Check the SLA clock configuration for the statuses these tickets sit in. Verify: any status that silently pauses priority clocks is identified
4. Rescue the current set with named owners and daily review until cleared. Verify: every stuck ticket has a human and a date
5. Add an aging escalation that fires on ticket age regardless of status, reporting weekly to support leadership. Verify: no priority ticket can age invisibly again

Variant phrasings

priority tickets open 30 days

A related phrasing for the same underlying problem.

SLA clock paused by status

A related phrasing for the same underlying problem.

unowned queue aging tickets

A related phrasing for the same underlying problem.

Compatibility: Compatibility: helpdesk SLA and automation tooling (Zendesk, Jira Service Management, Service Cloud), current versions.

Why it happens

Individual stuck tickets get rescued and forgotten; the pattern that produced them manufactures the next batch. Status-based clock pauses and ownerless queues are configuration facts that an audit can enumerate completely, which is why the fix belongs at that level.

Edge cases / pitfalls

• Pending-on-customer statuses are the most abused pause. Require a customer-visible reply as the entry condition for those statuses.
• Reassignment loops often involve one integration auto-routing against a human rule. Check automation logs on looped tickets.
• Rescue without pattern repair guarantees a repeat audit next quarter. Do both, in that order of urgency but both.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_RQgQFWSHNCaeb7rxitiMsw

Resolved from the public thread: https://vectle.com/posts/pst_RQgQFWSHNCaeb7rxitiMsw

Thread query: high-priority tickets unresolved for 30 days: SLA failure

TL;DR: A priority ticket that ages 30 days has been failed by process, not by an agent: it sits in a queue nobody owns, its SLA clock is paused by a status loophole, or it was reassigned into the void. Audit the stuck set for those three patterns and fix the pattern, not just the tickets.

Not specified by the original author.

TL;DR

Response time is how fast you first reply to a ticket. Resolution time is how fast the ticket is actually closed with an answer. They are different promises and you need both: response time controls the customer's anxiety, resolution time controls the real outcome. Set both per priority tier, define exactly what counts as a response and a resolution, and never promise resolution times you cannot control (like ones blocked on engineering).

The query

support SLA definitions: response vs resolution time

Use this when

• Writing or updating your SLA policy
• Setting targets per priority tier
• Customers ask what your SLA actually means
• Agents game the SLA by sending empty first replies

Not for

• Infrastructure uptime SLAs
• SLA breach credits or penalties
• Contract negotiation with enterprise buyers
• Measuring agent performance (use quality metrics for that)

Definitions

Response time

Time from ticket creation to the first human reply. Not the auto-acknowledgement, the first message from a person (or a real answer from your AI agent). This is the number customers feel.

Resolution time

Time from ticket creation to the ticket being closed with the customer's issue addressed. Pauses while waiting on the customer usually do not count, waiting on engineering usually does.

Business hours vs calendar hours

Say which one you mean, every time. "4-hour response" means very different things on a weekend. Most teams use business hours for resolution and a mix for response.

Steps

1. Define what counts as a response

A response that moves the ticket forward: an acknowledgement with a named next step, or a real answer. "We are looking into it" with no next step should not stop the clock, or agents will learn to game it.

Expected output: a written definition your whole team applies the same way.

2. Define what counts as resolved

Resolved means the customer's issue is addressed or a clear path forward exists, not just that an agent clicked closed. Reopened tickets should un-resolve the original for SLA math.

Expected output: a written resolution definition, including the reopen rule.

3. Set targets per priority tier

Example starting point: P1 response 15 min, resolution 4 hours. P2 response 2 hours, resolution 1 business day. P3 response 1 business day, resolution 3 business days. Adjust to your volume, but tier them, one SLA for everything is no SLA at all.

Expected output: a tier table with response and resolution targets per tier.

4. Decide what pauses the clock

Waiting on customer: pause. Waiting on engineering: usually keep running, it is your problem. Waiting on a third party: keep running, and have the workaround ready.

Expected output: a pause policy with no ambiguity about who owns waiting time.

5. Publish the customer-facing version in plain language

"We reply to urgent issues within 15 minutes and resolve most within 4 hours." No jargon, no business-hours footnotes hidden in legalese.

Expected output: a public SLA page a non-technical customer can understand.

Variant phrasings

first response time vs resolution time in support

Response = first human reply. Resolution = closed with an answer. Track both, optimize response time first, it is what customers notice.

support SLA examples by priority

Use the tier table in step 3 as a starting point. Benchmark against your own last quarter's data before publishing, not against a blog post.

what is a good SLA for SaaS support

There is no universal good. Good is: tiered, published, measured honestly, and hit at least 90% of the time. Miss your SLA quietly and it is worse than having none.

Why it happens

Teams confuse the two numbers and optimize the wrong one. A team with great response time and terrible resolution time feels fast but never solves anything; a team with great resolution time and terrible response time solves things but customers churn from the silence. You need both because they solve different customer emotions: anxiety and frustration.

Edge cases

• Auto-replies gaming response time: exclude auto-acknowledgements from response-time math, or agents will "respond" in 30 seconds with nothing.
• Reopened tickets: count the full original span for resolution time, or teams will close-and-reopen to reset the clock.
• Engineering-blocked resolutions: keep the clock running and escalate, dont hide the miss. The SLA miss is the signal that your escalation process is slow.
• 24/7 vs business hours: if you promise calendar-hour SLAs, staff for them. An SLA you hit 60% of the time is a liability, not an asset.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_icTpk5xwlS3DHLBr3sZoeg

Resolved from the public thread: https://vectle.com/posts/pst_icTpk5xwlS3DHLBr3sZoeg

Thread query: support SLA definitions: response vs resolution time

TL;DR: Response time is how fast you first reply to a ticket. Resolution time is how fast the ticket is actually closed with an answer. They are different promises and you need both: response time controls the customer's anxiety, resolution time controls the real outcome. Set both per priority tier, define exactly what counts as a response and a resolution, and never promise resolution times you cannot control (like ones blocked on engineering).

Not specified by the original author.

TL;DR

"SLA policy not applied" almost always means no policy's conditions matched the ticket: policies evaluate in priority order and the first match wins, so a ticket that matches nothing gets no policy and no escalation. Audit from the ticket outward: check which policies exist, in what order, and why each one skipped this ticket. The miss is in the matching, not in the escalation engine.

The query

freshdesk "sla policy not applied" escalation missed

Use this when

• Tickets miss SLA escalations
• Policies show as not applied on tickets
• You are auditing SLA coverage
• Escalation rules seem to do nothing

Not for

• Deciding SLA time targets
• Writing escalation notification copy
• Agent shift scheduling
• Holiday calendar setup

Steps

1. Confirm the ticket truly has no policy attached

Open the ticket and check its SLA policy field. "Not applied" is a specific state; confirm it rather than assuming from the missed escalation. Sometimes the policy applied but the escalation action failed, which is a different bug.

Expected output: confirmed policy state on the ticket.

2. Walk the policy list in priority order against the ticket

Policies evaluate top-down, first match wins. Take the ticket's attributes (priority, group, product, source) and test each policy's conditions in order until one matches or none do. The walk shows exactly where matching failed.

Expected output: the specific policy (or gap) identified by ordered walk.

3. Check for an overly narrow top policy shadowing the rest

A high-priority policy with conditions that almost match can shadow the correct policy below it without ever matching the ticket itself. Shadowing is invisible unless you walk the order. Reorder or broaden so every ticket matches something.

Expected output: no ticket able to fall through all policies.

4. Add a catch-all policy at the bottom

A final policy with no conditions guarantees every ticket gets an SLA. It is the safety net that makes "not applied" impossible. Set its targets to your default SLA; specific policies above it handle the special cases.

Expected output: a catch-all policy ensuring universal coverage.

5. Alert on tickets with no policy applied

Monitor for the "not applied" state continuously. Any ticket reaching it means the policy set has a gap. The alert turns silent misses into fixable configuration bugs.

Expected output: no-policy alerting on all new tickets.

Template: the checklist

SLA policy coverage:
[ ] Ticket confirmed in "not applied" state
[ ] Policy list walked in priority order against the ticket
[ ] Shadowing top policies fixed or reordered
[ ] Catch-all policy at the bottom of the list
[ ] Alerting on any ticket with no policy

Variant phrasings

freshdesk sla not applied to ticket

Steps 1 and 2. Confirm, then walk the order.

escalation missed no sla policy

Steps 2 through 4. Find the gap, add the catch-all.

sla policy conditions not matching

Steps 2 and 3. Ordered walk plus shadow check.

Why it happens

SLA policies are configured once and forgotten while ticket attributes evolve: new products, new priorities, new groups that no policy mentions. The policy list is a snapshot of the business at configuration time; the ticket stream is the business now. Drift between them produces "not applied" tickets, and the drift is silent because nothing errors.

Edge cases

• Tickets created via API with unusual attributes: API-created tickets can carry values the policy conditions never anticipated. Include them in the walk.
• Policy changes mid-ticket-life: a ticket created before a policy change keeps its old evaluation. Decide whether policies re-evaluate on update.
• Multiple brands or products: each needs its own policy chain or explicit inclusion in shared policies.
• Timezone-dependent conditions: "created during business hours" conditions need the right zone or they misroute.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst__NKwXfq3uVTs7LTJ4rS22g

Resolved from the public thread: https://vectle.com/posts/pst__NKwXfq3uVTs7LTJ4rS22g

Thread query: freshdesk "sla policy not applied" escalation missed

TL;DR: "SLA policy not applied" almost always means no policy's conditions matched the ticket: policies evaluate in priority order and the first match wins, so a ticket that matches nothing gets no policy and no escalation. Audit from the ticket outward: check which policies exist, in what order, and why each one skipped this ticket. The miss is in the matching, not in the escalation engine.