Creating a Support Ticket Sample Clauses

Creating a Support Ticket. The Supplier will use their ticketing portal, to ensure that the Supplier is aware of any/all issues, can ensure that matters get dealt with promptly and provide the Customer with an initial point of contact for all issues. Once a ticket has been logged with the Supplier, it will then be assigned to the most appropriate consultant. An Incident is defined as an event where it is not a standard operation of service for live and implemented modules. A request is for minor changes, enhancements or any other required operation not classified as an incident. When an incident has arisen that is identified as an issue with the actual implementation, the Supplier will highlight this.
Sample 1Sample 2
AutoNDA by SimpleDocs
Creating a Support Ticket. The Supplier will use their ticketing portal, to ensure that the Supplier is aware of any/all issues, can ensure that matters get dealt with promptly and provide the Customer with an initial point of contact for all issues. Once a ticket has been logged with the Supplier, it will then be assigned to the most appropriate consultant. An Incident is defined as an event where it is not a standard operation of service for live and implemented modules. A request is for minor changes, enhancements or any other required operation not classified as an incident. When an incident has arisen that is identified as an issue with the actual implementation, HPS will highlight this.
Sample 1
Creating a Support Ticket. The Supplier will use their ticketing portal, to ensure that the Supplier is aware of any/all issues, can ensure that matters get dealt with promptly and provide the Customer with an initial point of contact for all issues. An Incident is defined as an event where it is not a standard operation of service for live and implemented modules. A request is for any other required operation not classified as an incident e.g. a query. Exports of the current list of open tickets, their current statuses and owners are also available on request.
Sample 1

Related to Creating a Support Ticket

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Freedom. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Freedom (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If ECI chooses to subtend a Verizon access Tandem, ECI’s NPA/NXX must be assigned by ECI to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 ECI shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from ECI’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office ECI utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow ECI’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Child Support (Applicable if the Party is a natural person, not a corporation or partnership.) Party states that, as of the date the Agreement is signed, he/she: a. is not under any obligation to pay child support; or b. is under such an obligation and is in good standing with respect to that obligation; or c. has agreed to a payment plan with the Vermont Office of Child Support Services and is in full compliance with that plan. Party makes this statement with regard to support owed to any and all children residing in Vermont. In addition, if the Party is a resident of Vermont, Party makes this statement with regard to support owed to any and all children residing in any other state or territory of the United States.

  • Product Support Not applicable

  • Customer Support If Customer is entitled to receive Customer Support as part of a separately purchased Service Plan, Sage warrants that while Customer’s Service Plan is in effect and if it has paid all required Service Plan fees, Sage will use qualified personnel to provide Customer Support in a professional manner consistent with industry standards. Customer’s sole remedy under this section 5.2 is limited to Sage’s re-performance of the Customer Support services giving rise to Customer’s claim.

  • Software Support During the Term, Seller shall use commercially reasonable efforts to provide all Software updates and qualified Software upgrades in accordance with the terms of the Service Contract as such materials become commercially available for distribution. Purchaser’s use of all Software, updates, and upgrades of Software shall be subject to this Agreement, the Original Terms, and the applicable XXXX.

  • Dark Fiber Loop 2.8.4.1 Dark Fiber Loop is an unused optical transmission facility, without attached signal regeneration, multiplexing, aggregation or other electronics, from the demarcation point at an End User’s premises to the End User’s serving wire center. Dark Fiber Loops may be strands of optical fiber existing in aerial or underground structure. BellSouth will not provide line terminating elements, regeneration or other electronics necessary for AFN to utilize Dark Fiber Loops.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Wire Unbundled DS1 Digital Loop This is a designed 4-wire Loop that is provisioned according to industry standards for DS1 or Primary Rate ISDN services and will come standard with a test point, OC, and a DLR. A DS1 Loop may be provisioned over a variety of loop transmission technologies including copper, HDSL-based technology or fiber optic transport systems. It will include a 4-Wire DS1 Network Interface at the End User’s location.

  • Innovative Scheduling Schedules which are inconsistent with the Collective Agreement provisions may be developed in order to improve quality of working life, support continuity of resident care, ensure adequate staffing resources, and support cost-efficiency. The parties agree that such innovative schedules may be determined locally by the Home and the Union subject to the following principles: (a) Such schedules shall be established by mutual agreement of the Home and the Union; (b) These schedules may pertain to full-time and/or part-time employees; (c) The introduction of such schedules and trial periods, if any, shall be determined by the local parties. Such schedules may be discontinued by either party with notice as determined through local negotiations; (d) Upon written agreement of the Home and the Union, the parties may agree to amend collective agreement provisions to accommodate any innovative unit schedules; (e) It is understood and agreed that these arrangements are based on individual circumstances and each agreement is made on a without prejudice or precedent basis. (f) It is understood and agreed that these arrangements can be utilized for temporary job postings for seasonal coverage (e.g. weekend workers, etc.).

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!