Posted on

All you need to know about ITS in a call center

In call centers’ context, ITS stands for issue tracking system. It is also known as trouble ticket system, support ticket, request management or incident ticket system. An ITS is a computer software package that manages and maintains lists of issues, as needed by an organization and is used in its customer support center. They are basically used to create, update, and resolve reported customer issues, or even issues reported by that organization’s other employees. As a matter of fact, support ticket should include vital information for the account involved and the issue encountered.

Issue tracking system
Issue tracking system

In most cases, an issue tracking system also contains a knowledge base containing information on each customer, resolutions to common problems, and other relevant data. An ITS is similar to a “bug tracker”, and often, a software company will sell both. In fact, some bug trackers are capable of being used as an issue tracking system, and vice versa. Consistent use of an issue or bug tracking system is considered one of the “hallmarks of a good software team” as it enhances the quality of customer service.

Knowledge base software
Knowledge base software

A ticket element, within an issue tracking system, refers to a running report on a particular problem, its status, and other relevant data. They almost always have a unique reference number, also known as a case, issue or call log number which is used to allow the user or help staff to quickly locate, add to or communicate the status of the user’s issue or request. Also, they are commonly created in a help desk or call center environment

Support ticket
Support ticket

As far as issues are concerned, they can have several aspects to them. An urgency value may be assigned to each issue in the system, based on the overall importance of that issue. Of all the issues, low or zero urgency issues are minor and should be resolved as time permits. Other details of issues include the customer experiencing the issue (whether external or internal), date of submission, detailed descriptions of the problem being experienced, attempted solutions or workarounds, and other such information.