Skip to content

Latest commit

 

History

5 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 

Repository files navigation

osTicket logo

osTicket - Ticket Lifecycle: Intake Through Resolution

This tutorial outlines the lifecycle of a ticket from intake to resolution within the open-source help desk ticketing system osTicket.

Video Demonstration

Environments and Technologies Used

  • Microsoft Azure (Virtual Machines/Compute)
  • Remote Desktop
  • Internet Information Services (IIS)

Operating Systems Used

  • Windows 10 (21H2)

Ticket Lifecycle Stages

  • Intake
  • Assignment and Communication
  • Working the Issue
  • Resolution

Lifecycle Stages

These stages may be represented in different ways depending on the ticketing system being used, but they generally follow a similar process flow. By understanding the ticket lifecycle stages, support teams can efficiently manage and resolve requests and issues, resulting in higher customer satisfaction and support team productivity.

Create Tickets

Intake - The ticket is created when a user submits a request or issue to the support team. Assignment - The ticket is assigned to a specific agent or group of agents responsible for handling the request.


Work in Progress

    Working the Issue in progress
- The assigned agent begins working on the ticket by gathering information, troubleshooting, and communicating with the requester.Pending: If the ticket requires further information or clarification, it may be placed in a pending status until the requester provides the necessary details. On-hold: If the ticket cannot be resolved immediately or requires action from an external party, it may be placed on hold until the issue can be resolved. Escalation - If the ticket is not resolved within a certain timeframe or requires further attention, it may be escalated to a higher level of support or management.


Disk Sanitization Steps

    Resolution
- The ticket is resolved when the issue or request has been resolved to the satisfaction of the requester. Closure - The ticket is closed once it has been resolved and the requester has confirmed that the issue or request has been resolved to their satisfaction.

Disk Sanitization Steps

Follow-up - In some cases, the support team may follow up with the requester after the ticket has been closed to ensure that the issue or request has not resurfaced.


About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors