​
1.4 Resolution Process
Caju will address and resolve issues with the Services reported by Customer that are within Caju’s control using commercially reasonable efforts based on the severity, impact, available workarounds, and technical complexity of the issue. For Severity 1 and Severity 2 issues, Caju will investigate the issue and work toward a fix or temporary workaround. For Severity 3 issues, Caju will work during normal business hours to investigate and implement a fix or workaround. For Severity 4 issues, Caju may provide a fix in a future maintenance release.
​
1.5 Escalation Process
Customer may escalate an active support case if Customer is not satisfied with the resolution method, there has been a material change in business impact after the issue was reported, or Caju fails to respond materially within the applicable target response time. Escalation instructions will be made available through Caju’s designated support channel.
​
2. Service Levels
Caju will use commercially reasonable efforts to correct or edit the hosted Services, including the Core Platform and Messenger where included in the purchased Services, to the extent the Services do not perform in accordance with applicable user documentation. Caju will make generally released enhancements available to Customer subject to these Terms and the applicable Order Form.
​
2.1 Definitions
“Availability” means that Customer can access the applicable production Services and is measured using the formula in Section 2.2.
“Available For Use” means that the supported functions and features of the applicable production Services are capable of sending and receiving data to and from the Internet.
“Downtime” means service interruptions that occur outside applicable maintenance windows, excluding Planned Maintenance, Emergency Maintenance, and the other exclusions stated in this Schedule.
“Emergency Maintenance” means maintenance required to maintain availability on a go-forward basis or execute a critical security change.
“Outage” means an unplanned service interruption that temporarily prevents access to major functions of the applicable production Services.
“Planned Maintenance” means maintenance that occurs during the maintenance windows specified in Section 2.3, or maintenance outside those windows for which Caju has provided reasonable advance notice.
“Scheduled Uptime” means total time in the applicable calendar month less scheduled maintenance windows.
“Time Unavailable” means any period during the applicable calendar month that the applicable production Services are not Available For Use, excluding the items listed below.
Time Unavailable does not include periods during which the Services are not Available For Use due to: Planned Maintenance; Emergency Maintenance; interruptions in third party networks, carriers, messaging platforms, APIs, or services; utility interruptions where reasonable redundancy precautions are used; acts outside Caju’s reasonable control, including Customer directed activities, governmental or regulatory actions, court orders, and force majeure events; or Customer’s failure to respond to incidents that require Customer participation or to support, repair, or replace Customer supplied equipment, systems, credentials, accounts, or configurations.
​
2.2 Uptime Commitment
Caju will use commercially reasonable efforts to achieve monthly Availability for the production instance of the Core Platform and Messenger of not less than 99.8%. This commitment does not apply to user acceptance testing environments, sandbox environments, trial environments, beta functionality, or other non-production environments.
Availability is measured as follows: Availability = (Scheduled Uptime - Time Unavailable) / Scheduled Uptime.
​
2.3 Maintenance Windows
To the extent reasonably practicable, Caju will perform planned maintenance during the following maintenance windows: Monday through Friday from 11:00 PM to 1:00 AM Eastern Time, and weekends at any time. Caju may perform emergency maintenance outside these windows when reasonably required to maintain availability, security, or integrity of the Services.
​
2.4 Recovery Time Objective
Caju’s recovery time objective for the Services is twelve hours, subject to the applicable recovery plan and the exclusions stated in these Terms and this Schedule.
​
2.5 Recovery Point Objective
Caju’s recovery point objective for the Services is six hours, subject to the applicable recovery plan and the exclusions stated in these Terms and this Schedule.
1.3 Target Initial Response
After Customer creates a support case, Caju will use commercially reasonable efforts to respond within the target initial response time below for the corresponding severity level.
Severity
1
2
3
4
Target Initial Response
120 minutes
4 hours
2 business days
4 business days
Last updated: June 2026
Schedule 1. CAJU AI SUPPORT AND SERVICE LEVEL AGREEMENT
This Schedule sets forth Caju AI’s standard support and service level commitments for the Services. It is included as part of these Terms for standard and small orders unless a separate written agreement or Order Form expressly states otherwise.
​
1. Support
Caju AI provides standard support services with all Services at no additional charge. Caju’s support team and engineering resources are intended to help Customer report, diagnose, and resolve issues affecting the availability or performance of the Services.
​
1.1 Standard Support Services
Feature
Updates, fixes, and enhancements in standard release cycle
Web-based support
​
Standard support hours
​
​
Urgent support for Severity 1 issues
​
Standard Support
Included
​
Included
​
Monday through Friday, 8:00 AM to 8:00 PM Eastern Time, excluding United States federal holidays
Available 24 hours per day, 365 days per year through Caju’s designated urgent support channel
1.2 Service Incidents and Support Requests
Except for Severity 1 issues, Customer should report issues regarding availability or performance of the Services through Caju’s designated support channel. Severity 1 issues should be reported through Caju’s designated urgent support channel. Support requests should include a detailed description of the issue or request, including the operating conditions that gave rise to the issue. Caju will confirm receipt of support requests by email or through the applicable support channel where reasonably practicable.
Severity
1
​
​
2
​
​
​
3
​
​
4
Description
Service is down, or major functionality is unavailable or materially impacted for multiple users, and no workaround is available.
Important functionality is unavailable or degraded for multiple users, or major functionality is unavailable or materially impacted for a single user, and no workaround is available.
Important functionality is unavailable but a workaround is available, or there is intermittent disruption of Services.
​
A minor feature is unavailable, or there is a minor performance impact.

