The life of a telecom trouble ticket
There is one constant in the management of telecom services; circuits have problems. This is an unfortunate truth about the technology that we all depend on so much. With that fact in mind, the next thing to consider is how a company manages those events. Let’s take a hypothetical look at a company that manages the carriers directly as compared to one that outsources that process.
In this comparison, ABC Enterprises manages telecom for all 70 of their locations, while XYZ Corporation outsources the management of their telecom.
The branch manager of ABC Enterprises realizes that their T1 is down and production is at a standstill. Based on the time of day and time zone, he either calls corporate or takes on the task himself. Assuming that the “telecom department” is handling it, the investigation starts. Who is the carrier, what is the service, what number do I call? Eventually call is placed to the Customer Service call center of the carrier and the process begins. The trouble ticket is verbally explained to the customer service rep. What is the address of the facility, what is your account number, do you know the circuit ID of the T1, and is there any trouble history with this circuit? Please hold while we generate a trouble ticket. Compare that to the company that uses an outsourced Telecom Lifecycle Management service. The manager learns of the T1 problems and notifies corporate. The IT department logs onto their cloud based telecom management tool. They click on the site that is having the problems. Site information provided includes but is not limited to address, circuit type, underlying carrier, circuit ID, install date, long distance provider, associated other services and complete history of that circuit from day of installation. The IT manager clicks on the open case tab or calls vCom customer service. The ticket is opened and the management of that trouble is in place.
In the case of ABC Enterprises, the IT manager is informed that the ticket has been created and they can check back later. As the day moves on, the IT manager makes random calls to the call center to track the progress of the ticket. Throughout the day, there are many calls and a lot of time that the well paid IT manger is sitting on hold with the carrier rather than managing IT. It is now 6:00 in the HQ office and the process needs to be handed off to the west coast IT team to manage. The IT manger attempts to verbally explain the situation to the west coast office without missing any critical information. The west coast office now sits on hold with the carrier.
Meanwhile XYZ Corporation checks their TMaaS tool for constant updates (24/7/ 365) including ticket status, notes from customer service as well as EVERY e-mail regarding ticket from customer, carrier and anybody else involved in repairing the circuit. All of this is stored in the history of that circuit. The service is repaired and the notes reflect the nature of the problem and the ticket is now closed and archived.
We often run into situations where the customer wants to manage the carrier rather than have us do it. Based on the cost of managing those services in house and the lack of tools to do so, it is apparent that there is a far batter way.