How to Ensure Clear Ticket Ownership in IT Requests?

In the managed services provider world, we have a straightforward process: clients can log tickets via email or, if it’s urgent, they can call us. But they should do the email step first to provide a ticket number; that saves us time during the call. If I were in an internal IT role, I’d use a similar system—monitoring a dedicated support mailbox linked to the ticketing system to streamline the process.

For larger organizations, it’s vital to ensure that all tickets start at Level 1. Any issues that are raised outside of the formal ticketing system should be treated as best-effort and won’t fall under any service level agreements (SLAs). This keeps everyone aligned on expectations.

Automating the ticket creation process can be a game changer. Set up workflows that automatically assign requests to the sender. While it might take some time to fine-tune, it'll pay off in the end. Also, ensure that the helpdesk is filling out the tickets accurately when creating them manually. Just out of curiosity, what ticket system are you using?

Always check if a ticket has been created when someone approaches with a request. If it hasn’t, guide them to make one. It helps to take notes during the conversation and enter them into the ticket right away—it keeps all the details fresh and allows for better tracking.

One effective approach is to ignore any requests that haven't been documented through a ticket. Just assign the tickets and move on from there! It's all about being firm on what's accepted as a valid request and what isn’t. Management needs to communicate this policy clearly so that people understand the process; no bypassing the ticket system for quick favours! The only exceptions should be for critical issues, like hardware failures.