How are you keeping agents on top of aging cases? Looking for tools, views, and AI ideas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hey all,
Looking for some collective wisdom from other CSM/ITSM admins and support leaders. We've been seeing a recurring pattern that I'd love to hear how others are solving:
The problem
Customers are increasingly reporting that Support hasn't responded in X days, or they're having to ping us multiple times for an update on an open case. When we dig in, it's usually a mix of agent follow-through and the fact that our tooling doesn't make staying on top of cases easy. Manager coaching helps in the short term, but it doesn't scale, and we keep ending up in the same loop.
What we think is contributing
The out-of-the-box ServiceNow case states (New, Open, Awaiting Info, Awaiting Vendor, Resolved, Closed, etc.) are too blunt to surface "this case has gone quiet and needs a nudge." Default list views don't do a great job prioritizing aging cases against newer ones, especially when an agent has 30+ open at any given time. Time-in-state and SLA breach indicators exist, but they don't always reflect customer-perceived staleness, for example, a case sitting in "Awaiting Info" for 10 days because the agent never followed up. Coaching the behavior helps individual agents, but turnover, workload spikes, and competing priorities make it hard to sustain.
What we're considering
A custom list view or dashboard that surfaces cases by "days since last customer-facing update" rather than just state or priority. A scheduled job or notification that pings the agent (and/or manager) when a case crosses a staleness threshold. AI-assisted approaches: an agent that scans open cases daily, flags ones that look neglected, and either drafts a follow-up or surfaces them to the human. Browser extensions or UI customizations to reorder agent views based on customer-impact signals.
What I'd love to hear from you
How is your team measuring and surfacing case staleness beyond standard SLA fields? Are you using Now Assist, custom AI agents, or third-party tools to detect and act on neglected cases? Have you built custom states, list views, or dashboards that meaningfully changed agent behavior? Any workflow or notification patterns that worked, or didn't? If you tried AI for this and it didn't pan out, what got in the way?
Trying to avoid the "just coach harder" answer because it isn't scaling. Open to anything, no idea is too small. Thanks in advance.
- Labels:
-
Case Management
