• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer
Entry Software Corporation

Entry Software Corporation

Entry

  • About Us
    • Contact us
    • Our Story
    • Message from the CEO
    • Customer Quotes and Case Studies
    • Press Releases
  • TeamHeadquarters
    • Overview
    • Value Proposition
    • Help Desk
    • Project Management
    • Resource Management
    • Team Resource Management
    • My Company
    • My Organizations
    • Videos
  • Pricing
    • Cloud Pricing
    • On Premise Pricing
    • Services
  • Industries
    • Transportation
    • Education
    • Healthcare
    • Manufacturing
    • Municipalities
    • Service Business
  • Get a Demo

The Help Desk Ticket Life Cycle

June 12, 2017 by Mark Donais


The help desk ticket life cycle, AKA Incident Management, is the process that you define during your ITIL® Incident Management Process. The Help Desk Ticket Life Cycle is important because by defining it you can:

  • service your customers,
  • plan your resources,
  • define your acceptable backlog and
  • set the stage for customer and staff expectations.

You need to plan your Help Desk Ticket Life Cycle. A good way of visualizing the process is to use a funnel.

  1. Service requests come in the top of the funnel.
  2. Actions deliver the services.
  3. Completed requests come out the bottom.

As you plan your funnel, you will try to achieve an ideal where all service requests are handled immediately thus turning your funnel into a straight through pipe failing when you realize that to service all requests in this fashion requires too many people, resources, and money.

The funnel starts to constrict at resources and processes.

As you design your funnel, allow for backlogs. Define the backlogs in your ITIL® Strategy and determine acceptable values for the backlog of issues based on issue type. You may arrive at the following conclusions for a type. You have mission critical requests and non-mission critical issues.

Mission Critical Requests, levels one through three. A mission-critical request with a level of importance of one would be the most important issue. Backlogs are as follows:

  1. One: no backlog acceptable
  2. Two: 1 hour backlog
  3. Three: 4 hour backlog

Non-Critical Requests, levels one through three to signify levels of importance. A non-critical request with a level of importance of three would be the least important issue.

  1. One: One day backlog
  2. Two: One week backlog
  3. Three: Semi-permanent backlog state

The Service Process

The complications that you build into your Help Desk Life Cycle will slow it down. This is OK but must still allow the process to function in the worst-case scenario. If the Help Desk Life Cycle breaks when it is needed the most then it must be re-engineered until it works. The minimum amount of process should be in place and result in quick and efficient service to customers with a minimum of resources. See how this can be accomplished with TeamHeadquarters.

This is the delicate balance between service, cost and resources. If cost is no issue, then your organization can build a service pipeline. If cost is an issue, then your organization can build a service funnel.

Filed Under: IT Managers, ITIL, ITIL Service Desk, ITSM Tagged With: ticket life cycle

About Mark Donais

Primary Sidebar

TEAMHEADQUARTERS OVERVIEW

TEAMHEADQUARTERS EXPLAINER VIDEO

Recent Posts

  • Understanding Service Level Agreements (SLA)
  • Improving Customer Service
  • Remote Project Management
  • What does it take to be an IT Manager?
  • Tips for Managing IT Team Effectively

Recent Comments

  1. What Are Common Problems In Scheduling Housekeeping Staff? – Fallsgardencafe on Proper use of Project Milestones in the Field of Project Management

Archives

  • March 2022
  • February 2022
  • March 2019
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017

Categories

  • Agile
  • Audiences
  • Business
  • Capacity Planning
  • Case Study
  • Change Management
  • Client Management
  • Client Services
  • Cloud Based
  • Content strategy
  • Customer Service
  • Customer Tracking
  • Education
  • Facilities Management
  • Help Desk
  • Help Desk and Project Management Software
  • Help Desk Software
  • IT Help Desk
  • IT Managers
  • IT Strategy
  • IT Work Management
  • ITIL
  • ITIL Service Desk
  • ITSM
  • Leadership
  • Milestones
  • Multiple Projects
  • Never ending project
  • Operations Management
  • Prioritize Projects
  • Project Clarification
  • project delays
  • Project Management
  • Project Management Engagement
  • Project Management Software
  • Project Management Tools
  • Project Manager Communication
  • Project Negotiation
  • Projects Collision
  • Resource Management
  • SaaS
  • Schedule Management
  • Service Desk
  • Service Level Agreement
  • Small Business
  • Software
  • Strategy
  • Ticketing System
  • Time Management
  • Uncategorized
  • Work Management Software
  • Working Efficiently

Footer

Blog
Login to TeamHeadquarters™
Team Headquarters Help

Brochures & News

TeamHeadquarters™ brochure
Customer testimonials
Press Releases

Legal and Site

Privacy Policy

Free eBooks & Tools

  • IT Managers Guidebook to Implementing ITSM
  • The Essentials of Project Communication Success
  • Tracking Project Status Throughout the Engagement
  • ITSM Readiness Assessment
  • Challenges Facing IT Leaders when working with Disparate Systems
  • Customer Satisfaction Survey Best Practices

Entry Software Corporation

Founded in 1998, Entry Software Corporation has been leading the industry with service desk and project management software for manufacturing, transportation, healthcare, municipalities, service organizations, and education.

Entry Software Corporation © 1998 to 2022

 

Entry Software Corporation © 1998 to 2022