Submission of Support Cases Sample Clauses

The 'Submission of Support Cases' clause defines the process by which a party can report technical issues or request assistance from the service provider. Typically, this clause outlines the required method for submitting support requests, such as through an online portal, email, or phone, and may specify the information that must be included, like a description of the issue and relevant account details. Its core practical function is to ensure that support requests are communicated efficiently and consistently, enabling timely and effective resolution of problems.
Submission of Support Cases. Each Support Case shall; (a) designate the Severity Level of the Error in accordance with the definitions in Table 1, (b) identify the Customer’s Account that experienced the error, (c) include information sufficiently detailed to allow Snowflake Support to attempt to duplicate the Error (including any relevant error messages), and (d) provide contact information for the Customer Contact most familiar with the issue. Unless Customer expressly designates the Severity Level, the Support Case will default to Severity Level four. If Customer believes the issue to be related to Client Software (as defined in the Agreement), then the Support Case shall also include the applicable Client Software log files. If Customer Contacts submit Support Cases related to enchancement or feature requests, Snowflake shall treat those tickets as closed once the request has been forwarded internally.
View SourceView Similar (4)
Submission of Support Cases. Each Support Case shall; (a) designate the Severity Level of the Error in accordance with the definitions in Table 1, (b) identify the Customer’s Account that experienced the error, (c) include information succinctly detailed to allow Amorphic Support to attempt to duplicate the Error (including any relevant error messages), and (d) provide contact information for the Customer Contact most familiar with the issue. Unless Customer expressly designates the Severity Level, the Support Case will default to Severity Level four. If Customer believes that the issue to be related to Client Software (as defined in the Agreement), then the Support Case shall also include the applicable Client Software log files. If Customer Contacts submit Support Cases related to enhancement or feature requests, Cloudwick shall treat those tickets as closed once the request has been forwarded internally.
View SourceView Similar (3)
Submission of Support Cases. Each Support Case shall; (a) designate the Severity Level of the Error in accordance with the definitions in Table 1, (b) identify the Customer’s account that experienced the error, (c) include information sufficiently detailed to allow Apollo to duplicate the Error (including any relevant error messages), and (d) provide contact information for the Customer Contact most familiar with the issue. Unless Customer expressly designates the Severity Level, the Support Case will default to a P4 Error.
View SourceView Similar (2)
Submission of Support Cases. Customer Contacts may submit a support request to the iplicit support email address or other means as may be designated by iplicit (“iplicit Support Portal”) and the iplicit support representative will determine the severity level based on the description provided by the Customer Contacts according to Table 2.2 above (“Severity Level”) solely for purposes of having the support request submitted (collectively, a “Support Case”). Customer Contacts will ensure that each Support Case submitted will; (a) designate the initial Severity Level of the Error in accordance with the definitions in Table 2.2 above, (b)identify the Services that experienced the error, (c) include information sufficiently detailed to allow iplicitto duplicate the Error (including any relevant error messages), and (d) provide contact information for the Customer Contact most familiar with the issue.
View SourceView Similar (2)
Submission of Support Cases a. Mechanism Authorized Customer Contacts may file support cases by submitting support requests to the Immuta Support Website located at ▇▇▇▇▇://▇▇▇▇▇▇▇.▇▇▇▇▇▇.▇▇▇ (or a successor URL that may be designated by Immuta). If the Customer Contacts cannot use the Immuta Support Website due to technical issues, the Customer Contact may email ▇▇▇▇▇▇▇@▇▇▇▇▇▇.▇▇▇ to initiate or progress a case. Please note that any email submission will not be subject to SLA timetables until the email has been forwarded to the Immuta support system; Immuta will make reasonable efforts to minimize this processing time. Any email must indicate intention to file a support case and the information detailed for support cases below, or it will not be subject to SLA timetables.
View SourceView Similar (2)
Submission of Support Cases. Each Support Case shall; (a) designate the Severity Level of the Error in accordance with the definitions in Table 1, (b) identify the Customer Account that experienced the error, (c) include information sufficiently detailed to allow Snowflake Support to attempt to duplicate the Error (including any relevant error messages, but not export-controlled data, personal data (other than as required herein), sensitive data, other regulated data, or Customer Data), and (d) provide contact information for the Customer Contact most familiar with the issue. Information submitted in a Support Case is not Customer Data. Unless Customer expressly designates the Severity Level, the Support Case will default to Severity Level 4. If Customer believes the issue to be related to Client Software (as defined in the Agreement), then the Support Case shall also include the applicable Client Software log files. If Customer Contacts submit Support Cases related to enhancement or feature requests, Snowflake shall treat those tickets as closed once the request has been forwarded internally.
View Source
Submission of Support Cases. Each Support Case shall (a) identify the Customer’s account that experienced the error, (b) include information sufficiently detailed to allow Virtana to duplicate the Error (including any relevant error messages), and (c) provide contact information for the Customer Contact most familiar with the issue. The Support Case will default to a Normal (P3) priority and can be modified to a higher priority by Virtana Support or modified to a lower priority by mutual agreement between the Customer and Virtana Support.
View Source

Related to Submission of Support Cases

  • Submission of Agreement Submission of this Lease to Tenant for signature does not constitute a reservation of space or an option to acquire a right of entry. This Lease is not binding or effective until execution by and delivery to both Landlord and Tenant.

  • SUBMISSION OF BID Bids may be submitted via the electronic submission portal at: ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇▇.▇▇▇/buyer/691, or in the Procurement Division; Internal Operations Centre II, ▇▇▇ ▇. ▇▇▇▇▇ ▇▇▇▇▇▇; ▇▇▇ ▇▇▇▇▇, ▇▇▇▇▇▇▇, ▇▇ ▇▇▇▇▇, prior to the submission deadline. Bids will be opened per the public meeting notice. If bid will be mailed or hand delivered, ensure it is secured in a sealed envelope, addressed as follows: A. Invitation for Bids Number B. Due Date of Bid Submittal C. Name of Bidder

  • Submission of Grievances A. Any employee or group of employees shall have the right to present a grievance. No employee or group of employees shall be hindered from or disciplined for exercising this right. B. If any two (2) or more employees have essentially the same grievance they may, and if requested by the County must, collectively present and pursue their grievance if they report to the same immediate supervisor. C. If the grievant is a group of more than three (3) employees, the group shall, at the request of the County, appoint one (1) or two (2) employees to speak for the collective group. To be considered a grievant in a group grievance, each employee must be individually identified as a grievant when the grievance is submitted at Step 2.

  • SUBMISSION OF AUDIT Within 30 days after receipt of the independent certified public accountant's report or nine months after the end of the fiscal year, Grantee shall submit electronically one copy of the Single Audit or Program-Specific Audit to DFPS as directed in this Contract and another copy to: ▇▇▇▇▇▇_▇▇▇▇▇_▇▇▇▇▇▇@▇▇▇▇.▇▇▇▇▇.▇▇▇.

  • Submission of Grievance Information a. Upon appointment of the arbitrator, the appealing party shall, within five (5) days after notice of appointment, forward to the arbitrator, with a copy to the School Board, the submission of the grievance which shall include the following: 1. The issues involved. 2. Statement of the facts. 3. Position of the grievant. 4. The written documents relating to Section 5 of the grievance procedure.