Close them or kill them—but don’t let them rot.

If you’ve ever run a time entry report and thought,
“We had how many tickets open last month?”
…you’re not alone.

In many TSPs, open tickets accumulate like junk in a server closet. At first, it’s just a few. But give it six months, and you’re sitting on hundreds of open tickets—many of them long resolved, forgotten, or worse, incorrectly sitting in “Waiting on Customer” since the Nixon administration.

Let’s talk about why this happens, why it’s a problem, and how to fix it without blowing up your service team.

Why Open Ticket Bloat Happens

• No one owns the cleanup.
  Techs move on to the next fire, and managers are too busy to babysit status columns.

• Workflows aren’t chasing stale tickets.
  If automation isn’t poking old tickets, they just sit.

• Fear of closing “too soon.”
  Some techs leave tickets open “just in case” the client replies again.

• No status discipline.
  If “In Progress” is used for everything, there’s no way to track what’s actually happening.

• Client confusion.
  Clients think the issue’s resolved, but never hit “we’re good” — so the ticket stays open forever.

Why It’s a Real Problem

📊 Garbage Data

Reporting becomes useless when 300 tickets are open but 75% of them are dead weight. Your team looks busier than they are, your dashboards lie, and any SLA or utilization numbers get skewed.

📬 Missed Communication

When everything looks “In Progress,” the truly urgent tickets get buried. Escalations are missed, responses are delayed, and clients get frustrated.

🧾 Billing Issues

Open tickets with unapproved or unposted time entries lead to missed invoicing or billing delays. Worse, you might accidentally close the billing period with unresolved charges still sitting on the board.

What You Should Be Doing

✅ 1. Define a Lifecycle for Every Status

Statuses should be active or closed—no limbo.
Set expectations:

• “Waiting on Customer” = follow up for X days → then close

• “In Progress” = updated every X hours

• “New” = auto-escalate if untouched after X hours

✅ 2. Use Workflow Rules to Chase Stale Tickets

Examples:

• Any ticket in “Waiting on Parts/Repair” for X days > Notify the process owner

• Any ticket untouched in X + days → notify manager or escalate

✅ 3. Implement Auto-Close Policies

Once a ticket hits a final state (e.g., Resolved or Waiting on Customer), set a timer.
Auto-close after X days if no client response.
Bonus: send a “We’re closing this ticket unless you respond” email first.

✅ 4. Educate Your Clients

Train your users that closing a ticket doesn’t mean you’re gone forever. If they reply to a closed ticket, PSA reopens it (or creates a new one—your choice). No service is lost. They just stop seeing that old ticket hanging around.

✅ 5. Audit Monthly

Every 30 days, pull a list of tickets over 30+ days old and review with the team. If it’s dead, close it. If it’s alive, update it.

Wrap-Up

We use X instead of hardcoded numbers here—because there’s no one-size-fits-all. Your ticket lifecycle should be constructed around your internal SLAs, external client expectations, and operational policies. What works for a 5-person TSP isn’t going to cut it for a 50-person service desk with a 24/7 NOC.

One thing doesn’t change: metric reporting will always lie if your service boards aren’t actively maintained—by humans, workflows, or both. Garbage in, garbage out.

Open tickets aren’t just digital clutter—they lead to false utilization, missed revenue, and confused clients. If your ConnectWise dashboard looks more like a graveyard than a living system, it’s time to clean house.

Start small. Automate what you can. Close tickets with confidence.
Because a clean board isn’t just prettier—it’s smarter, more profitable, and way less stressful.