1. Creating and managing support engagements
The Subscriber may open a support engagement by visiting the Choreo Labs online customer portal at https://support.choreolabs.com. New Subscribers are provided instructions on accessing the Choreo Labs customer portal and other available engagement methods. There are no limits on customer account authorized users. A designated administrator user of the Subscriber will be granted access to the customer portal. This administrator user will have the authority to add or remove other users from the customer portal.
To ensure we can properly address your issue, please ensure that you:
- Correctly classify the issue either as a Case, Security Report Analysis, Service Request or otherwise.
- Provide an initial Severity Level for Cases.
- Identify the specific deployment and products affected or involved.
- Provide sufficient information with your report so Choreo Labs can replicate or otherwise understand the issue and respond appropriately.
- Respond promptly to outreach from Choreo Labs's support team to provide any additional information.
- Work with stakeholders in your organization to ensure their participation as necessary to reach a satisfactory outcome.
2. Support engagement types
A Choreo Labs Subscription includes access to a customer account, which handles distinctive types of engagements:
A "Case" is a dedicated support engagement focused on product-specific technical resolution or guidance. A Case is used to investigate unexpected product behavior or to clarify functional usage of Choreo Labs products.
A "Case" with severity S0-S3 represents a failure of one of the specific production or pre-production deployments (if applicable) covered by your Subscription. A production deployment is a system that performs, or assists in performing, legally binding transactions and where a failure of a system in production will have an immediate economic impact on the end users and on the organization. A pre-production system is part of a release management system encompassing staging, testing, or QA deployments.
A "Case" with severity S4 ("Query") provides general technical support for Choreo Labs products and languages. Queries may represent questions about features, usage, functional implementation, or best practices, as may arise during evaluation, development, or migration activities. A Query need not be linked to a specific production or pre-production deployment.
A "Security Report Analysis" involves the analysis of reports generated from security vulnerability scans conducted on specific production or pre-production deployments. Choreo Labs will open a Case with appropriate severity for any confirmed vulnerabilities detected during this analysis process. These cases track the resolution of the vulnerability.
A "Service Request" A request submitted by a Subscriber of a Managed Deployment for a task to be performed on the Managed Deployment, including requests for changes to the deployment or retrieval of information from the deployment.
Apart from the above engagement types, Subscribers can also engage with "Change Request" records which are used to track changes of Managed Deployments. Change Requests are created by Choreo Labs in response to a Service Request or for a change initiated by Choreo Labs.
3. Service levels
For each reported issue Choreo Labs endeavors to respond to and resolve the Case as quickly as possible, within the Target Response Time, Target Workaround Time (if applicable), and Target Resolution Time (if applicable) associated with a Cases's Severity Level. In the event that a Workaround is not reached for a Case within the Target Workaround Time, or a resolution is not reached within the Target Resolution Time, taking into account any delays in Subscriber's provision of necessary information, the Case will be escalated to the Choreo Labs executive team and a support "war team" comprised of Choreo Labs support engineer(s), Choreo Labs executive(s), and Subscriber representative(s) will be convened and a response plan will be established, including technical assessment, mitigation strategy evaluation, resource allocations, and status update frequency. The support team will work continuously under the direction of the war team until a final resolution of the Case is reached.
Enterprise support plan service levels
| Hours of coverage | 24x7x365 | |||
|---|---|---|---|---|
| Cases with Severity S0-S3 | S0* | S1 | S2 | S3 |
| Target Response Time | 15 minutes | 1 hour | 4 hours | 6 hours |
| Target Workaround Time | 4 hours | 24 hours | 48 hours | 72 hours |
| Target Resolution Time | 48 hours | 48 hours | 72 hours | 1 Business Week |
| Status Update Frequency | 4 hours | |||
| Environment | prod + pre-prod | prod + pre-prod | prod + pre-prod | prod + pre-prod |
| Cases with Severity S4 | ||||
| Target Response Time | 1 Business Day | |||
| Target Resolution Time | best efforts | |||
| Limits | 100 hours | |||
| Security Report Analysis | ||||
| Target Response Time | 1 hour | |||
| Target Completion Time | 2 Business Weeks | |||
| Service Request | ||||
| Target Response Time | 1 Business Day | |||
| Target Completion Time | best efforts | |||
* S0 priority is applicable for Managed Deployments only.
Basic support plan service levels
| Hours of coverage | Americas: 12x5 (7:00 a.m.-7:00 p.m. ET M-F)EMEA: 12x5 (7:00 a.m. -7:00 p.m. GMT M-F)ME: 12x5 (7:00 a.m.-7:00 p.m. GMT S-T)APAC: 12x5 (7:00 a.m. -7:00 p.m. IST M-F) | ||
|---|---|---|---|
| Cases with Severity S1-S3 | S1 | S2 | S3 |
| Target Response Time | 4 hours | 6 hours | 8 hours |
| Target Workaround Time | 48 hours | 72 hours | 1 Business Week |
| Environment | production only | production only | production only |
| Cases with Severity S4 | |||
| Target Response Time | 1 Business Day | ||
| Limits | 25 hours | ||
| Security Report Analysis | |||
| Target Response Time | 4 hours | ||
| Target Completion Time | 3 Business Weeks | ||
4. Case severity
A Subscriber makes the initial determination of the severity level of Cases, pursuant to the severity of impact.
If a Case is misclassified with respect to severity level or the type of Case, the support team, in consultation with the Subscriber, will reclassify the Case accordingly.
| Case Severity Level Guidelines | |
|---|---|
| Severity Level 0 (S0): Catastrophic |
|
| Severity Level 1 (S1): Critical |
|
| Severity Level 2 (S2): High |
|
| Severity Level 3 (S3): Medium |
|
| Severity Level 4 (S4): Low |
|
5. Scope
To be in scope for support, a Case must affect the operation of the specific Supported Choreo Labs Product instances associated with, and within the usage limits defined by, the Subscription.
The scope of a Case with Severity S4 (Query) encompasses Choreo Labs products applicable to the project. Queries arising from completely different projects are not in scope – distinct projects (different goals, business units, development or operational teams) should have distinct Subscriptions.
Cases with Severity S4 (Query) are subject to maximum hourly Query Support Limits as specified in the Subscription Order Form. All hours expended by Choreo Labs in reaching a satisfactory resolution are counted towards this limit, except for hours expended by Choreo Labs in developing a fix for a product, connector, migration script, or documentation where the error or omission is so severe that it prevents the products from being used at even a basic level.
Security Report Analysis cases are limited in scope to requests for analysis of security reports specifically relevant to or generated for Subscriber's deployments of Choreo Labs products. Resolution of vulnerabilities is not within scope; Incidents will be spawned for any confirmed vulnerabilities.
Choreo Labs will investigate issues raised relating to custom product extensions. However, resolutions to such issues may be outside Choreo Labs's direct control. Changes to customized code are at Choreo Labs's discretion, and we may suspend the SLA for such incidents. A full resolution to an issue in a custom product extension may require a consulting engagement.
A resolution to a Case may in some cases consist of advice to seek a solution elsewhere – namely when the issue is caused by a hardware failure, third-party software, Choreo Labs products that have been heavily modified outside the many well-documented and supported extension mechanisms, attempts to use the software in an environment or for purposes for which it was not designed or well outside the published specs, issues that are effectively requests for consultancy services, or if no progress can be made without an onsite visit (unless your subscription provides for this feature).
We may suspend the SLA for a Case – or for the entire support account if the issue isn't addressed promptly – if your Subscription lapses, if we find you are using any Choreo Labs software in production without a subscription (even if the issue doesn't directly affect the unsupported software), if you have exceeded any limits defined in your Subscription, if you have failed to conform to applicable license terms, if you are using the support system improperly or abusively, or if you are using the software for illegal purposes.
For us to provide good service, we often need your help with the Case: prompt response to requests for information through our support system, following our advice or instruction on a resolution, or properly installing Updates that are recommended as part of the resolution. On a P1 Incident we expect you to make resources available on a 24x7 basis to assist Choreo Labs's round-the-clock efforts in resolving the Incident. Our Service Level targets are predicated on your sufficient involvement.
6. Support levels
Choreo Labs's Basic Support Plan and Enterprise Support Plan offers L1-L4 support. OEM Support Plan offers L2-L4 support.
| Level 1 (L1) | Initial case acceptance from the End User, validation of support eligibility, initial response, and case assignment. Collection of basic information about the product usage scenario, deployment environment, and configuration as may be needed to understand the issue thoroughly. |
|---|---|
| Level 2 (L2) | Diagnosis of the issue and verification that the issue is related to the Choreo Labs product. Application of known solutions to the issue, where related to product usage, configuration, deployment, update level, or environment. |
| Level 3 (L3) | Advanced reproduction, analysis and debugging. Provision of a Fix through re-configuring, adjusting the use of the product, or adjusting the deployed environment. |
| Level 4 (L4) | Developing a product update or documentation Fix that resolves the issue. |
7. Updates and upgrades
Updates are available to Subscribers and other registered users through the Choreo Labs Update services at https://choreolabs.com/updates. Updates are cumulative within an update channel – new updates issued by Choreo Labs include or depend upon previous updates made to the affected component. Subscribers are encouraged to stay up to date with all relevant Updates from Choreo Labs.
Updates are available to Subscribers and may be used both for development activities and production deployment.
If Choreo Labs determines that an Update is required to remedy an Error in one or more Supported Choreo Labs Product components, which Choreo Labs will determine by acting reasonably and in good faith, Choreo Labs will identify or develop a Fix, build and certify the Fix into an Update and make that Update available through the Choreo Labs Update service. Choreo Labs will provide Fixes it develops to the provider or development community for the software component, who can subsequently decide if the Fix will be committed into the software component's source code tree.
Subscribers are encouraged to upgrade regularly. Upgrading to a newer minor or major version does not invalidate your Subscription. Please keep Choreo Labs informed of any significant usage changes regarding the products under Subscription – it helps us respond more quickly and effectively to support cases.
Note that Choreo Labs Update services do not apply to Ballerina. A resolution for an incident with the Ballerina compiler or the Ballerina Library may include an early access to a patch release, provided to you through your support account. Subsequently the fix will be made available through a patch release to the open source project and under the open source license terms. Subscribers are also eligible to receive relevant Security bulletins and early access to patch releases addressing potential security vulnerabilities through the same mechanism.
8. Lifespan and deprecation
Choreo Labs commits to support each major and minor release of the Supported Choreo Labs Product for a minimum of 3 years from the date of release. After this period Choreo Labs may discontinue Choreo Labs Support Services for a product version at any time.
After Choreo Labs notifies Subscriber of the intention to discontinue support for a product version, Choreo Labs will use commercially reasonable efforts to continue to support the version for at least one year after that announcement.
A complete record of the release and active support dates for each product version is maintained at https://choreolabs.com/products/support-matrix.
9. Changes to or discontinuance of support services
Choreo Labs reserves the right to modify this Support Services Policy subject to the terms of the Subscription entered into between the Subscriber and Choreo Labs.
10. Data retention
This section outlines the Choreo Labs policy regarding the retention of user data.
Retention Period for Support Users' PII: Choreo Labs will retain the personally identifiable information (PII) of support users, including their names and email addresses, for a period of 90 days from the termination of the contract. After this period, Choreo Labs will delete or securely dispose of the PII to prevent unauthorized access, use, or disclosure.
Retention Period for Support Case Attachments: Choreo Labs will retain attachments related to support cases for a period of 90 days from the resolution or closure of the respective case, or from the termination of the contract, whichever comes first. After this period, Choreo Labs will delete the attachments from its systems.
Retention of Support Portal Data (Excluding Support Cases): Choreo Labs will retain non-support case based data stored in the support portal for a period of 90 days from the termination of the contract. After the retention period, Choreo Labs will delete the above data from its systems.
11. Questions
Questions or correspondence about this policy can be directed to [email protected], or to Choreo Labs, Attn: Support Manager, 10900 Stonelake Blvd, Building 2, Suite 100, Austin TX, 78759.
12. Definitions
- "Ballerina Library"
- means the packages published to Ballerina Central under 'ballerina' and 'ballerinax' organizations
- "Business Day"
- means any day, excluding weekends and public holidays, in the United States of America, unless otherwise specified in a Subscription.
- "Business Week"
- means five consecutive Business Days.
- "Combined Product"
- means each value-added software application program and/or computer hardware product specified in a Subscription that (i) incorporates the Supported Choreo Labs Product and (ii) is developed by Subscriber for commercial distribution to more than one End-User.
- "Completion Time"
- means the time elapsed between the acknowledgement of a task and the completion of the task or an ETA of the completion of the task to the reasonable satisfaction of Subscriber, as indicated on the Choreo Labs Support Portal.
- "Query Support Limit"
- means the maximum allowed utilization within a Subscription term of the support system for raising Queries, measured in hours expended by Choreo Labs in reaching a resolution.
- "Documentation"
- means any current user guides, operating instructions, release notes, update announcements, installation guides, on-line help files regarding the use of the Supported Choreo Labs Product, manuals or other materials that are generally made available with the software by Choreo Labs.
- "End User"
- means Subscriber or a third party licensed to use a Combined Product internally and not for distribution.
- "Error"
- means either (a) a failure of the Supported Choreo Labs Product to conform to the specifications set forth in the Documentation, resulting in the inability to use, or restriction in the use of, the software, a runtime failure of the systems under Managed Services hosting provided by Choreo Labs, and/or (b) a problem requiring new procedures, clarifications, or additional information. It does not include development of new features.
- "First Level Support"
- should your Order Form designate it, offers L1-L4 support (detailed under Support Levels in Section 6 above) on a 24x7x365 basis for the Supported Choreo Labs Product.
- "Fix"
- means either a software modification or addition that, when made or added to the Supported Choreo Labs Product, corrects the Error or Incident, or a procedure or routine that, when observed in the regular operation of the software, eliminates the practical adverse effect of the Error on Subscriber or End Users.
- "Managed Deployment"
- means a deployment of Supported Choreo Labs Products, wherein Choreo Labs assumes full responsibility for hosting and managing the solution, in accordance with the service levels.
- "Managed Third Party Component"
- means a third-party component that is administered by Choreo Labs as an integral part of a Managed Deployment.
- "Second Level Support"
- should your Order Form designate it, offers L2-L4 support (detailed under Support Levels in Section 6 above) on a 24x7x365 basis for Supported Choreo Labs Product used in a Combined Product.
- "Subscriber"
- means those individuals and entities that have entered into a Subscription with Choreo Labs for all necessary licenses and the provision of Support Services.
- "Subscription"
- means the applicable agreement(s) between Choreo Labs and a Subscriber for the provision of Support Services, including Order Forms.
- "Support Engagement"
- means a Subscriber-initiated request for assistance created via the support portal.
- "Support Services"
- means access to Choreo Labs support systems and personnel to be used within the scope and limits as set out in this Support Policy and the Subscription.
- "Support Policy"
- means the policies and procedures as set forth herein.
- "Supported Choreo Labs Product"
- means the instances of software identified in a Subscription, or upgraded versions thereof, used within the limits proscribed by the Subscription.
- "Resolution Time"
- means the time elapsed between the acknowledgement of a Case and the final resolution or Fix or an ETA of a Fix to the Case to the reasonable satisfaction of Subscriber, as indicated on the Choreo Labs Support Portal. For Cases categorized with a S0 severity and associated with a Managed Third Party Component, the final resolution is contingent upon the availability of assistance for troubleshooting or a Fix from the respective third-party component vendor.
- "Response Time"
- is defined as the time elapsed between the reporting of an Incident by the Subscriber or Choreo Labs becoming aware of the Incident (whichever is earlier) and a Choreo Labs Technical Support Engineer acknowledging the receipt of such report to Subscriber through the Choreo Labs Support Portal.
- "Workaround Time"
- means the time elapsed between the acknowledgement of an Incident and the provision of a Fix or a Workaround for an Incident, to the reasonable satisfaction of the Subscriber.
- "Target"
- means a goal Choreo Labs shall endeavor to achieve.
- "Workaround"
- is a temporary solution for an Incident preceding a permanent resolution or Fix.
- "Update"
- means software components, media, printed materials, and online or electronic documentation that augments the capability or addresses a requirement or deficiency in the Supported Choreo Labs Product. Updates include patches obtained through the Choreo Labs Update service or delivered directly to the Subscriber.
13. Compatibility
For continuity and ease of reference, this section maps the Incident priority levels (P0–P3) and Query type used in Choreo Labs Support Services Policies version 5.9 and below to the equivalent severity levels in this current policy.
Severity to priority level mapping
The Incidents with priorities from P0-P3 is equivalent to the severities defined in this policy from S0-S3. The Query type issues are directly equivalent to the S4 severity defined in this policy. The following illustrates this mapping:
| Severity | Applicable policy version | Priority | Compatible policy version |
|---|---|---|---|
| S0 | 6.0 or above | P0 | 5.9 or below |
| S1 | 6.0 or above | P1 | 5.9 or below |
| S2 | 6.0 or above | P2 | 5.9 or below |
| S3 | 6.0 or above | P3 | 5.9 or below |
| S4 | 6.0 or above | Query | 5.9 or below |
Note:
All the references mentioned with severity S0-S3 are applicable as incidents and S4 will be applicable for query types for the support policies version 5.9 or below.