Want Big Improvements in ITSM? Start Small.

Have you ever faced a challenge so big that you didn’t know where to begin, so you simply did nothing? It’s happened to the best of us, and it happens far too often in the world of ITSM. In many cases, IT decision makers know improvements must be made, but the looming costs and risks have them circling their wagons, afraid to take that leap and get started. If you are in this situation currently, the solution is simple: get back to basics. Rather than taking on huge, risky and expensive ITSM projects, start where you are and take it one step at a time. By starting small, you’ll eventually achieve the big change you seek.

As an example, let’s take a larger ITSM organization that provides support service to external clients across the globe. An operation like this has a ton of service desks, some of which support multiple customers, others are dedicated to individual customers and still others are designated for internal users. Some service desks provide only logging and dispatch while others also offer level 1 support. Across all of these service desks, there are a wide variety of tools and technologies being employed.

In this scenario, the vast majority of communication with customers, for all the service desks, takes place via telephone. Decision-makers within the organization recognize the need for more efficient communication channels (i.e. self-service portals and chatbots). The problem is, in a company that large, the costs of implementation would be tremendous. IT leaders have actually already identified a tool capable of supporting such a complex environment, but because they lack confidence and adequate justification that the project would run smoothly and produce ROI, they can’t nail down funding.

Believe it or not, the solution to this monster of a dilemma is actually quite obvious. Rather than attempting to roll out chat for their entire user base – a significant and costly undertaking – all they really need to do is begin where they are and implement in several smaller steps.

For instance, IT could introduce an easy-to-use, out-of-the-box chatbot platform and designate a small group of users to begin using this tool when they need IT support. IT would then closely monitor the process to identify any issues – either on the service desk or end user side – and work to resolve those issues before scaling up. Over time, the IT team will have:

  • Pinpointed and addressed many issues as they relate to chat-based interactions with the service desk
  • Identified which types of requests are best suited for chat and which are better handled via other channels
  • Figured out how to best encourage users to transition from telephone support to chat
  • Gathered and analyzed data regarding the volume of requests each agent can manage using chat
  • Determined exactly how much time and money could be saved if scaled to the entire organization

Rolling out chatbot support this way is far less risky, and by starting with a tool that is easy to use and doesn’t require coding and/or a ton of training, the overall cost of implementation also remains low. As the project is slowly scaled up, the IT team will have all the information they need to determine whether full implementation would be a cost-effective investment with quantifiable proof to back them up. They’ll also already know what needs to be done in order to ensure success as the project expands.

The good news is, starting small is easy when you have the right tool in your corner. Ayehu is specifically designed to provide rapid time-to-adoption and enhanced simplicity to even the most complex ITSM projects. Don’t believe us? Try it free for 30 days and experience it for yourself. You have nothing to lose!

5 Ways to level up your service desk using it process automation