SuccessKPI Service Level Agreement
Exhibit A: Service Level Agreement
SuccessKPI provides Service Level Agreements (SLAs) to our Enterprise customers purchasing premium or elite support.
These SLAs include the following:
- Uptime SLA
- Incident Response and Resolution SLA
- Uptime SLA. Success KPI operates a high availability architecture capable of failover within multiple AWS recovery zones and failover across multiple Amazon regions. We operate a Business Continuity Plan which is tested quarterly. As a reporting platform we provide an important but not a “minute to minute” essential platform.
- SuccessKPI provides a 99.9% uptime SLA measured monthly on a 24×7 basis. Security is our primary objective based on the data we manage. SuccessKPI provides a Software as a Service platform that is in use across multiple time zones and targets high availability for all of our customers. We measure uptime on an availability basis based on system uptime using third party uptime tools. We provide reporting to our customers on demand.
- Continuous Monitoring: SuccessKPI continuously monitors our platform for uptime and responds immediately to any issues irrespective of client reports. Credits: This section identifies the credits for non-performance and over performance as appropriate and is the sole remedy for any outages experienced by the Customer.
- SLA Standard: We will make the platform available 24 hours a day, 7 days a week, and use commercially reasonable best efforts to provide 99.9% or better uptime, except for
- Scheduled Downtime,
- Outages caused by third parties including our CCaaS partners,
- Outages caused by networks, access points and the Internet
- Customer related downtime.
- Requests: If the platform is unavailable in any given calendar month, the Customer may request a credit within fifteen days of the end of that current month via support@successkpi.com.
- Credit Calculation: The credits will be calculated as follows: one (1) minus the amount of downtime in a month divided by the total minutes of possible availability in that month. As an example, for 10 minutes of downtime in a 30 day month the calculation would be as follows: 1 – (10 mins)/(30 days x 24 hour x 60 Minutes = 1 – (10/43,200) = 99.977%.
- Repeated Outages: If SuccessKPI misses the uptime threshold three times within any calendar year, then the Customer may request an in-person meeting of the Director of Operations of SuccessKPI and a corrective action plan. Failure to meet this plan may result in further penalties up to and including termination of the agreement.
|
Uptime % for any Given Month
|
Credit |
| Above 99.9% |
No Credit |
| 99.85% to 99.9% |
5% |
| 99.8% to 99.9% |
10% |
| Below 99.8% Uptime |
20% |
- Incident Response SLA. Success KPI has four levels of system response based on the severity of the case being reported by the end client. Time is measured from the time SuccessKPI logs a case from the customer.
Below is a chart of our Service Level Agreements including Response time and recovery goal.
| Incident Type Goal for Response |
Approach to Resolution Severity |
| 1: Severe impact to business operations as system is complete Out of Service and unavailable. |
Phone Response with Work continuously until system is restored.
in 30 minutes |
| Severity 2: Major System component not working A primary system component is not operational |
Phone Response within one hour. Goal is to restore functionality within 2 business days. |
| Severity 3: Business is operational. System is operating and available. A Feature of the product that is essential to the business is not working as specified |
Phone Response within one business day. Goal is to restore feature to previously working state within one week. |
| Severity 4: A minor bug, defect, or feature request that the customer would like to see addressed in a future release. |
Email Response within two business days. Fix as is necessary. Acceptance/Rejection (and associate reason if rejected) and commitment date will be acknowledged in the Quarterly Business Review. |
Goal for Response: Measures the agreed targeted response time acknowledging a case has been received and a time stamp for acceptance of the case.
Approach to Resolution: Measures the goal for time to resolve issues at this severity level. Time is measured based on log into SuccessKPI case management system.
Note: for any Severity Level 1 outage, SuccessKPI will submit a Root Cause Analysis within five business days of the outage resolution.
Last Modified: January 24, 2025