Support Escalation Clause Samples
Support Escalation. 8.1. Subject to clause 8.2, if Karantis360 is unable to resolve the Support Request within the timescales detailed in clause 7.1, the Support Request shall, without further notice of either party, become a Major Incident (as defined in clause 7.1 above) and the Target Fix Time for Major Incidents shall apply from the point of such Support Request being escalated.
8.2. If Karantis360 is unable to resolve a Support Request which is classified as a Major Incident within the timescale detailed in clause 7.1, the escalation process in clause 8.1 shall not apply and Karantis360 shall use its best endeavours to provide a Solution as soon as practicable.
Support Escalation. Trintech’s assigned engineering and development resources will receive an unresolved Level 2 Support Issue for resolution. • These additional Trintech resources will work with the Level 2 Support team to resolve Issues related directly to product development. • Issues may require involvement of other teams or departments within Trintech, and Subscriber will be notified accordingly. • Escalation Support is only available 8:00 AM– 6:00 PM CST (Central Standard Time) in the US.
Support Escalation. SS&C shall provide maintenance and support to the version of the Software base system made pursuant to the then current version of SS&C's Chorus Product Support for North America Reference Guide (the “Support Program”), a current copy of which is available at ▇▇▇▇▇://▇▇▇▇▇▇▇.▇▇▇▇.▇▇▇▇▇/choruscustomercenter. SS&C may modify the Support Program from time to time provided, however, that the level of support will not be materially reduced from that offered upon the Effective Date.
Support Escalation. In the event an Incident has not been resolved in a timely manner, or an Incident that is resolvable from the FAQs supplied by Entrust Datacard is reported to Entrust Datacard as a Second Line Support Incident multiple times, Entrust Datacard or MSP may convene a meeting between the parties' management to establish a plan to correct the situation. Each party may change its management representative at any time upon written notice to the other party.
Support Escalation. In the event that an Incident increases in its impact to the Client or that allocated resources are inadequate to provide a solution to Client, PMWeb shall escalate Incidents to an appropriate level of its organization. Purposes of escalation shall be to obtain additional expertise or resources, and/or re-evaluate priority/impact.
Support Escalation. Process Client acknowledges that there will be situations where PeopleSupport eReps, supervision and management will be unable to resolve a voice or email inquiry. In such circumstances, the issue will be assigned to the appropriate internal Client department who will resolve the issue in accordance with established policies and procedures. A detailed Contact escalation process will be documented in the Client provided training manual. PeopleSupport staff will be trained to handle escalations from eReps. As a result, *** not exceed *** received ***.
Support Escalation. SOLUS shall respond to Customer’s requests for service by issuing service tickets (“Service Tickets”). Service Tickets shall be obtained by the Customer’s designated contact person(s) by: (a;) an email to ▇▇▇▇▇▇▇@▇▇▇▇▇.▇▇▇▇ ; or (c) by speaking with a SOLUS Helpdesk representative by telephone. Each request for service shall be assigned a Service Ticket number for tracking purposes.