I've noticed that growing IT teams face challenges when keeping ticket ownership clear. Even with a ticketing system, requests often come in through various channels like Slack, email, or informal verbal requests. By the time these requests are officially logged, it becomes unclear who is responsible for what, leading to confusion in priorities. Dashboards might appear organized until something slips through the cracks, resulting in escalations and a scramble to address issues. I'm curious how other teams tackle this dilemma. Do you have a single intake method? Do you utilize Slack workflows or bots for ticket management? Or do you accept a bit of chaos and hope for the best? I'm looking for practical strategies to maintain accountability and visibility without creating excessive overhead.
7 Answers
The real challenge isn't just the volume of requests; it's losing the context around them. We found success by linking requests to a central tracking system right from the start, even if they begin as informal chats or emails. This ensures everyone knows who’s responsible, reducing the chances of forgetting something important without adding extra steps to the process.
While working at a Managed Service Provider (MSP), we have two ways for clients to log a ticket: either by emailing our support address or calling if it's urgent, but they should ideally email first for a ticket number. If I were in an internal IT setting, I'd implement the same protocol with a monitored support email. If anything comes through informally, it doesn't get a SLA, and we'll address it when we can recall it!
In my experience at the enterprise level, all tickets start at L1. Any issues raised outside of the ticket system are treated as best effort, so not part of the Service Level Agreement (SLA).
One simple solution is to ignore any requests that aren't submitted through the ticket system. Just assign tickets and stick to that policy. It streamlines everything and makes ownership clear. If someone doesn’t put in a ticket, then it’s not my problem!
Totally! Management should enforce this policy as well. No bypassing the ticket system unless it’s an emergency!
Slack is great for quick queries but not reliable for tracking ownership. Tools that convert Slack messages into formal tickets, like Siit, can eliminate confusion and maintain oversight without adding too much hassle.
Always ask if there's already a ticket. If something comes up in a chat and needs to be addressed, jot down some quick notes and create a ticket on the spot. This way, you have the info documented as you go, which helps a lot!
Exactly! You could say something like, 'That sounds like it needs attention. Have you put in a ticket yet? If you have a ticket number, I'll make sure it's being looked at.' It's all about using friendly language.
Setting up automated ticket creation can help a lot! If you get a request, it can automatically assign a ticket to the person who reached out. It might take a bit to perfect the workflows, but that's definitely the way to go. By the way, what ticketing system are you currently using?
Absolutely agree with that! No ticket, no problem.