Neo4j AuraDB and AuraDS Enterprise (“Service”) shall be subject to the following Enterprise Support provisions for the duration of Subscriber’s subscription term:
Subscriber is expected to manage “First Line Support” services for their own end users of the Service. First Line Support includes providing direct responses to all requests relating to performance, functionality and operation raised by users regarding the Service.
If, after reasonable commercial efforts, Subscriber is unable to diagnose or resolve problems or issues in the Service, Subscriber may then contact Neo4j for “Second Line Support” that includes Service Levels 2 through 4 below. Subscriber must use all commercially reasonable efforts to provide Neo4j with the necessary access required (e.g. access to servers, log files, etc.) to verify that observed issues can be replicated and originate in the Service in order to be provided Second Line Support.
Ticket severity levels are assigned during ticket creation. Severity assignment will be validated with Subscriber by the Neo4j Customer Support Engineer and is based on the technical and business impact of Subscriber’s technical issue as outlined below. Neo4j Customer Support, at their sole discretion, may upgrade or downgrade the severity of the ticket depending on developments during the ticket flow process. For example, if available, a temporary resolution may be provided to mitigate the material impact of a given problem resulting in the reduction of the severity of a ticket. Severity levels will also be adjusted downward as the technical issue is mitigated or if Subscriber does not engage in like-effort.
The production use of the Service is stopped or so severely impacted that the user of the Service cannot reasonably continue work. The user of the Service is experiencing a complete loss of service. The operation is mission critical to the business and the situation is an emergency.
A Severity 1 service request has one or more of the following characteristics:
Neo4j will use commercially reasonable efforts to respond to Severity 1 service requests within the Response Time Guidelines specified below. When Neo4j determines that the issue is indeed a Severity 1, Neo4j will employ commercially reasonable efforts to resolve the issue, including the engagement of engineers on a 24×7 basis as long as useful progress can be made. Whilst a Severity 1 service request remains active, Neo4j will assign a designated point of contact to Subscriber, who will be available 24×7 for Enterprise Support issues. During this same period, Subscriber is required to provide Neo4j with a contact, available 24×7 for Enterprise Support, and reachable via email and phone, to assist with data gathering, testing, and applying fixes. Subscriber will make all commercially reasonable efforts to provide Neo4j with the necessary troubleshooting materials (e.g. application log files, client error messages, etc.). When requested materials are not provided in a timely manner, Neo4j is unable to guarantee the quality of support and cannot be held accountable for delay in resolution.
Please allocate Severity 1 classification with great care, so that valid Severity 1 situations obtain the necessary resource allocation from Neo4j.
The user of the Service is experiencing a severe loss of service. Important features are unavailable with no acceptable workaround; however, operations can continue in a restricted fashion. The operation is mission critical to the business.
Neo4j will use commercially reasonable efforts to respond to Severity 2 service requests within the Response Time Guidelines set forth below. When Neo4j determines that the issue is Severity 2, Neo4j will employ commercially reasonable efforts to resolve the issue, including the engagement of engineers within local business hours of Subscriber’s region, until the issue is resolved or as long as useful progress can be made. While a Severity 2 service request remains active, Neo4j will assign a designated point of contact to Subscriber, who will be available within local business hours*. During this same period, Subscriber is required to provide Neo4j with a contact, available within their local business hours and reachable via email, to assist with data gathering, testing, and applying fixes. Subscriber will make all commercially reasonable efforts to provide Neo4j with the necessary troubleshooting materials (e.g. application log files, client error messages, etc.). When requested materials are not provided in a timely manner, Neo4j is unable to guarantee the quality of support and cannot be held accountable for delay in resolution.
The user of the Service is experiencing a minor loss of service. The impact is an inconvenience, which may require a workaround to restore functionality.
Neo4j will use commercially reasonable efforts to respond to Severity 3 service requests within the Response Time Guidelines set forth below.
Subscriber requests information, an enhancement, or documentation clarification regarding the Service but there is no impact on the operation of the Service. The user of the Service is experiencing no loss of service. The result does not impede the operation of a system. Neo4j will use commercially reasonable efforts to respond to Severity 4 service requests within the Response Time Guidelines set forth below.
|
Enterprise Support |
|
|
Severity 1 |
< 1 hour |
|
Severity 2 |
< 4 business hours * |
|
Severity 3 |
< 8 business hours * |
|
Severity 4 |
< 8 business hours * |
Guidelines for service request escalation from Subscriber’s First Line Support to Neo4j’s Second Line Support and escalation within Neo4j are the following Service Levels:
The Subscriber is expected to manage First Line Support services for their own end users of the Software. First Line Support includes providing direct responses to all requests relating to performance, functionality and operation raised by users regarding the Software. If, after reasonable commercial efforts, the customer is unable to diagnose or resolve problems or issues in the Software, the customer may then contact Neo4j for “Second Line Support” that includes Levels 2 and 3 below.
A Neo4j Support Engineer receives information on an issue and analyzes the symptoms. They will engage in appropriate troubleshooting practices, and propose solutions or further investigative actions accordingly. Neo4j Support Engineers will, as needed, conduct advanced troubleshooting and analysis in collaboration with Neo4j Aura Site Reliability Engineers (“SREs”) and assigned Subscriber resources. Investigative actions will be prioritized and managed in order to address the issue. Subscriber is required to make all commercially reasonable efforts to provide Neo4j with access to systems and materials (log files, etc.) as required to diagnose and reproduce the issue.
The most critical or complex issues are addressed at Level 3. All information and actions taken in Level 2 are shared with the Neo4j Product Engineering team, who engage in further research and analysis, provide Level 2 with feedback, guidance and when appropriate propose solutions to be developed and provide detailed estimates for delivery.
Escalation between service levels 2 and 3 will be made at the discretion of Neo4j, based on the results of investigation into the issue.
Neo4j reserves the right to change, alter, replace or otherwise modify these Support Terms at any time but no such change(s) shall materially reduce or diminish the level of Support provided to the Customer. The date of last modification is stated at the end of these Support Terms.
Last modified: September 22, 2023
