The Helpdesk Model – What It Means to Put Helpdesk to Work and Improve


Have you considered the impact your IT helpdesk has on the business you support? Think about your company’s reliance on technology and IT applications— when service interruptions happen, they impact processes and cause business disruption. The IT Helpdesk is much more than answering the phone and helping users solve their IT problems. Helpdesk has a direct impact on running the business, providing quality customer services and ensuring business profitability. If you are implementing an IT helpdesk in your company or in the process of improving your existing one, this article is for you. First, let’s discuss the IT Helpdesk Model. The diagram model shows the eight components of the IT Helpdesk Model. Each is briefly described below.  

Eight Components of the IT Helpdesk Model 

  1. IT Helpdesk Organization – This component represents the managers, staff, functions and supporting groups that comprise the IT helpdesk organization.
  2. Enablers – Enablers are tangible and intangible components needed to operate the IT helpdesk. This includes technology, tools, communication channels and analytics. Other important enablers are the required competencies of the individual staff working at the helpdesk and the group’s combined capabilities. 
  3. Service Review Board – The  Service Review Board is the steering committee or sponsor of the IT helpdesk organization. The group is composed of key IT managers, business/customer representatives and (if necessary) external consultants. They are responsible for providing strategic guidance, support, resources, and feedback to the group. 
  4. Business / Customers – This represents the customers that receive the IT helpdesk services. Your customers are everyone in the company; not just everyone who has computers, but everyone who has access to one that uses it as part of his / her function. It is important for IT helpdesk to know its customers and be able to identify and segment them. 
  5. Mission – The mission statement is the declaration of purpose, values, direction and tactics. It governs how the IT helpdesk will run its service delivery to its customers and guide every interaction it has with the users. 
  6. Service Offer – Your service offer represents the scope of your services to your customers. The services that your IT helpdesk provide are determined by business or customer needs. A good service offer is composed of service elements that are manageable and provide the best value to the business. 
  7. Performance – It is critical for part of the IT helpdesk function to be tied up with performance measures.  Performance should be measured periodically if the service offers are attained in a satisfactory manner. This component represents performance indicators that have to be defined and tracked. Performance also includes how the IT Helpdesk receives and handles feedback from surveys and customer focus groups.  
  8. Continuous Improvement – This component is tied up with performance measures. Your IT helpdesk will have to adjust services regularly — as business changes and as your customers demand more. Continuous improvement includes working on actionable items from performance monitoring or data analysis. 

Five Ways to Improve Your IT Helpdesk

1. Understand your Purpose, Involve your Customers and Set the Right Expectations  – Understand what senior management and your internal customers expect. Have focus group discussions with business leaders and key customers. Listen to feedback—positive and negative. Understand their concerns and identify opportunities. Invite your key customers to join and participate in your Service Review Board. When you and your customers communicate and understand what your service offers are, it easier for you to keep them satisfied because you have set the right expectations for your services. 

2. Establish a Clear Mission Statement  – Your mission statement is your declaration of purpose and values. This will set the direction of the group on how to interact with customers. It governs every interaction that deals with a call, request or problem. Putting together a mission statement must be a collaborative process. Let key members of the helpdesk and internal stakeholders participate in putting together a mission statement. A sample mission statement could read, “Focus on the needs of the business and support the customer in making the best use of technology in business.”  A sample value statement would read, “We aim to minimize downtime by restoring service as fast as we can. We solve problems, not symptoms, and work to resolve the root causes.”

3. Develop Needed Competencies and Roles. – To have an effective helpdesk organization, there needs to be clearly defined roles and an effective way of performing them. The major competencies and roles within helpdesk are: stakeholders, problem solver or experts, data analyst, communicator, and the customer service liaison. Stakeholders are represented in the IT Helpdesk Model as the Service Review Board. This group is established to provide sponsorship, guidance and support to the IT helpdesk organization. Problem solver and experts are senior members (level two or higher) of the helpdesk whose task is to solve escalated problems and find solutions to recurring incidents. Data analysts consistently mine helpdesk databases for trend analysis. The Communicator is responsible for the continuous improvement of helpdesk communication and customer service competencies. They are also responsible for call quality assurance. Customer Service Liaisons are members of the helpdesk who manage customer relationship and gather feedback from the customer through surveys and focus group discussions. 

4. Develop Your Service Offer – Your service offer should be tied up with your mission, customer need, budget and internal capabilities. Focus on providing services that give the best value to the business. Eliminate non-value creating services from your portfolio. If you provide too many services on a broad range of domains, you are setting your helpdesk group up for failure. Avoid situations where your resources are thinly spread and customers with important needs are forced to wait while you attend to a service that does not create value. Services are manageable, supportive of the business needs, well defined and well understood. After defining your service offer, communicate and market services to your customers. Remember that the service offer needs to be adjusted on a regular basis in order cope with changes in business needs, budget and customer expectations. An example of service offers are: “Provide support between 6am to 7pm daily. Allow customer channels such as email, call, voice mail, chat, and intranet site. Provide consulting on software recommendations. Broadcast information about system availability and planned maintenance. etc.” 

5.Have a Culture of Continuous Improvement – Most existing IT Helpdesks have massive amounts of data at their disposal—yet fail to utilize it in any meaningful way. Running an IT Helpdesk means gathering a lot of data for the purpose of evaluating service performance and resolving problems. Use data effectively to discover valuable insights and evaluate performance versus set target and objectives. Use data to conduct trend analysis on recurring issues so as to implement proactive measures in reducing the number of calls and incidents. Have a culture of continuous improvement. Don’t settle for mediocre performance. Always challenge your IT Helpdesk to continuous improvement in every aspect of the service it provides.

Please share with us your experiences in implementing and managing your IT Helpdesk. What were the challenges and key learnings? You can also post your questions about the topic so that I and readers can respond to them. Thank you.

Follow Glenn Remoreras and IT Branding on Twitter.

6 thoughts on “The Helpdesk Model – What It Means to Put Helpdesk to Work and Improve

  1. The name Service Desk indicates more the orientation of giving a good service, and this is the core of the business. But what about IT process automation for having a culture of continuous improvement, as you mentioned in your 5th point. Where you can free the hands of your IT personnel from mundane repetitive tasks and let them deal with important service oriented operations. This should be on the agenda as well. For more about it read this eBook http://bit.ly/QxabE8

  2. ITIL terminology is just silly. It doesn’t matter what you call it as long as you provide all the services needed and everyone knows your name. Help Desk is what most people know (at least at my company), so changing the name to Service Desk or anything else would only serve as a barrier to communication. Sure, people would get used to it eventually but why bother. To challenge ITIL with another English source on naming, “What’s in a name? that which we call a rose by any other name would smell as sweet” Don’t worry about the name; worry about the job.

  3. Hi, According to ITIL v3, shouldn’t be called Service Desk instead of Help Desk? I know is not a deep thought, just wondering.

Leave a comment