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.
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.
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.
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.
Submission of Support Cases a. Mechanism Authorized Customer Contacts may file support cases by submitting support requests to the Immuta Support Website located at xxxxx://xxxxxxx.xxxxxx.xxx (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 xxxxxxx@xxxxxx.xxx 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 and properly categorized; 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.
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.
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.
