How One Hospital Cut Support Tickets by 32% in Two Months
When the same three questions kept flooding the IT desk every shift, a mid‑size health system decided to stop treating them as isolated incidents. By turning tip sheets into a searchable knowledge hub and tracking unanswered queries, they slashed tickets by a third in just 60 days.
The Moment It All Went Too Far
It was 2 a.m. on a Tuesday. The charge nurse on the med‑surg floor, Maria, stared at her phone as the pager kept buzzing. “Why does the Epic Order‑Set keep resetting?” she muttered, then hit the call button for the IT help desk. On the other end, Jake, the application analyst, recognized the problem immediately—this was the third call about the same issue that night.
Maria’s voice was weary. “It’s the same thing we saw yesterday, and the day before. Can you just fix it for good?”
Jake sighed. “I’ll send you the tip sheet again.”
He opened a PDF that lived in a SharePoint folder dated 2018, scrolled to the relevant page, attached it, and hung up. The next shift heard the same question, the same attachment, the same frustration. By the end of the week the help desk logged 84 tickets that were essentially repeats of three core issues: Epic order‑set resets, Pyxis lock‑outs, and Teams channel notifications.
The Problem: Repeated Requests Ate Up Time and Morale
Across the 420‑bed system, the IT support team was drowning in what should have been “quick‑win” calls. According to a 2022 HIMSS survey, hospitals spend on average 23 % of their IT staff’s time on repeat support requests that could be resolved with existing documentation1.
At our hospital, the ticketing system showed:
- Average handle time: 12 minutes per ticket (including verification and follow‑up)
- Repeat rate: 41 % of tickets were exact duplicates of a prior request within the last 30 days
- Staff impact: Roughly 340 hours per month of analyst and nurse time spent on the same three issues
Those numbers translate into dollars. The AHA reports that the average cost of a support ticket in a mid‑size hospital hovers around $45 when you factor in labor, lost productivity, and indirect costs2. That means the repeat tickets alone were costing the organization $15,300 per month – money that could have been redirected to patient‑care initiatives.
But the hidden cost was even worse: morale. Nurses complained that “the same thing keeps happening, and nobody knows why.” Junior staff felt they were walking a tightrope between caring for patients and hunting down a missing workflow doc that lived somewhere in a labyrinth of folders.
What We Did: Turn Documentation Into a Living Knowledge Base
The leadership team convened a cross‑functional task force: a charge nurse, an application analyst, a clinical educator, and the CIO. Their charter was simple – eliminate repeat tickets.
1. Harvest Existing Content
First, they pulled every tip sheet, SOP, and quick‑reference guide that lived on the network – from the “binder behind the Pyxis” to the “Teams channel nobody reads.” They ended up with 274 PDFs and Word docs, many of which were outdated or duplicated.
2. Clean, Tag, and Upload
A clinical educator and two nurse preceptors spent two weeks reviewing each file, stripping out stale steps (e.g., references to a now‑retired version of Epic), and tagging the content with metadata: module, role, system, keyword. The result was a central repository of 202 current, searchable resources.
3. Deploy AI‑Powered Search
Instead of forcing staff to comb through folders, the team rolled out an AI search engine that indexes the hospital’s own documents. The engine respects HIPAA – it uses AES‑256 encryption, auto‑redacts PHI, and runs inside the hospital’s firewall.
When Maria typed “Epic order‑set reset” into the search bar, the top result was the exact tip sheet she needed, highlighted with a “Most relevant for Charge Nurse – 2‑minute fix” banner. No more digging through a 2019 SharePoint sub‑folder.
4. Log Every Interaction
Every time a support ticket was closed, the analyst logged the steps taken, the documents referenced, and the outcome. The system automatically flagged any ticket that didn’t have an associated knowledge article. Those “unanswered questions” went to a weekly review board.
5. Close Knowledge Gaps
During the first two weeks, the board identified seven unanswered questions – everything from a new medication barcode mismatch to a rare Cerner interface error. The team assigned owners, built new tip sheets, and uploaded them within 48 hours. The cycle repeated until the backlog of gaps was under five.
The Outcome: A 32 % Drop in Tickets in 60 Days
Six weeks after the new knowledge hub went live, the metrics looked dramatically different.
- Ticket volume: 321 tickets total – a 32 % reduction from the baseline of 474 tickets in the preceding 60‑day period.
- Repeat rate: Fell to 18 %, meaning most calls were truly new issues.
- Average handle time: Shrunk to 8 minutes per ticket, a 33 % efficiency gain.
- Time saved: Roughly 210 hours of analyst and nurse time reclaimed in two months.
- Cost avoidance: Approximately $9,450 saved on support‑ticket labor alone.
Beyond the numbers, the qualitative shift was palpable. The charge nurses reported fewer “late‑night scrambles,” and the help‑desk staff finally felt they were solving problems instead of playing whack‑a‑mole.
A senior director of clinical operations summed it up: “We used to think a tip sheet was a nice‑to‑have. Now it’s the first line of defense. When the knowledge is right at the point of care, the phone stops ringing.”
Lessons Learned (and What Might Trip You Up)
- Don’t just dump documents. The cleaning and tagging phase ate up most of the effort, but it paid off. Without metadata, the AI search was no better than Google on a messy SharePoint.
- Make logging mandatory. The habit of associating every ticket with a knowledge article created the data set that later highlighted gaps.
- Involve front‑line staff early. The tip sheets that mattered were the ones nurses wrote for nurses – jargon‑free, step‑by‑step, with screenshots taken on the actual workstations.
- Expect resistance. Some senior analysts initially feared the AI would replace them. Show them the data – the tool freed them to tackle complex integrations, not to be redundant.
- Keep the loop open. Unanswered‑question tracking turned a static library into a living process. If you stop reviewing gaps, the benefit erodes.
Where Do We Go From Here?
The team is now expanding the AI search to include policy documents and regulatory updates, hoping to shave off the “I need to ask legal” calls that still bubble up. They’re also piloting a mobile‑first version so that a nurse on a rapid response can access the same tip sheet without trudging back to a workstation.
What started as a frantic midnight call turned into a systematic overhaul of how knowledge lives in the hospital. The result? Fewer tickets, faster resolutions, and a culture that trusts the right information will be at their fingertips when they need it.
If your organization is wrestling with the same repeat‑ticket nightmare, think of the knowledge base not as a project but as an ongoing service to the front line. The payoff isn’t just a number on a dashboard; it’s the confidence of a nurse who can fix an issue without waiting for a call back.
Footnotes
-
HIMSS. Knowledge Management in Healthcare: Impact on Operational Efficiency, 2022. https://www.himss.org/resources/knowledge-management-healthcare ↩
-
American Hospital Association. Hospital Statistics 2023. https://www.aha.org/statistics/overview-hospital-statistics ↩