Story

He Stopped Waiting for IT Three Weeks Ago

By Felix Maru · November 18, 2026 · 7 min read

The ticket had been open for twenty-three days when I found it.

That is not unusual by itself. Tickets slip sometimes. Requests get buried, priorities shift, things fall through the cracks. But what caught me during that first-of-the-month queue audit was not the age. It was the silence. No follow-up from the user. No duplicate ticket. No escalation to a manager. Just a request, sitting there unread, assigned to a queue that apparently nobody had opened since it was submitted.

Tom, from the operations team, had written in on October 9th: "Hi, I need read access to the Q4-Client folder on SharePoint for the Carter account. Working on deliverables with the team and can't pull up the files. Thanks."

Simple request. Clear context. Reasonable ask. Completely unactioned.

I opened the assignment trail. The ticket had been routed to a queue called IT-Ops and had not moved since.

The Queue That Nobody Was Watching

The IT-Ops queue was an email alias we had set up two years earlier to catch general requests from the operations side of the business. It pointed to a shared mailbox owned by three people on the IT team. Straightforward setup, one that had worked fine for a long time.

In September, one of those three people left. The offboarding process was followed correctly: account deprovisioned, licenses reassigned, files transferred to their manager, access revoked. All the boxes checked. What nobody thought to verify was what that account owned rather than what it accessed.

It had been the mailbox's primary licensed owner. When the account was deprovisioned, the mailbox lost its Exchange license. It did not bounce incoming messages. It did not generate delivery failure notices. It did not send any alert to anyone. It simply became inaccessible. Emails routed into it and disappeared into a folder that nobody could open.

Tickets were not failing. They were delivering. They just had nowhere to go.

I queried the IT-Ops queue for the previous 90 days. There were seven tickets in a similar state. The oldest was thirty-one days old. Tom's was not the first.

The Phone Call

I called Tom the same morning. He picked up on the second ring.

When I explained who I was and why I was calling, there was a brief pause on the line. The kind of pause that tells you the person is recalibrating, reaching back a few weeks to remember something they had already mentally filed away.

"The SharePoint thing? Yeah, I figured nobody got it. I ended up having my manager share the files with me directly. We're basically wrapping up the Carter project now anyway."

I told him what had happened. The queue alias, the deprovisioned account, the unlicensed mailbox, tickets routing into an inaccessible dead end. I told him none of it was on him. The system had failed, not his request.

"These things happen," he said. He said it politely, without edge. He said it the way people say it when they have already done the work of not being angry about something, when the frustration has been processed, converted into adjusted expectations, and filed.

That phrase is worth sitting with for a moment. "These things happen" is not grace. It is accommodation. It is what a user says when they have downgraded their model of what IT support is capable of, decided that the adjustment is permanent, and moved on. Tom was not angry. He had adapted. And in a support context, that is harder to come back from than anger.

Anger means someone still believes you can help them and wants you to. Calm adaptation means they have already stopped counting on you for this category of problem.

The Other Six

I worked through the rest of the queue audit that morning and called every user with a stranded ticket.

Five were small delays with no lasting consequences: a printer PIN reset someone had already figured out through a colleague, a question about shared calendar permissions that had been answered informally, a request for a software license that the user had borrowed from a teammate in the interim. I closed each of those with a full explanation, an apology, and confirmation that the fix was done on my end.

The sixth was different. A user in the accounts team had submitted a request for dashboard access three weeks before an internal audit. The audit had run. She had spent two days pulling numbers manually from raw spreadsheets because the access she needed never arrived.

That call took longer. I did not explain or minimize. I told her what had happened, got the access set up while we were still on the phone, and asked whether anything had been missed in the audit because of it. Nothing had been, it turned out, but that she had to do two extra days of manual work to get there was entirely on the routing failure, and I said so directly.

After all seven calls, I sent a brief internal note to the team: routing issue in the IT-Ops queue, seven tickets stranded, all resolved, mailbox rebuilt. No assigning blame. Just the facts and the fix.

What the Silence Actually Signals

There is a version of a support failure that announces itself loudly. The escalation to a manager, the angry reply-all, the ticket reopened three times. Those failures are hard to deal with, but they are honest. They tell you exactly where the breakdown happened and that the user still believes the channel is worth using.

Then there is this version. The user who submits one ticket, hears nothing, works around it, and never comes back. No follow-up, no complaint, no escalation. Just a quiet recalibration of what IT support is for.

Tom did not stop trusting the support channel because he could not access a folder. He stopped trusting it because the channel he used to fix that did not respond. The routing failure was the technical problem. The trust failure was the one that persisted after I called him back.

A user who adapts around a broken system is not fine. They are practicing for the next time something goes wrong. And the next time, they may not file a ticket at all. They will start with the workaround because they have learned that is what actually works.

When users stop asking, most support teams do not notice. The queue gets quieter, and quieter sometimes looks like success.

Two Things I Added to the Monthly Audit

That same day I added two checks to my regular routine, and they have stayed there since.

The first is a sweep for tickets older than ten days with zero agent activity. Not just open tickets, but specifically tickets that are open and have not been touched since they were submitted. The age filter alone catches neglect. The activity filter catches routing failures. Those are different problems and both are worth finding.

The second is a routing health check: every queue alias in the system confirmed as pointing to a live, monitored mailbox, owned by at least two active accounts. I run this check after every team departure now, not during the offboarding itself, but as a separate follow-up 48 hours later, once the account has actually been deprovisioned and I can verify the mailbox still responds.

Neither check takes more than twenty minutes. The routing fix on the IT-Ops mailbox took another twenty. The whole corrective effort ran under two hours.

What it cost to get there was harder to calculate. Seven users had spent between eleven and thirty-one days assuming the IT support channel was something it was not. That gap does not close with a fix. It closes over time, one resolved ticket at a time, as people update their experience back toward something worth trusting.

The scariest IT support failure is not the one that generates an escalation. It is the one that generates silence. The routing fix takes twenty minutes. The relationship work takes considerably longer.

If you're thinking about support operations on your own team and want to compare notes, I'm usually around.

Share 𝕏 in ✉

Comments