Unacceptable Customer Service Events Sample Clauses

Unacceptable Customer Service Events. 1.1 The Section Developer shall proactively ensure that Trip data submitted to MDTA meets or exceeds performance standards as well as actively and honestly communicate to MDTA any issues that occur (or may occur) with Trip data. The parties acknowledge and agree that whenever possible MDTA shall learn of issues with respect to Trip data from the Section Developer and not from Users or the general public. If the Section Developer experiences quality issues with respect to Trip data, it shall communicate such issues to MDTA immediately (notwithstanding that the Section Developer may not be aware of the cause or resolution of such issue). The Section Developer shall keep MDTA informed as to the status of the issue as it works to identify the cause of and correct the issue. MDTA may relax the requirements of Noncompliance Event ID#15.3 (Trip Processing) in Table 25-6 (Operating Period Performance) of the Predevelopment Work Requirements for Trips that are affected by issues that are promptly reported to MDTA in accordance with this Section 1.1.
AutoNDA by SimpleDocs

Related to Unacceptable Customer Service Events

  • CUSTOMER SERVICE ACCESS The Competitive Supplier agrees to provide, or cause to be provided, certain customer services to Participating Consumers. Such services shall be reasonably accessible to all Participating Consumers, shall be available during normal working hours, shall allow Participating Consumers to transact business they may have with the Competitive Supplier, and shall serve as a communications liaison among the Competitive Supplier, the Town, and the Local Distributor. A toll-free telephone number will be established by Competitive Supplier and be available for Participating Consumers to contact Competitive Supplier during normal business hours (9:00 A.M. - 5:00 P.M. Eastern Standard Time, Monday through Friday) to resolve concerns, answer questions and transact business with respect to the service received from Competitive Supplier. The Town will post program-related information on the Town’s website which will be available to Participating Consumers for general information, product and service information, and other purposes.

  • Customer Service Standards The Franchising Authority hereby adopts the customer service standards set forth in Part 76, §76.309 of the FCC’s rules and regulations, as amended. The Grantee shall comply in all respects with the customer service requirements established by the FCC.

  • Customer Service A. PRIMARY ACCOUNT REPRESENTATIVE. Supplier will assign an Account Representative to Sourcewell for this Contract and must provide prompt notice to Sourcewell if that person is changed. The Account Representative will be responsible for: • Maintenance and management of this Contract; • Timely response to all Sourcewell and Participating Entity inquiries; and • Business reviews to Sourcewell and Participating Entities, if applicable.

  • CONTRACTOR CUSTOMER SERVICE REPRESENTATIVE Contractor shall designate a customer service representative (and inform Enterprise Services of the same) who shall be responsible for addressing Purchaser issues pertaining to this Master Contract.

  • Customer Service Support During the Term of this Agreement, VNDS will provide reasonable telephone and e-mail customer service support to Registrar, not Registered Name Holder or prospective customers of Registrar, for nontechnical issues solely relating to the System and its operation. VNDS will provide Registrar with a telephone number and e-mail address for such support during implementation of the Supported Protocol, APIs and Software. First-level telephone support will be available on a 7-day/24-hour basis. VNDS will provide a web-based customer service capability in the future and such web-based support will become the primary method of customer service support to Registrar at such time.

  • Minimum Customer Support Requirements for TIPS Sales Vendor shall provide timely and commercially reasonable support for TIPS Sales or as agreed to in the applicable Supplemental Agreement.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Customer Services Customer Relationship Management (CRM): All aspects of the CRM process, including planning, scheduling, and control activities involved with service delivery. The service components facilitate agencies’ requirements for managing and coordinating customer interactions across multiple communication channels and business lines. Customer Preferences: Customizing customer preferences relative to interface requirements and information delivery mechanisms (e.g., personalization, subscriptions, alerts and notifications).

  • AIN Selective Carrier Routing for Operator Services, Directory Assistance and Repair Centers 4.3.1 BellSouth will provide AIN Selective Carrier Routing at the request of <<customer_name>>. AIN Selective Carrier Routing will provide <<customer_name>> with the capability of routing operator calls, 0+ and 0- and 0+ NPA (LNPA) 555-1212 directory assistance, 1+411 directory assistance and 611 repair center calls to pre-selected destinations.

  • Approved Services; Additional Services Registry Operator shall be entitled to provide the Registry Services described in clauses (a) and (b) of the first paragraph of Section 2.1 in the Specification 6 attached hereto (“Specification 6”) and such other Registry Services set forth on Exhibit A (collectively, the “Approved Services”). If Registry Operator desires to provide any Registry Service that is not an Approved Service or is a material modification to an Approved Service (each, an “Additional Service”), Registry Operator shall submit a request for approval of such Additional Service pursuant to the Registry Services Evaluation Policy at xxxx://xxx.xxxxx.xxx/en/registries/rsep/rsep.html, as such policy may be amended from time to time in accordance with the bylaws of ICANN (as amended from time to time, the “ICANN Bylaws”) applicable to Consensus Policies (the “RSEP”). Registry Operator may offer Additional Services only with the written approval of ICANN, and, upon any such approval, such Additional Services shall be deemed Registry Services under this Agreement. In its reasonable discretion, ICANN may require an amendment to this Agreement reflecting the provision of any Additional Service which is approved pursuant to the RSEP, which amendment shall be in a form reasonably acceptable to the parties.

Time is Money Join Law Insider Premium to draft better contracts faster.