I've been wondering how other teams handle IT requests that come in via Slack. We've got users sending requests everywhere—DMs, channels, emails... you name it. We've made efforts like reminding them to submit formal tickets, but let's be real, Slack isn't going anywhere. The issue is that context gets lost and nothing gets properly tracked, which leads to a lot of cleanup work for the help desk. Are you all just straight up forcing every request into a ticketing system, or do you use something that can automatically convert Slack messages into tickets? What strategies have you found effective in both the short and long term?
7 Answers
Honestly, if there's no ticket, it doesn't happen. It’s really that simple. Just stand firm about this policy; if users insist on communicating via Slack, keep redirecting them to your ticketing process. Eventually, they'll catch on. A clear procedure will help them understand that ticketing ensures accountability and proper tracking.
I've seen the chaos you're talking about. We ended up using ClearFeed to manage requests through Slack without forcing users to change their habits. It identifies genuine requests and keeps everything organized, making it easier to track than traditional methods.
No ticket, no service, that’s my mantra. If users come to me through Slack, I reply with a friendly reminder to submit a ticket so we don't lose track. At the end of the day, it's about keeping everyone accountable and ensuring proper documentation.
I like to add something like 'so we can track and handle your request properly' when I ask them to submit a ticket. It makes it sound less stiff and more friendly.
We have a designated channel for IT requests in Slack. Users are directed there, and a ticket gets created whenever they post a request. This way, they know exactly where to go, and we avoid message overload.
Management also plays a big role. If they clearly communicate that requests need to go through tickets, it sets the tone for everyone else. You genuinely need that backup to make sure users understand the change.
It's not rocket science! Just keep it straightforward: if there's no ticket, there's no support. It's about educating users on why submitting a ticket is crucial for tracking their requests efficiently. You'll thank yourself later when everything is documented properly.
Haha, I love this approach! I always remind my team that it’s not personal, it’s just policy.
Integrating a ticketing system with Slack can really help. We’ve set it up so that when users send a message in the appropriate channel, it automatically creates a ticket. This way, we save time and keep everything organized without users needing to change their behavior drastically.
That sounds smart! We tried a similar method with integrations and it really cut down on the chaos.
Absolutely! It's all about sticking to the rules. I've found that once people realize they won't get immediate help without a ticket, they'll start doing it the right way.