Requesting Support Sample Clauses

Requesting Support. 3.1 All requests for Support from the Customer must be made via telephone on 00000 000000 or e-mail to xxxxxxxx@xxxxxxx.xx.xx 3.2 The Customer must inform Telemat IT Support of any Incidents as soon as is practically possible. If there is a delay informing Telemat IT Support of obvious warning signs then the fault may grow and cause additional impact. 3.3 Upon receiving notification regarding an issue with the Customer’s System, the issue will be logged as an Incident with an allocated Incident reference number. The Incident reference number along with details of the Incident will be provided to the Customer. 3.4 In the event of the Customer wishing to query the progress of an Incident, the Customer must be able to state the specific Incident reference number to enable Telemat IT Support to identify the Incident in question.
AutoNDA by SimpleDocs
Requesting Support. 3.1 All requests for Support from the Customer must be made via e-mail to our centralised support logging system via xxxxxxx@x000xxxxx.xx.xx
Requesting Support. Any and all Client end-users are authorized to request service using the processes and provisions detailed within this Agreement unless otherwise noted herein.
Requesting Support. For support requests for which a resolution is not found in the Documentation, Customer can submit a ticket, through the Support Web Site.
Requesting Support. The ‘Client’ is expected to test fully all billing scenarios before final invoices are sent out to customers. This especially includes testing after any change in their data that was the result of modifications the ‘service provider’ might have done following a request for support.
Requesting Support. Problems and questions relating to BookWise Solutions Limited Products should be communicated to BookWise Solutions by one of the approved methods. • Email - xxxx@xxxxxxxxxxxxxxxxx.xxx • Phone - 0000 000 0000 A support call is more likely to be resolved quickly where the report contains a detailed description of the problem and how to reproduce it.
Requesting Support. 11.1 Customer may request SA for support services in the event the SaaS Services provided under the Agreement do not substantially conform to the specifications set forth in the Agreement. Prior to requesting support services, Customer must comply with all published operating and troubleshooting procedures for the SaaS Services. If such efforts are unsuccessful in eliminating the issue, Customer shall then promptly notify SA of the issue.
AutoNDA by SimpleDocs
Requesting Support. 2.1 All requests for Support from the Customer must be made via the xxxx://xxxxxx.xxxxxx.xxx/ portal. Links for the GRi Kayako support platform may also be located on the GRi homepage (xxx.xxxxxx.xxx) and the online store (xxxx://xxxxx.xxxxxx.xxx). 2.2 Upon receiving notification regarding an issue with the Customer’s System, the issue will be logged as an Incident with an allocated Incident reference number. The Incident reference number along with details of the Incident will be stated to the Caller. 2.3 In the event of the Customer wishing to query the progress of an Incident, the Customer must be able to state the specific Incident reference number to enable GRi to identify the Incident in question. 2.4 GRi retains the right to install 3rd party software on the Customer’s System to facilitate the remote connection and delivery of Support to the Customer. In accordance with this right: a. If at any stage following the commencement of the Agreement the Customer refuses GRi the right to install / use 3rd party software upon their System for the purposes stated in clause 2.4 above, GRi retains the right to revise any pricing previously agreed for the Agreement or to terminate the Agreement. b. GRi warrants to the Customer that all 3rd party software installed upon the Customers System for the purpose stated in clause 2.4 above will be licensed accordingly by GRi. c. The ownership of 3rd party software installed upon the Customer’s System for the purpose stated in clause 2.4 above will remain vested in GRi. d. The Customer can request that GRi demonstrate and explain what 3rd party software it intends to install on the Customer’s System and for what purpose it is intended. 2.5 No guarantees or commitments will be given regarding the length of time required for resolving Incidents. 2.6 The customer will provide GRi or its representative with unrestricted access to the system and will provide such further facilities and assistance as the representative may require to carry out the work. GRi will not be liable when its representative cannot provide support as a result of the Customer failing to provide such facilities or assistance.
Requesting Support. 3.1 All requests for Support from the Customer must be made via e-mail to our centralised support logging system via xxxxx@xxxxxxxxxxx.xx.xx. • 3.2 The Customer must inform LOUDCROWD IT of any Incidents as soon as is practically possible. If there is a delay informing LOUDCROWD IT of obvious warning signs then the fault may grow and cause additional impact.
Requesting Support. 3.1 All requests for Support from the Customer must be made via telephone on 0000 000 0000 , online at xxx.xxxxxxxxxx.xxx / dedicated helpdesk provided by PENTRE TECH Ltd or email support xxxxxxx@xxxxxxxxxx.xxx 3.2 The Customer must inform PENTRE TECH LTD of any Incidents as soon as is practically possible. If there is a delay informing PENTRE TECH LTD of obvious warning signs then the fault may grow and cause additional impact which PENTRE TECH LTD accepts no liability for.
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!