The Integrated Service Desk: 4 Ways to Improve Processes and Consolidate Systems

  • 2,550 views
Uploaded on

This HDI article examines four innovative ways integrated processes could work if the appropriate tools were readily available.

This HDI article examines four innovative ways integrated processes could work if the appropriate tools were readily available.

More in: Lifestyle
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
2,550
On Slideshare
0
From Embeds
0
Number of Embeds
9

Actions

Shares
Downloads
50
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. The Integrated Service Desk: Special Advertising SectionFour Ways to Improve Processes and Consolidate Systems 4
  • 2. Special Advertising Section Not too long ago, all an IT support A lack of integrated tools can also affect how quickly larger problems are identified. Many times, tools used to professional needed was to know the monitor the environment are separate from the tools used nuances of an operating system and have for support, and, in fact, are often owned by completely a basic understanding of how a computer different teams. Problems could be proactively identified was put together. While IT support was a if only those monitoring systems were integrated directly very specialized and necessary function, with the service management tools. Rather than the support team only having visibility into single incidents, it was narrowly focused because the they would have a broader view of support issues. It technology was new and immature. The would enable them to do root cause analysis in advance, work intake for the IT support team was rather than damage control after the fact. often simply a tap on the shoulder and a What this clearly shows is that, by and large, support request: “Can you fix my computer?” tools and processes have simply not kept up with the growth of technology as a whole. Why can’t all of these Today, technology touches nearly every aspect of our systems be integrated? lives. Even the definition of “computer” has blurred to the point that it hardly resembles those big, heavy Let’s examine four innovative ways integrated processes bricks we worked on and supported “way back when.” could work if the appropriate tools were readily available. We still have desktop and laptop PCs, but we also have tablets, smartphones, thin clients, and countless wired and wirelessly connected devices running many different flavors of operating systems. Add to that the rich complexity of enterprise networking, with virtual desktops, mobility, cloud-based services, and the consumerization of technology, and it all adds up to an extraordinarily complicated world. Despite the changes and challenges, users still expect the same— or better—levels of support from their IT departments. Unfortunately, support systems have not always kept up with the growth of technology. Many IT shops still struggle with the same shoulder-tap model that was used in simpler times. Even if they’ve managed to move beyond that, it’s often only by using a number of unrelated or dissimilar tools. The lack of an integrated set of tools results in a disorganized workflow. Even if there is an incident management tool, it may require considerable manual effort, with the incident ticket being passed back and forth between support teams. The customer contact process could still be manual as well; if remote tools are being used, they’re likely to be a separate set of tools entirely. Documentation is lacking because the support team is constantly distracted by requests from clients to fix routine problems. These are typically issues that could be fixed by end users if they only had access to self-service tools that allowed them to resolve their own issues.
  • 3. Special Advertising Section 1: to visit the user’s desk. Advances in remote support tools have made it possible for an IT support team to take over a desktop, configure or repair software, Streamlines the Workflow troubleshoot the operating system, and even reboot the client device while maintaining the networkIt takes time to move a ticket through the chain of connection. Really, the only time a physical visitcustody. The service desk owns it first; they pass it along to might be necessary is if the client machine can’tthe next level of support, and then it often has to go back connect to the network or hardware needs to beto the service desk for final closure. Why not streamline repaired/replaced.this workflow and include the second-level support team Since the support session originates with the incidentfrom the beginning? Instead of the service desk acting as tool, it becomes much easier to document what ita dispatcher, the service desk guides the incoming call takes to resolve an issue. This information can, in turn,directly to the support team that can fix the problem. be used to populate a knowledge management tool soFrom there, rather than moving outside the incident that similar issues can either be quickly resolved orsystem to open a remote support session, the tool for even converted to a self-service function. The oppositetaking control of a client desktop is integrated right into can also be true. If an organization allows clients tothe incident tool. In many cases—in fact, in the majority request assistance via, for instance, a chat client, onceof cases—it’s really not necessary for second-level support a problem has been identified, a support ticket can be created directly from the remote support session. This saves time and reduces the volume of calls coming into the service desk. The support system should also be closely integrated with monitoring tools. Rather than waiting for recurring incidents be become a management issue, have the monitoring tools proactively identify trends and issue warnings to IT support. Armed with this information, the support team can begin working on fixing potential problems before they get out of hand. Finally, any support tool needs to be adaptable. Technology changes quickly, and support professionals need to be able to keep up. Can it support mobility? Virtual environments? Clients expect their support teams to adapt, so the tools we use must be flexible enough to accommodate a changing technology landscape. 2: Fits Your Support Framework The flexibility of the tool is very important because the overall framework of how clients are supported depends upon the industry, the maturity of the IT organization, and the needs of the business. One common IT framework is ITIL, which sets standards for incident, problem, release, and change management. Even if an organization hasn’t formally adopted the ITIL strategy, they likely follow a similar framework
  • 4. Special Advertising Section just to keep the environment orderly; there’s no such thing as the perfect system, so everyone has developed processes that define how the support team responds when things go awry. Whichever tool you select for support, you should be able to adapt it to your internal support framework. When changes or new software releases occur, the 4: details—approvals, ownership, and the specifics of the change—should seamlessly pass into the support system so the team is aware and can be on the lookout for potential incidents that result. If there’s a marked increase in incidents, those issues can be tied to a Enables and Empowers the Business problem ticket, which, in turn, should be escalated Last but not least, any modern support tool needs to enable back to the owner of the change. Since this all the business by making simple or routine jobs a self-service should be happening inside one system, no time is task. By tying your monitoring tools into your incident wasted moving from one tool to the next or trying to system, you can quickly determine the most common types determine the root cause of a problem. of incidents. Using that information, build self-service around the resolution of the issue. This makes your clients happy because they get a faster turnaround, and it makes 3: your IT support team happy because they now have time to focus upon bigger, more critical issues. Facilitates Anytime, Moving from an IT support “toolbox” to a streamlined, integrated set of tools just makes good business sense. Anywhere Availability Streamlined workflows result in better, faster resolution times and provide better visibility into the overall IT We hear a lot about cloud computing nowadays, and framework. Support teams are able to focus on the bigger our support tools should take advantage of this new issues rather than the routine—all the while enabling the technology. By putting services in the cloud, analysts business and making your customers happy! will no longer need to hurry back to their desks to update incidents; it can be done right from a user’s desk, if necessary. It also opens up the support team Written by Mike Hanson on behalf of Citrix. For more to a virtual world where it doesn’t matter where they information about creating an integrated service desk, sit. Having the availability in the cloud enables the please visit www.gotoassist.com. Additionally, visit team to get an incident to the right person, no matter news.citrixonline.com/resources for more white papers, where they happen to be located at the time. briefs, and webinars on this topic.