Support Incidents Sample Clauses

Support Incidents. 5.1. Participating Institution shall report all issues via Salesforce, through the creation of a Salesforce Case (a "Support Case"). Level I and II issues, as described in 5.2 below, should also be reported to 00X0xxx@xxxxxxxxxxxxx.xxx.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
Support Incidents. A single support incident may involve several e-mails and off-line work in order to be resolved. You agree to provide BALKAN App with detailed information about the issue encountered and cooperate with BALKAN App's requests for additional information as they attempt to resolve the issue. BALKAN App support engineers will make reasonable efforts to resolve your support issues; however, BALKAN App does not guarantee that all support issues will be resolved. Bug reports and product feature suggestions are not considered support incidents, and BALKAN App is not obligated to acknowledge or address such bug reports and/or product feature suggestions.
Sample 1Sample 2Sample 3See All (5)
Support Incidents. 5.1. Customer shall report all issues via Salesforce, through the creation of a Salesforce Case (a "Support Case"). Level I and II issues, as described in 5.2 below, should also be reported to 00X0xxx@xxxxxxxxxxxxx.xxx.
Sample 1
Support Incidents. During the Term, Subscriber shall report problems to Sectigo by telephone at Sectigo’s designated support telephone number, email address, or website form, and shall furnish a full description of the problem. Subscriber shall, upon Sectigo’s request, also provide written problem descriptions and supporting technical information as required by Sectigo. Support Incidents submitted via email will be answered via email. Upon receipt of all necessary information, the Support Incident shall be classified by Sectigo into one of the four categories described in Table A. Sectigo shall respond to Support Incidents in accordance with the Priority Level assigned by Sectigo. Table B sets forth the targeted time for Sectigo to provide actions for each Support Incident based upon the Priority Level assigned to the Support Incident, as measured from receipt of the Support Incident from Subscriber to the target resolution, respectively. For a Support Incident classified as Low Priority, the Support Incident will be resolved by providing an answer to the question regarding the use or operation of SCM. For Support Incident classified as L1 Critical Priority, L2 High Priority, or L3 Medium Priority, Sectigo shall attempt to provide a bug fix or workaround as per the Performance Standards. A Support Incident may require the involvement of several Designated Contacts or a direct one to one interaction with a single technician. Response Times and target resolutions exclude code fixes, customized configuration, and product enhancements, and may include workaround solutions based on the type of Support Incident and Priority Level. Subscriber acknowledges that the target resolution of a Support Incident may vary depending on the nature and seriousness of the Support Incident, and that no guarantee is made by Sectigo as to the time within which such resolution will be completed. Sectigo may choose to defer resolution of Support Incidents until release of the next major or minor update of the Sectigo product or service.
Sample 1
Support Incidents 
Sample 1

Related to Support Incidents

  • Data Incidents Merchant must report all instances of a Data Incident (as defined in the American Express Merchant Operating Guide) immediately to ISO after discovery of the incident. Merchant must ensure data quality and that Transaction Data and customer information is processed promptly, accurately, and completely, and complies with the American Express Technical Specifications. THE FOLLOWING SERVICES ARE PROVIDED BY ISO ONLY. Bank shall not have any obligation or liability of any nature in connection with such services. PART THREE

  • Reporting Incidents The Interconnection Parties shall report to each other in writing as soon as practical all accidents or occurrences resulting in injuries to any person, including death, and any property damage arising out of the Interconnection Service Agreement.

  • Significant Incidents In addition to notifying the appropriate authorities, Grantee will submit notice to the SUD email box, XxxxxxxxxXxxxx.Xxxxxxxxx@xxxx.xxxxx.xx.xx and Substance Use Xxxxxxxx@xxxx.xxxxx.xx.xx significant incidents involving substantial disruption of Grantee’s program operation or affecting or potentially affecting the health, safety or welfare of the System Agency funded clients or participants within three (3) calendar days of discovery.

  • Security Incidents 11.1 Includes identification, managing and agreed reporting procedures for actual or suspected security breaches.

  • Reporting Security Incidents The Business Associate will report to the County any Incident of which the Business Associate becomes aware that is:

  • Breaches and Security Incidents During the term of the Agreement, CONTRACTOR 27 agrees to implement reasonable systems for the discovery of any Breach of unsecured DHCS PI and PII 28 or security incident. CONTRACTOR agrees to give notification of any beach of unsecured DHCS PI 29 and PII or security incident in accordance with subparagraph F, of the Business Associate Contract, 30 Exhibit B to the Agreement.

  • Security Incident “Security Incident” means the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system.

  • Reporting Unsuccessful Security Incidents Business Associate shall provide Covered Entity upon written request a Report that: (a) identifies the categories of Unsuccessful Security Incidents; (b) indicates whether Business Associate believes its current defensive security measures are adequate to address all Unsuccessful Security Incidents, given the scope and nature of such attempts; and (c) if the security measures are not adequate, the measures Business Associate will implement to address the security inadequacies.

  • Security Incident Response Upon becoming aware of a Security Incident, MailChimp shall notify Customer without undue delay and shall provide timely information relating to the Security Incident as it becomes known or as is reasonably requested by Customer.

  • Non-Grievability No dispute over a claim for any benefits extended by this Health and Welfare Fund shall be subject to the grievance procedure.

Time is Money Join Law Insider Premium to draft better contracts faster.