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
AutoNDA by SimpleDocs
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. 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. To receive the support defined in this document, requestors must do one of the following: o Self-serve support via the IT Knowledgebase at xxx.xxxxxx.xx/xx o Submit a web form to request equipment & software installation (Service Requests) (xxxx://xxx.xxxxxx.xx/it/forms) o Contact the IT Services Service Desk for any IT related issues (incidents) at 000-000-0000 o Send an email to XXXxxxxxx@xxxxxx.xx o Visit the ITS Walk-in Service Desk  Downtown campus location: 000 Xxxxxxxxxx Xxxx, Xxxx 000  Xxxxxxxxx campus location: Xxxxxxxxx Xxxxxxx Building, Room MS2-025  When making the help request, include the following: o Clearly identify yourself (or whom the request is about)  Main contact, Phone #, Building/Room #. o Clearly define the problem o The exact text of any error message o Who is experiencing the problem o On what computer o How it impacts the person's work 8 Support Tickets  New help requests will be recorded as Support Tickets in the ITS ticketing system.  Support Tickets remain open until the request is completed, or incident resolved.  The ITS Service Desk will provide regular status updates throughout the ticket life cycle.  Customers can check on the status of a Support Ticket by calling the ITS Service Desk during its open hours.
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. All requests for Support from the Customer must be made via e-mail to our centralised support logging system via xxxxxxx@xxxxxxxxx.xxx The Customer must inform Paperflow of any Incidents as soon as it is practically possible. If there is a delay in informing Paperflow of obvious warning signs then the fault may grow and cause additional impact. Upon receiving notification regarding an issue with the Customer’s System, the issue will be logged as an Incident with an allocated Ticket number. The Ticket number along with details of the Incident will be notified to the Customer. The Supplier will use best endeavours to respond to all calls for service within the time specified. In the event of the Customer wishing to query the progress of an Incident, the Customer must be able to state the specific Ticket number to enable Paperflow to identify the Incident in question. Delivery of Support Support will be delivered by Paperflow to the Customer in accordance with the Support Schedule. The Support Schedule will be stated in the Support Service Agreement. Whilst working on Incidents, Consultants will keep a record of the time they spend and the actions taken. This information will be logged in the Paperflow Support Application under the specific Ticket number. No guarantees or commitments will be given regarding the length of time required for resolving Incidents.
Requesting Support. An employee of the CUSTOMER that requires assistance must contact the ICT Helpdesk by calling +00(0)00 000 0000 / 0861 S-E-B-A-T-A / 0861 73 22 82 during support hours or by sending an email to xxxxxxxxxxx@xxxxxx.xx.xx. The Helpdesk will log and track every call, and make information about each call readily available for the CUSTOMER in the monthly report. If the CUSTOMER wishes to escalate calls logged with the Helpdesk, the following person(s) should be contacted in the following order:
AutoNDA by SimpleDocs
Requesting Support. Web Support is provided primarily by opening a ticket via our dedicated support ticket system: xxxxx://xxxxxxxxxxxxxxxx.xxx/support. You will need to register your free account if you do not already have one with us. After you have opened a ticket an automated response will be sent confirming that your request has been received and a reference number will be provided. Please quote this number if following up a support ticket. Requests made via the support ticket system are processed during normal hours of operation as described in section 4. below. If submitting more than one support request of a similar priority level you must tell us if you want these dealt with in a certain order, otherwise, they will generally be processed in the same order that we receive them. Where we receive multiple requests for work from different people at the same company, these will generally be dealt with in the order they are received, unless you tell us otherwise. Where a support request is received that is of a higher priority than an existing request, unless you tell us otherwise, the higher priority request will normally be dealt with first.
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).
Requesting Support. Wazuh Technical Support Engineers will provide Support by remote assistance. Except in the case of Priority 1 issues, requests for Support must be made through Wazuh’s Support Portal. A Wazuh Technical Support Engineer will respond via email or phone. Priority 1 issues may be reported by phone. Priority Business Impact 1 Critical Yes Trouble condition where a Wazuh platform central component is completely out of service, or the Wazuh platform is causing business impact to the customer. 2 High Yes Trouble condition where a Wazuh platform central component, or a deployed Wazuh agent, is not fully functional and is causing business impact to the customer. 3 Medium No Trouble condition where a Wazuh platform central component, or a deployed Wazuh agent, is not fully functional but is not causing business impact to the customer. 4 Low No Any condition or request for assistance that is not causing business impact to the customer. This priority is also used for information exchange and feature requests.
Time is Money Join Law Insider Premium to draft better contracts faster.