follow-up cadence for unresolved tickets

TL;DR

Unresolved tickets die from neglect, not complexity. Follow up on waiting-on-customer tickets after 2 business days, on engineering-blocked tickets weekly with a status ping, and escalate anything unresolved past 2 weeks. Each follow-up should add information or a clear next step, never just "checking in." The goal is zero tickets in limbo, every open ticket should have a named owner and a next action.

The query

follow-up cadence for unresolved tickets

Use this when

• Tickets keep going stale and dying silently
• You need a team rulebook for follow-up timing
• Agents ask "how long do I wait before bumping"
• You are building auto-follow-up rules in your ticketing tool

Not for

• First replies to new tickets
• Outage or incident status updates
• Sales or churn-save outreach sequences
• Closing tickets cleanly

Steps

1. Classify every open ticket by who it is waiting on

Waiting on customer, waiting on engineering, waiting on a third party, or waiting on you. You cannot schedule follow-ups without this.

Expected output: every open ticket has a waiter tag and a named owner.

2. Waiting on customer: bump at 2 business days, close at 7

First bump restates the single question they need to answer. Second bump at day 5 warns the ticket will close. Day 7: close with a note they can reopen anytime.

Expected output: no waiting-on-customer ticket sits unbumped past 2 business days.

3. Waiting on engineering: status ping weekly

Once a week, post a visible update on the customer ticket even if the update is "still with engineering, here is what they are looking at." Silence is what breeds angry follow-ups.

Expected output: the customer hears from you weekly even when nothing changed.

4. Waiting on a third party: ping twice, then offer the workaround

After two unanswered vendor pings, stop waiting and give the customer the best workaround or alternative path. Waiting past that point is your problem, not theirs.

Expected output: every third-party-blocked ticket has a workaround offered by day 10.

5. Escalate anything unresolved past 2 weeks

Two weeks open is a process failure, not a ticket. Escalate to a lead with a summary: what is blocked, what has been tried, what the customer was last told.

Expected output: zero tickets older than 2 weeks without a lead aware of them.

6. Make every follow-up carry information

Never send a bare "just checking in." Each bump restates the question, shares a status, or offers the workaround. The customer should learn something from every message you send.

Expected output: read any three follow-ups and each one contains a fact the customer did not have.

Variant phrasings

how often should support follow up on open tickets

The cadence above: 2 days for customer waits, weekly for engineering waits, escalate at 2 weeks. Adjust for your SLA tiers, P1s get daily pings.

support ticket follow-up best practices

Same rules, plus the meta-rule: the cadence is a backstop, not a schedule. If you have news, send it now, dont wait for the bump day.

when to close a stale support ticket

Day 7 for waiting-on-customer after two bumps. Engineering-blocked tickets never auto-close, they escalate instead.

Why it happens

Tickets go stale because following up feels like nagging and nobody owns the waiting state. The ticket looks open but nobody is thinking about it. A written cadence removes the decision: the clock decides, not the agent's guilt. Teams with a written cadence close unresolved tickets twice as fast, not because they work harder, but because nothing sits invisible.

Edge cases

• High-value accounts: tighten the cadence (daily bumps for customer waits, twice-weekly engineering pings) and put a lead on anything past 1 week.
• Customer says "dont rush me": respect it, but set a calendar reminder anyway. Silence from them does not mean the ticket should be silent on your board.
• Engineering says "no ETA": say that honestly to the customer weekly, and escalate internally. "No ETA" for 2 weeks is a management problem.
• Tickets that keep reopening: after the second reopen, treat it as a new ticket with a root-cause review, not another bump.

Provenance

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

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

Thread query: follow-up cadence for unresolved tickets

TL;DR: Unresolved tickets die from neglect, not complexity. Follow up on waiting-on-customer tickets after 2 business days, on engineering-blocked tickets weekly with a status ping, and escalate anything unresolved past 2 weeks. Each follow-up should add information or a clear next step, never just "checking in." The goal is zero tickets in limbo, every open ticket should have a named owner and a next action.