Service Level Agreement

This Service Level Agreement ("SLA") documents and governs the agreed provisions of Service Terms of Support, Support Scope, Exclusions, Release and Deployment schedule and is exec

 · 9 min read

This Service Level Agreement ("SLA") documents and governs the agreed provisions of Service Terms of Support, Support Scope, Exclusions, Release and Deployment schedule and is executed between KAINOTOMO PH LTD ("KAINOTOMO", "We", "Us" or "Our") and the Customer("You", "Your" or "Customer") who has agreed to the Master Service Agreement ("MSA") (Link:- )

Please note that this SLA only applies to Support Services provided by KAINOTOMO pursuant to the MSA.(Link:- ) 

Please read the contents of this document carefully before using any of Our Services.

I. Definitions

  1. "Agreement" means this SLA describes the support policy of KAINOTOMO and shall apply to all Customers who have agreed to the MSA .
  2. "Business Days" means a day other than a Saturday, Sunday or public holiday in the state or territory where the Service is being provided by KAINOTOMO. 
  3. "Business Hours":- 08:00 to 16:00 Cyprus Standard Time ("IST") (Monday-Friday)
  4. "Cloud Service" means any distinct, subscription-based, hosted (and maintained) services that are offered by KAINOTOMO.
  5. "Core KAINOTOMO software's Feature(s)" means those features of KAINOTOMO software's that are provided within KAINOTOMO software's and Core KAINOTOMO software's Modules, as distributed without any modification and without any additional Modules. Core KAINOTOMO software's Feature(s) may include features provided by Core KAINOTOMO software's Modules. The list of Core KAINOTOMO software's Feature(s) can be modified by KAINOTOMO at any time in its sole discretion without prior notification to the Customer.
  6. "Core KAINOTOMO software's Modules" means Modules that are provided within the standard and unmodified public releases of KAINOTOMO software's, as distributed by KAINOTOMO software's Core Maintainers. Core KAINOTOMO software's Modules may include: (i) accounts, (ii) assets, (iii) buying, (iv) customer relationship management, (v) human resource, (vi) projects, (vii) quality management, (viii) selling, (ix) stock, and (x) support. The list of Core KAINOTOMO software's Modules may be modified by KAINOTOMO at any time in its sole discretion without any prior notification to the Customer.
  7. "Customer" shall mean: (i) in case an individual accepts this Agreement on behalf of himself / herself, then such individual; and (ii) in case an individual accepts this Agreement on behalf of a company, organization, or other entity (whether or not it is registered or incorporated), such company, organization or other entity.
  8. "Customer Data" means electronic data or any other information submitted by the Customer to KAINOTOMO, excluding content from third-party applications, integrations.
  9. "Database" means the underlying database that stores the Customer Data.
  10. "Documentation" means the applicable web resources pertaining to the information of using KAINOTOMO software's, updated from time to time, the comprehensive Do-It-Yourself Guide, accessible via or from within the KAINOTOMO software's Account.
  11. "Downtime" means the time there was unavailability of an KAINOTOMO software's account due to maintenance activity at our end.It may occur due to breakdown at the server's end since KAINOTOMO may host with Third Parties.
  12. "KAINOTOMO software's Account" means the web URL for accessing the account Customer has subscribed for with KAINOTOMO. This is synonymous to KAINOTOMO software's Site and KAINOTOMO software's Instance. 
  13. *"KAINOTOMO Consultants" *refers to the Consultants who are representatives of KAINOTOMO.
  14. "Issue" means a support ticket that has been raised by a Customer or an Authorized User for reporting an incident or requesting service requests.
  15. "Services" means the products and services that are ordered by the Customer under the MSA or provided to Customer free of charge (as applicable) or under a free trial, and made available online by KAINOTOMO. 
  16. "Support Scope" shall have the meaning assigned to it in Section 2.1 of this Agreement.
  17. "Support Services" shall have the meaning under Section 5.1.1 of MSA (Link:- )
  18. "Subscription" means the active hosting, server or support plan that the Customer has paid for availing KAINOTOMO Services.
  19. "User" means any individual to whom the customer grants access for accessing the KAINOTOMO software's Account.
  20. "User Role" means the role granted to the Users in an KAINOTOMO software's account. Different User Roles have various permissions and access control is exhibited using User Roles.
  21. "Weekend Support" :-refers to the support provided by KAINOTOMO Consultants on weekends (Saturday & Sunday).

II. Service Levels

This section provides all the relevant details on Service Availability, monitoring the scope of services and related components.

2.1. Support Scope

2.1.1 Support Services will be provided by KAINOTOMO only on the standard product and official release of KAINOTOMO software's. Configurations of options available within Core KAINOTOMO software's Features are a part of the standard product support. Support Services are not provided for code customizations, custom Modules and third-party Modules.

2.1.2. Support Services will be provided only for Instances running on distributions of Linux that are supported by Bench. The list of Linux distributions supported by Bench is subject to change at any time without prior notice. Customer shall be the sole responsible party to ensure that Customer is using a Linux distribution supported by Bench.

2.1.3. The Scope of this Service Level Agreement shall also include:

  1. Functional support: Functional Support shall include support on all standard features of KAINOTOMO software's. KAINOTOMO shall only provide support in the form of guidance to the Customer. The onus of implementation extends to the Customer. Functional Support to the extent of Configuration support shall include but not limited to support for configuring workflow.
  2. Issue Investigation: Issue Investigation refers to examining the reported behavior of a feature when it is not exhibiting expected functionality. All issues shall be replicable and Customer shall support KAINOTOMO in replicating the issue in a non-production environment.
  3. Bug fix: Bug fix refers to fixing of verified bugs after Investigation. Bugs will be fixed based on severity and criticality and which are included in our regular Release process. In cases of Critical bugs it may be resolved on priority basis and released immediately.
  4. Data fix: In cases of Data fix, support shall be provided to the Customer only for correcting data if it is an outcome of a verified bug.
  5. Upgrade Support: KAINOTOMO will provide upgrades and maintain the latest version of the application in the KAINOTOMO software's Account.
  6. Scaling Support: Optimising database to improve performance wherever deemed necessary.
  7. Priority & Phone Support: Priority and phone support shall be provided to a Customer who has additionally purchased the Priority & Phone Support and is part of the Order form executed between KAINOTOMO & the Customer. If the Customer has purchased Priority and Phone Support then the Service levels shall be according to Table II of Clause 2.6 of this Agreement.

2.1.4 Upon KAINOTOMO sole discretion, the Scope of this Agreement (depending on several parameters) may include Support services in feature request or feature redesign. 

2.2. Support Process, Creation of Support Tickets

2.2.1 Customers can get Support Services at  

2.2.2. All Support tickets raised by the Customer shall be classified as "Unclassified". KAINOTOMO shall classify such Support Tickets according to Section 2.4 of this Agreement. The Customer shall be notified at a reasonable time by KAINOTOMO about the Issue Priority of the Support ticket raised by the Customer.

2.2.3. Support tickets generated by the Customer shall remain "Open" for thirty one (31) days from the date of reply of the Support Ticket by KAINOTOMO. The Support tickets after thirty one (31) days shall be automatically "Closed" if the Customer does not reply against the Support Ticket. 

2.3 Support Exclusions

The following Services are not included in Support and are exclusively beyond the Scope of this Agreement. Upon KAINOTOMO sole discretion, KAINOTOMO Consultants may provide these services on a case to case basis. KAINOTOMO Consultants may train the Customers to implement these Services but the liability to perform these Services shall solely be on the Customer. These Support Services include:

  1. Scenario support: Scenario Support shall refer to Mapping User's specific business use-case.
  2. Data Entry & Data Import:- KAINOTOMO shall not be responsible for providing support in physically or electronically entering data of the Customer into the database or/and importing data from Customer's legacy database or storage. 
  3. Client Script & Print Format:- KAINOTOMO shall not provide support in code customization to the Customers or/and provide amendments to the Print format. 
  4. Manual Data Sanitization:- KAINOTOMO shall not provide support is sorting or filtering of data of the Customer. The Customer is solely responsible for managing its own data.
  5. User Management & Permission Management:- Customer shall be solely responsible for its User & Permission Management.
  6. Infrastructure Purchase:- KAINOTOMO shall not provide any type of Infrastructure purchase to the Customer such as, but not limited to, server or any other type of hardware. 
  7. KAINOTOMO shall provide all support through the Support Portal Query session shall not be addressed via Telephonic Support to any Customer unless priority Phone Support is purchased.

2.4 Support Hours

The Support hours are calculated under Cyprus Standard Time ("IST").The coverage parameters specific to the service(s) covered in this Agreement are as follows:

  1. Business Hours: Monday-Friday, 08:00 to 16:00 IST
  2. Support Email: 
  3. The Email Support shall be only available on weekend (Saturday, Sunday) support in case if the in-app support is not accessible.
  4. Weekend Support shall only be available to Customer only on Critical issues.
  5. Emails received outside the Business hours will be queued and we will try to ensure solving the issue the same or next business day.
  6. In case of Customers on Phone & Priority Support, the Calls received after specified hours & weekends, will be forwarded to a designated KAINOTOMO Consultant. The best efforts will be taken to rectify the problem as per Section 2.6 of this Agreement.

2.5 Support Levels

The criteria of each level of Issue Priority shall be as per the following sequence. Each support issue will be classified based on the criticality and impact by KAINOTOMO.

2.5.1 Issue Priority Critical:-

  1. System is inoperable / not functioning

  2. Impact threatening productivity

  3. Server Failure

  4. Network down for whole Office Functional Query:-

  1. Issues ranging from functional queries related to various features and modules of KAINOTOMO software's, Cloud Subscription Plans, Data import assistance. Investigation:-

  1. System is operational but performance very bad

  2. Deep Issues that require investigation in the core such as Stock Balance mismatch, Email delivery and performance, network issue for 3 or more Users Bug:-

  1. System is operational but behaviour of a specific feature or module is incorrect

  2. Error Reports reported by User are automatically tagged as Bug Service Request:-

  1. When User reports a service request like major version upgrade, upgrade of subscription plan

2.6 Support Resolution Times


In case of Standard Service Levels, the response and resolution times of the issues are as specified below:-

Issue Priority Response Time Resolution Time
Unclassified 2 hours 4 hours
Critical 1 hour 4 hours
Functional Query 2 hours 16 hours
Investigation 2 hours 16 hours
Bug 2 hours 40 hours or next release
Service Request 2 hours 40 hours


In case the Customer has purchased Priority and Phone Support from KAINOTOMO, the response and resolution times of the issues are as specified below:-

Issue Priority Response Time Resolution Time
Unclassified 1 hour 4 hours
Critical 1 hour 2 hours
Functional Query 1 hour 12 hours
Investigation 1 hour 12 hours
Bug 1 hour 32 hours or next release
Service Request 1 hour 32 hours


In case the Customer has purchased only L2 bug support from KAINOTOMO (applicable only for KAINOTOMO software's, KAINOTOMO Framework and HR/Payroll apps), the response and resolution times of the issues are as specified below:-

Issue Priority Response Time Resolution Time
Unclassified 2 hour 4 hours
Critical 1 hour 4 hours
Bug 2 hours 32 hours or next release

These hours are subject to:

  1. The matrix shown above is for defined Business Hours.
  2. The response and resolution time are indicative and not final. Actual resolution may depend on factors that may be out of control such as unavailability of server etc.
  3. KAINOTOMO does not accept any penalty if these support requests are not resolved within the indicative times.
  4. Fixing is subject to the Release Process as mentioned under Section 5 of this Agreement. These levels and support hours may change based on continuous improvement of our services.

III Release Process

3.1 Release Cycle

KAINOTOMO ensures that security fixes, bug fixes, upgrades, feature enhancements are deployed and released timely. Following is the release process:

  1. Regular Releases: Minor version releases for resolution of the bug fixes, new features, enhancement of existing features will be deployed once every three months. Issues tagged as Bug, Service Request, Discomfort are fixed/released in the said period.
  2. Critical Releases: To ensure that there is no compromise on customer experience, KAINOTOMO will resolve Issues tagged as Critical within 24 business hours.

3.2 Deployment

Deployment of release will be done based on the deploy mechanism that is setup. If you are on KAINOTOMO Hosted Instance, the deployment is done in off peak hours and primarily there is reasonable minimum downtime.

For critical issues, deployment will be done as soon as the issue has been resolved and the release has been cleared for release.

IV Escalation Matrix

To report an Issue, Customers shall raise a support ticket by visiting In case, the issue has not been resolved according to the SLA Agreement, the issue can be escalated by reporting it via