Service Level Agreement (SLA)
版本 3 · 更新于 2026年11月18日
This Service Level Agreement (this “SLA”) forms part of, and is incorporated by reference into, the 12Times Master Network and Software Services Agreement (“MNSA”) and each Order Form. Capitalized terms not defined here have the meanings in the MNSA. This SLA applies only to Covered Production Services expressly identified in an Order Form.
1. SCOPE
1.1 Covered Production Services. This SLA applies to the production, 12Times-controlled orchestration service that accepts valid requests, performs configured administrative AI or workflow processing, and makes the resulting response or transaction available at the 12Times service boundary (“Covered Production Services”). This SLA applies beginning on the Go-Live Date identified or confirmed under the applicable Order Form.
1.2 Excluded Components. Unless an Order Form states otherwise, this SLA does not apply to: (a) alpha, beta, pilot, preview, evaluation, or free services; (b) professional services and implementation; (c) Customer Systems; (d) Third-Party Services; (e) delivery or receipt after a message leaves the 12Times-controlled boundary; or (f) the correctness of an AI output, system-of-record data, End-User contact information, or a Customer-approved workflow.
1.3 No Clinical Response SLA. This SLA is a technology-availability and support agreement. It does not establish a clinical response time, a duty of care to an End User, an emergency-service obligation, or a guarantee that Customer personnel will act on an escalation.
1.4 Order Form Control. An Order Form may identify additional Covered Production Services or a different support package; any deviation must expressly reference this SLA.
2. DEFINITIONS
“Actual Monthly Availability” the percentage calculated under Section 3.2 for the applicable calendar month.
“Business Hours” 9:00 a.m. to 6:00 p.m. Eastern Time, Monday–Friday, excluding U.S. federal holidays.
“Eligible Monthly Fee” the recurring subscription fee actually paid for the affected Covered Production Service for the month, excluding implementation fees, usage charges, third-party charges, taxes, hardware, and professional services.
“Excluded Time” time excluded under Section 4.
“Service Credit” a credit applied to future fees under Section 7; not a cash refund.
“Unavailable Minute” a full minute during which a Covered Production Service is continuously unavailable to Customer after the first five consecutive minutes of a qualifying outage, excluding Excluded Time.
3. MONTHLY AVAILABILITY COMMITMENT
3.1 Commitment. 12Times will use commercially reasonable efforts to provide at least 99.5% Actual Monthly Availability for Covered Production Services during each calendar month.
3.2 Formula. Actual Monthly Availability = ((T − U) ÷ T) × 100%, where T is the total minutes in the calendar month and U is the total Unavailable Minutes that month.
3.3 Measurement. 12Times determines availability using its monitoring, logs, and incident records. Customer evidence may be considered, but isolated endpoint, End-User-device, channel-delivery, or system-of-record failures do not establish unavailability.
3.4 Material Availability. A Covered Production Service is unavailable only when the 12Times-controlled service cannot accept or process valid requests for a material portion of Customer’s production tenant. Individual message failures, partial degradation, increased latency, or an inaccurate output are not unavailability unless they prevent material use.
3.5 Illustrative Allowance. In a 30-day month, 99.5% availability permits up to about 216 minutes of qualifying unavailability after applying Excluded Time.
3.6 Initial Stabilization Period. The first sixty (60) days after the Go-Live Date — unless the applicable Order Form expressly provides for a period of up to ninety (90) days — is an Initial Stabilization Period during which 12Times will use commercially reasonable efforts to maintain availability and tune the custom deployment (messaging channels, Customer systems, and third-party dependencies), and during which Service Credits do not apply. The Service Commitment and Service Credits apply beginning at the end of the Initial Stabilization Period.
4. EXCLUDED TIME
4.1 No Unavailable Minute is counted to the extent caused by:
- Scheduled Maintenance under Section 5, or emergency maintenance necessary to protect security, integrity, or operation.
- A factor outside 12Times’ reasonable control — internet backbone, utility, telecommunications, cloud-region, public-health emergency, natural disaster, government action, war, or widespread cyberattack.
- Customer action or inaction, Customer Systems, configuration, credentials, network, devices, data, personnel, or failure to follow Documentation.
- A Third-Party Service — including a Customer system of record (such as an EHR/EMR), WeChat or another consumer messaging platform (such as Gmail, WhatsApp, or iMessage), an identity provider, an API, or a Customer-selected integration — except to the extent the failure is caused by a component under 12Times’ direct control.
- Customer’s use beyond documented limits, unsupported configurations, unauthorized modifications, malicious or unlawful use, or a suspension permitted by the MNSA.
- Alpha, beta, pilot, preview, evaluation, or free functionality.
- A single period of continuous unavailability lasting fewer than five minutes.
- Customer’s failure to provide timely access or information reasonably required to diagnose or remedy an incident.
4.2 Provider-Caused Exception. A third-party failure is not automatically excluded if the qualifying outage is caused by 12Times’ failure to properly operate a Provider-controlled component. The parties will allocate time according to the primary cause where reasonably determinable.
5. MAINTENANCE AND STATUS COMMUNICATIONS
5.1 Scheduled Maintenance. 12Times will use commercially reasonable efforts to give at least twenty-four (24) hours’ advance notice of Scheduled Maintenance and to schedule it outside typical Customer business hours.
5.2 Emergency Maintenance. 12Times may perform emergency maintenance without advance notice where reasonably necessary to address a security vulnerability, legal requirement, data-integrity issue, or material service risk.
5.3 Status Updates. For a material production incident, 12Times will provide status updates through the support channel or email as reasonably appropriate. Status estimates are good-faith targets and may change.
6. SUPPORT AND INCIDENT RESPONSE TARGETS
6.1 Support Channels. Customer will submit support requests through the designated support channel, including the Customer name, affected function, start time, transaction identifiers where available, business impact, and a knowledgeable contact. 12Times will provide Customer with the applicable support contact method(s), including the method for submitting a P1 emergency, at onboarding, and may update them from time to time on notice.
| Severity | Qualification | Initial Response | Update |
|---|---|---|---|
| P1 Critical | Covered Production Service materially unavailable; a critical workflow broadly unavailable; or a confirmed Provider-controlled security event. | Target 2–4 hours (commercially reasonable) after proper submission via the P1 emergency channel; 12Times monitors on an extended basis but does not guarantee 24×7 staffing. Commercially reasonable efforts to restore or provide a workaround (target, not guaranteed). | Target every 2 hours during active, staffed response periods. |
| P2 High | Material degradation of a core function with no reasonable workaround, but not fully unavailable. | 8 Business Hours; timing to resolve depends on cause, third party, and complexity. | At least each Business Day. |
| P3 Standard | Non-critical defect, intermittent issue, inquiry, configuration request, or optimization question. | 24 Business Hours; handled through normal support or release planning. | As reasonably appropriate. |
6.2 Severity Assignment. 12Times may reasonably reclassify severity based on objective impact. A P1 must concern a current production event and use the P1 method. Feature requests, implementation questions, individual-message issues, and inaccurate outputs are not P1 unless they cause material unavailability.
6.3 Response vs. Resolution. “Initial Response” means acknowledgment by qualified personnel and commencement of triage. A workaround target is not a warranty that the root cause will be permanently corrected within the stated time.
6.4 Customer Cooperation. Response clocks may pause while 12Times reasonably awaits Customer information, access, testing, approval, or action. Customer will maintain an available incident contact for P1 events.
6.5 Security and HIPAA. Security-Incident and breach-notification obligations are governed by the MNSA and BAA. This support table does not extend or replace a legally required notification deadline.
7. SERVICE CREDITS
7.1 Eligibility. If Actual Monthly Availability falls below 99.5% and Customer satisfies Section 8, Customer is eligible for the following Service Credit against the Eligible Monthly Fee:
| Actual Monthly Availability | Service Credit |
|---|---|
| Less than 99.5% but ≥ 99.0% | 5% of the Eligible Monthly Fee |
| Less than 99.0% | 10% of the Eligible Monthly Fee |
7.2 Cap. Total Service Credits for a calendar month will not exceed 10% of the Eligible Monthly Fee, regardless of the number of incidents or affected functions.
7.3 Application. Service Credits apply to future amounts payable for the affected Service. They are not cash refunds, are not transferable, and have no value after termination except as required by law.
7.4 No Double Recovery. The same event cannot generate multiple or overlapping credits. If an Order Form provides a more specific credit for the same event, the more specific credit applies.
7.5 Account Status. Customer is not eligible for a Service Credit while undisputed fees are materially past due or Customer is in material breach.
8. CREDIT CLAIM PROCEDURE
8.1 Deadline. Customer must submit an “SLA Credit Claim” through the support channel within thirty (30) days after the last day of the calendar month in which the alleged failure occurred.
8.2 Contents. The claim must include: (a) Customer and affected tenant; (b) dates and times; (c) affected Covered Production Service; (d) relevant support-ticket numbers; (e) business impact; and (f) reasonably available evidence.
8.3 Review. 12Times will review its monitoring and incident records and notify Customer of the determination; approved credits appear on a future invoice. Failure to submit a timely, complete claim waives the credit for that month.
8.4 PHI in Tickets. Customer will not be required to submit PHI in a support ticket unless 12Times expressly provides an approved secure method and the information is necessary.
9. SOLE REMEDY AND RELATIONSHIP TO OTHER OBLIGATIONS
9.1 Sole Remedy. Service Credits are 12Times’ sole liability and Customer’s sole and exclusive remedy for failure to meet the monthly availability commitment.
9.2 Independent Breaches. This limitation applies only to the availability commitment. It does not eliminate remedies for a separate breach of the BAA, confidentiality, data-security, intellectual-property, or other provisions of the Agreement.
9.3 Support Targets. Failure to meet a support response or workaround target does not independently create a Service Credit unless an Order Form expressly provides one.
10. CUSTOMER CONTINUITY RESPONSIBILITIES
10.1 Fallback Procedures. Customer will maintain reasonable manual or alternative procedures for End-User communications and scheduling during an outage, including a method for staff to access Customer’s system of record and communicate urgent instructions.
10.2 Not an Emergency Channel. Customer will not represent the Services as an emergency channel and, where applicable to Customer’s use, will maintain notices directing End Users to 911 or Customer’s approved emergency pathway.
10.3 Backup of Records. Customer is responsible for backup and retention of its records (including, for healthcare deployments, the legal medical record), contact lists, schedules, and other information needed to continue operations, unless an Order Form expressly assigns a backup obligation to 12Times.
11. UPDATES AND PRECEDENCE
11.1 Updates. 12Times may update this SLA prospectively. A material reduction in the availability commitment or Service Credit percentage will not apply during an active committed Order Term unless required by law, necessary for a security or patient-safety risk, or accepted by Customer.
11.2 Precedence. The BAA controls as to PHI and HIPAA. An Order Form controls only where it expressly identifies a deviation from this SLA. The MNSA controls other conflicts.
11.3 No Third-Party Rights. This SLA does not create rights for any End User or other third party.
APPENDIX A — Availability Examples
| Month | Total Minutes | 99.5% Max Qualifying Unavailability |
|---|---|---|
| 28 days | 40,320 | 201.6 minutes |
| 30 days | 43,200 | 216 minutes |
| 31 days | 44,640 | 223.2 minutes |
A.1 Example — No Credit. In a 30-day month, Customer experiences 120 qualifying Unavailable Minutes plus 180 minutes of a third-party-vendor outage (for example, an EHR or messaging platform) (Excluded Time). Availability = (43,200 − 120) ÷ 43,200 = 99.722%. No Service Credit.
A.2 Example — 5% Credit. In a 30-day month, 300 qualifying Unavailable Minutes. Availability = (43,200 − 300) ÷ 43,200 = 99.306%. Eligible for a 5% Service Credit, subject to a timely claim.
A.3 Example — 10% Credit. In a 30-day month, 600 qualifying Unavailable Minutes. Availability = (43,200 − 600) ÷ 43,200 = 98.611%. Eligible for a 10% Service Credit, subject to a timely claim.