Customer Escalation Sample Clauses

Customer Escalation. If the problem is not being addressed in a satisfactory manner, an escalation procedure with 4 contact levels is available for the customers. The sequence should be the one specified in the following table; the timing is left to the Customer discretion; the Customer should however take into consideration the timing of the HER internal escalation procedure as described in 4.6.2. Out of office hours, the Customer may request escalation through the CSC. ============================================================================== CONTACT CONTACT FUNCTION TEL. NUMBER FAX NUMBER TEL. NO. AFTER LEVEL & NAME(S) HOURS --------- ------------------- ------------- ------------- -------------- 1st Level Shift Leader 32-2-▇▇▇-▇▇▇▇ ▇2-2-▇▇▇-▇▇▇▇ ▇▇-2-▇▇▇-▇▇▇▇ --------- ------------------- ------------- ------------- ------------- 2nd Level Brun▇ ▇▇▇▇▇▇▇ 32-2-▇▇▇-▇▇▇▇ ▇2-2-▇▇▇-▇▇▇▇ ▇▇-2-▇▇▇-▇▇▇▇ CSC Manager --------- ------------------- ------------- ------------- ------------- 3rd Level John ▇▇▇▇▇▇▇▇ 32-2-▇▇▇-▇▇▇▇ ▇2-2-▇▇▇-▇▇▇▇ ▇▇-2-▇▇▇-▇▇▇▇ Operations Director --------- ------------------- ------------- ------------- ------------- 4th Level Jan ▇▇▇▇▇▇ 32-2-▇▇▇-▇▇▇▇ ▇2-2-▇▇▇-▇▇▇▇ ▇▇-2-▇▇▇-▇▇▇▇ Managing Director ==============================================================================
Customer Escalation. For Support Tickets involving Critical Priority Errors and High Priority Errors only, if Customer reasonably determines that there is a performance issue in connection with the response provided by Minerva’s initial TSEs, Customer may request escalation of such Support Ticket to Tier-2. If such an Error is still not proceeding to Customer’s reasonable expectations, Customer may escalate the Support Ticket for such Error to Minerva’s Director of Technical Support or the applicable third party vendor. If such escalation does not resolve the issue, ▇▇▇▇▇▇▇ may escalate the issue to its Vice President of Technical Support or, if applicable, within the applicable third party vendor. Support Tickets involving Medium Priority Errors and Low Priority Errors may not be escalated by Customer using the escalation process in this Section.
Customer Escalation. For Support Tickets involving ”Priority 1 – Critical” and ”Priority 2 – High” only, if Customer reasonably determines that there is a performance issue in connection with the response provided by ▇▇▇▇▇▇▇’▇ initial TSEs, Customer may request escalation of such Support Ticket to Tier 2. If such an Error is still not proceeding to Customer’s reasonable expectations, Customer may escalate the Support Ticket for such Error to ▇▇▇▇▇▇▇’▇ Technical Support Manager. If such escalation does not resolve the issue, ▇▇▇▇▇▇▇ may escalate the issue to its Vice President of Professional Services. Support Tickets involving “Priority 3 – Medium” and “Priority 4 – Low” Errors may not be escalated by Customer using the escalation process in this Section.
Customer Escalation. Exodus will notify customers via phone and e-mail of any problem conditions that occur in the tape exchange process. BANDWIDTH REPORTS Part Number EXO-SRBW Description Exodus Bandwidth Reports provide customers with graphical and tabular statistics of their bandwidth usage. Reports are accessible via the web and show traffic volumes between the customer's equipment and the network In addition to providing the traffic volume at a particular instance in time, the reports include summary statistics of maximum, minimum, and 95% loading. This information offers customer a way to monitor usage trends and assist with the capacity planning of server and network resources. Reports Monthly Monthly reports are included with each network service purchased. Monthly reports are produced on the 16th and 1st of the month. On the 16th of the month the report lists usage for each of the prior 15 days. On the 1st of the month, the report provides bandwidth usage for the prior month. Daily Daily reports are made available each day of the month. Reports for the previous day are available by 4:00 AM PDT the following morning. Daily Reports are ordered as an optional service using the part number shown above. Both the Monthly and Daily Reports feature:
Customer Escalation. If the customer believes the incident is not being handled appropriately, they may escalate directly to management by contacting the support team with the escalation request.

Related to Customer Escalation

  • PRICE ESCALATION/DE-ESCALATION (CPI) The County may allow a price escalation provision within this award. The original contract prices shall be firm for an initial one (1) year period. A price escalation/de-escalation will be considered at one (1) year intervals thereafter, provided the Contractor notifies the County, in writing, of the pending price escalation/de-escalation a minimum of sixty (60) days prior to the effective date. Price adjustments shall be based on the latest version of the Consumers Price Index (CPI-U) for All Urban Consumers, All Items, U.S. City Average, non-seasonal, as published by the U.S. Department of Labor, Bureau of Labor Statistics. This information is available at ▇▇▇.▇▇▇.▇▇▇. Price adjustment shall be calculated by applying the simple percentage model to the CPI data. This method is defined as subtracting the base period index value (at the time of initial award) from the index value at time of calculation (latest version of the CPI published as of the date of request for price adjustment), divided by the base period index value to identify percentage of change, then multiplying the percentage of change by 100 to identify the percentage change. Formula is as follows: Current Index – Base Index / Base Index = % of Change CPI for current period 232.945 Less CPI for base period 229.815 Equals index point change 3.130 Divided by base period CPI 229.815 Equals 0.0136 Result multiplied by 100 0.0136 x 100 Equals percent change 1.4% % of Change x 100 = Percentage Change CPI-U Calculation Example: A price increase may be requested only at each time interval specified above, using the methodology outlined in this section. To request a price increase, Contractor shall submit a letter stating the percentage amount of the requested increase and adjusted price to the Orange County Procurement Division. The letter shall include the complete calculation utilizing the formula above, and a copy of the CPI-U index table used in the calculation. The maximum allowable increase shall not exceed 4%, unless authorized by the Manager, Procurement Division. All price adjustments must be accepted by the Manager, Procurement Division and shall be memorialized by written amendment to this contract. No retroactive contract price adjustments will be allowed. Should the CPI-U for All Urban Consumers, All Items, U.S City Average, as published by the U.S. Department of Labor, Bureau of Labor Statistics decrease during the term of the contract, or any renewals, the Contractor shall notify the Orange County Procurement Division of price decreases in the method outlined above. If approved, the price adjustment shall become effective on the contract renewal date. If the Contractor fails to pass the decrease on to the County, the County reserves the right to place the Contractor in default, cancel the award, and remove the Contractor from the County Vendor List for a period of time deemed suitable by the County. In the event of this occurrence, the County further reserves the right to utilize any options as stated herein.

  • Escalation If parties are unable to resolve the issue in a timely manner, as specified above, either Sourcewell or Supplier may escalate the resolution of the issue to a higher level of management. The Supplier will have 30 calendar days to cure an outstanding issue.

  • Non-Escalation Unless otherwise specified within the RFP documents, the unit prices reflected on the contract shall remain firm with no provision for price increases during the term of the contract.

  • Interconnection Customer Compensation If the CAISO requests or directs the Interconnection Customer to provide a service pursuant to Articles 9.6.3 (Payment for Reactive Power) or 13.5.1 of this LGIA, the CAISO shall compensate the Interconnection Customer in accordance with the CAISO Tariff.

  • Emergency Escalation Escalation is strictly for purposes of notifying and investigating possible or potential issues in relation to monitored services. The initiation of any escalation and the subsequent cooperative investigations do not in themselves imply that a monitored service has failed its performance requirements. Escalations shall be carried out between ICANN and Registry Operators, Registrars and Registry Operator, and Registrars and ICANN. Registry Operators and ICANN must provide said emergency operations departments. Current contacts must be maintained between ICANN and Registry Operators and published to Registrars, where relevant to their role in escalations, prior to any processing of an Emergency Escalation by all related parties, and kept current at all times.