The Internet Engineering Task Force's Network Working Group specified requirements for a trouble ticketing system in RFC 1297 (NOC Internal Integrated Trouble Ticket System Functional Specification Wishlist). In the RFC document, the author compares the trouble ticket to a patient's hospital chart, because both define a problem and help to coordinate the work of several different people who will work on the problem at different times.
As a ticket moves though the system, it is usually classified as a certain type of issue, which in turn determines the skillset and expertise level of the agent(s) the ticket is assigned to. Until the issue is resolved, the "open ticket" for the problem remains in the work queue, with issues of highest priority taking precedence in terms of work flow.
Continue Reading About trouble ticket (trouble report)
SearchCRM offers a collection of Best Web Links for "Customer Care and Tracking."
The Network Working Group's RFC 1297: NOC Trouble Ticket Requirements provides more information.
A Nortel document walks you through the trouble ticket workflow procedures in "Workflow Scenario: Trouble Ticket."
SearchCRM.com offers a white paper: Employee Self-Service: Benefits for the Help Desk
SearchCRM.com's Ask the Expert: Knowledge management for the help desk
Related Terms
contact center infrastructure
A contact center infrastructure is a framework composed of the physical and virtual resources that a call center facility needs ... See complete definition
contact center software
Contact center software is a technology tool that increases the effectiveness and efficiency of a contact center, with specific ... See complete definition
high-touch customer service
High-touch customer service refers to the idea that some customer service issues are complex or high value and thus require human... See complete definition
trouble ticket tracking excel template, trouble ticket tracking software, trouble ticket tracking system
Source: http://docphy.com/technology/computers/software/trouble-ticket-trouble-report.html
No comments:
Post a Comment