We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Support Process Sample Clauses

Support Process. You must report Your Product problems directly to Our designated Support organization and provide the following information: • the Grant Number; • the location of the Product; • a detailed description of the problem; • a description of the hardware on which the Software is loaded, including any serial number or service tag number where applicable; • the names and versions of any operating systems, networks, and software running with the Software, including patches and fixes; and • technical contact information (including name, phone number and email address). We may request that You take certain actions to determine whether the problem or error is related to the Product, or other item. You must reasonably cooperate with Us during this process.
AutoNDA by SimpleDocs
Support Process a. The support process starts when the Client has submitted a support request and RapidDeploy has opened a new a service ticket. All support actions, metrics and escalations will be linked and recorded against by the service ticket. b. Once a service ticket has been assigned, Tier 1 support will review the support request and assign the appropriate Severity, service level criteria and request type. If the request type is either a bug requiring technical assistance or a new feature request, the service ticket is passed to the development management team for assessment, prioritization and scheduling as part of the development delivery process. c. If the service ticket is for either a non-technical bug or general support request, the service ticket is then assigned to Tier 1 support for resolution. At this point the ticket will be subject to SLA timelines for initial response and updates. RapidDeploy will escalate beyond Tier 1 support as needed in order to resolve the incident in a timely manner. d. During assessment of and on completion / resolution of the service ticket, the Client will be provided with a resolution progress and feedback pertaining to their request. e. Training on the support process and usage of RapidDeploy support tools will be provided during Client onboarding.
Support ProcessAfter submission in the Support Portal, Mendix will analyze the ticket and, if applicable, try to reproduce the incident or evaluate the completeness of the information of a change request. If Mendix determines the root cause of the incident is the App Platform, Mendix will resolve the issue according to the assigned priority, as defined under section 1.7 (Priority Levels). If the root cause of a reported incident is deemed to be an external failure (i.e. the root cause is not the App Platform, but e.g. the (model of the) Mendix Application), Mendix shall inform Customer of such fact and Mendix will have no obligation to resolve such issue. However, in such case however Mendix shall use reasonable efforts in supporting Customer in resolving the incident which may include involving (paid) Mendix Expert Services. Mendix will seek Customer’s written approval and agreement to pay any related fees before performing such services.
Support Process a. When Licensee requires technical support, a CSC support member will open a service ticket, document the nature of the issue, assist the Licensee in collecting logs, screen captures and documenting the sequence of events or steps resulting in the issue to initiate troubleshooting and engage the necessary support resources. b. A strict “one issue per ticket” policy is enforced. This allows the CSC Agility Platform Support Team to work multiple issues simultaneously with the Licensee, ensuring each request or issue is handled appropriately and documented correctly.
Support Process. A. Prioritization. Four Js agrees to use the customer problem Prioritization Method (listed above in Definitions) for classifying customer reported problems that result in Problem Resolution Requests, and for responding to and resolving individual Problem Resolution Requests according to the Service Level Objectives (response, status, resolution times) described below. The customer may reasonably set the problem priority using the definitions in this Agreement.
Support ProcessAfter submission in the Support Portal, Brainial will analyze the ticket and, if applicable, try to reproduce the incident or evaluate the completeness of the information of a change request. If Brainial determines the root cause of the incident in the Software, Brainial will resolve the issue according to the assigned priority, as defined under section 1.7 (Priority Levels). If the root cause of a reported incident is deemed to be an external failure (i.e. the root cause is not the Software, but e.g. an external system or source that connects with the Brainial API), Brainial shall inform Customer of such fact and Brainial will have no obligation to resolve such issue. However, in such cases Brainial shall use reasonable efforts in supporting Customer in resolving the incident which may include involving (paid) Brainial Consultancy Services. Brainial will seek Customer’s written approval and agreement to pay any related fees before performing such consultancy services.
Support Process. On discovering an issue, it is important for the customer to gather the following information, to enable the Support Team to raise a new case and assign it to the appropriate Support Consultant:  Name  Company NameTelephone Number  Description of the problem, including details of any error messages.  Details of what you were doing before the problem occurred.  Details of the system / browser you are using.  Screenshots, if possible.  Any changes to computer, operating system, data or way of working. Contact can be made by telephone 00000 000000), email (xxxxxxx@xxxxxxx.xxx) or via the website contact form (xxx.xxxxxxx.xxx) . Upon receipt of a support request from a customer, the support consultant will first verify that the customer’s organisation qualifies for support for the product concerned and that the customer has received the appropriate level of training for the product in question. The contact details will be verified and the incident details will be collated and a case raised. A unique case number generated by the system will identify each incident. This case number will be communicated to the customer by phone or email and should be noted by the customer for future reference, so that any support consultant can recall the history of case. Where the customer does not qualify for support for the product concerned, interim support will be provided on one occasion only. In these instances, the customer will be advised that support cannot be provided beyond the current query, without valid cover. The customer will be given the option to renew maintenance cover to ensure that support and can be provided going forward. It may be necessary to gather information from a number of sources, to accurately diagnose the issue. This may involve information in relation to the customer’s environment. The consultant will diagnose the issue, and prioritise, respond and resolve in line with our service levels. On successful resolution of the issue, the case will be closed. Please note that Geoplan will close a support case where the customer has not been contactable for three consecutive attempts, or where feedback is expected from the customer, but not received within 5 working days. The Support Team will raise a new case should the customer return to report the same incident.
AutoNDA by SimpleDocs
Support ProcessThe Customer makes a request for support by phone or email. Acknowledgement of all valid requests will be made by means of the ticketing system at the offices of Medusa. The acknowledgement will be made to the originator of the request. Acknowledgement of a support request will usually be made by email Medusa will provide the Customer with a final description of the resolution of support requests.
Support Process. The Client's authorised staff will be provided with access to Catalyst’s web-based Work Request Management System (WRMS). Where the Client requires Catalyst support, the Client’s authorised staff should create a work request in WRMS. To submit a request: a. access WRMS through a web browser at xxxxx://xxxx.xxxxxxxx.xxx.xx with your username and password; b. create a new work request by clicking on the 'New Request' menu link; c. in the 'Brief' text box, enter a short title for the problem/request;
Support Process. Notwithstanding any reference to other online or hotline support services found via any other URL’s, the only applicable contact channels for Maintenance Services related to Mendix Platform Products are found via the Mendix Support Portal, which also includes the telephone numbers for the Support Phone. Incident Reports must be reported by submitting a ticket in the Mendix Support Portal. The Mendix Support Portal provides all information about the progress and status of raised tickets. Critical incidents reported in the Mendix Support Portal have to be followed by a phone call to the Support Phone in order to immediately determine the best communication line while handling the ticket.
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!