Trouble Ticket Sample Clauses
A Trouble Ticket clause defines the process for reporting, tracking, and resolving technical issues or service disruptions within a contractual relationship. Typically, it outlines how parties should submit trouble tickets, the information required, and the expected response and resolution times. For example, a customer experiencing a service outage would submit a ticket through a designated portal, triggering the provider’s support team to investigate and address the issue. This clause ensures a clear, standardized method for handling problems, thereby minimizing downtime and misunderstandings between parties.
Trouble Ticket. A Trouble Ticket is the method used by either Customer or Verizon to advise the Verizon Help Desk of a perceived Fault, including a Network Outage or a failure to meet an SLC. A unique trouble ticket reference number will be raised and given to the Customer and should be used each time the Customer calls in to the Help Desk for any Fault update or if appropriate, to inform Verizon of restoration of the Managed Global Network.
Trouble Ticket. Defined in Section 10.2.
Trouble Ticket. Orbitz will create a Trouble Ticket in response to system abnormalities. Each Trouble Ticket shall contain:
(i) Trouble Ticket reference number.
(ii) A description of the problem or interruption or degradation of the Hosting and Support Services, (each a "Service Problem") sufficient to assign a severity level and initiate an investigation of the Service Problem.
(iii) A description of any actions taken by Airline to correct the reported Service Problem.
(iv) The time and date of the call. (v) Source of Service Problem report (vi) An initial severity level designation assigned by Orbitz based upon agreed upon Severity Level Definitions
Trouble Ticket. The tool by which an Eligible Customer reports a perceived fault issue to VTSL and the sole means by which Service Outage Time is calculated
Trouble Ticket. A record of a Services Outage and its subsequent resolution, as recorded by Seller/NECECT; Trouble Tickets are initiated by End Users contacting the published End Users Service points of contact. End User will provide supporting information as reasonably requested by Seller/NEC Cloud.
Trouble Ticket. Official communication from OMB to PROVIDER o fan outage condition caused by products and services provided by PROVIDER. When circuits are under MNS coverage PROVIDER will be responsible to identify and acknowledge that the circuit encounters any problems. Hence for MNS circuits the outage start will initiate immediately when the MNS System identifies the issue.
Trouble Ticket. In the event of an Incident, FRUITA must submit a "Trouble Ticket" to Browns Hill. The Trouble Ticket must include the following information:
a. A detailed description of the Incident;
b. Detailed descriptions of FRUITA's attempts to resolve the Incident at the time of occurrence (subject to the provisions of Section 3(a) of the vSaaS™ Services Agreement.
c. The Trouble Ticket must be submitted electronically (i.e., through Browns Hill's website, ▇▇▇▇▇://▇▇▇▇▇.▇▇▇▇▇▇▇.▇▇▇:58043/data/perspective/client/Support), unless FRUITA determines that the Incident requires emergency resolution. In that event, the Trouble Ticket may be submitted verbally (either by telephone or in person) to Browns Hill at the telephone number provided to FRUITA.
Trouble Ticket. Orbitz will create a Trouble Ticket in response to system abnormalities. Each Trouble Ticket shall contain:
(i) Trouble Ticket reference number. Exhibit F - v ------------ *** Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions.
(ii) A description of the problem or interruption or degradation of the Hosting and Support Services, (each a "Service Problem") sufficient to assign a severity level and initiate an investigation of the Service Problem.
(iii) A description of any actions taken by AA to correct the reported Service Problem.
(iv) The time and date of the call. (v) Source of Service Problem report (vi) An initial severity level designation assigned by Orbitz based upon agreed upon Severity Level Definitions
Trouble Ticket. A record of a Services Outage and its subsequent resolution, as recorded by NECAM; Trouble Tickets are initiated by End-User calling the published End-User Service number of End-User’s dealer of record. End- User will provide supporting information as reasonably requested by NECAM which may include (as applicable), without limitation, the applicable circuit ID, circuit end- point(s), IP address(es), originating phone number and terminating phone number.
Trouble Ticket. Issue reported by a customer registered in STC system for the service that customer has purchased from STC. A period of time notified in advance, during which preventive maintenance of the service, the network or any other component that is necessary to prevent a defect or disruption, causing an impact on the customer’s ability to use/access the service. Downtime resulting from STC Cloud performing maintenance on the service during a maintenance window.