Partner Service Level Agreement

Date: 01st Jan 2020

1. Introduction

This document is indicative of the scope, terms of support, exclusions, release, and deployment schedule that will be applicable to all customers who have subscribed for Partner Services.

Since we are improving our services to improve our customer experience, this support agreement is only indicative and is subject to change.

This document covers the scope, inclusions, exclusions, categorization, resolution details of what is covered under Partner’s standard support contract.

2. Definitions

  1. Agreement means this service level agreement which describes the support policy of Partner that will apply for all users hosted with Partner.
  2. Cloud Service means any distinct, subscription-based, hosted (and maintained) services that are offered by Partner.
  3. Customer means the company or other legal entity that is the owner of the data for this Partner account.
  4. Customer Data means electronic data and information submitted by the Customer to the Services, excluding content from third-party applications, integrations.
  5. Database means the underlying database that stores the Customer Data.
  6. Documentation means the applicable web resources pertaining to the information of using ERP, updated from time to time, the comprehensive Do-It-Yourself Guide, accessible via or from within the Partner Account.
  7. Downtime means the time there was unavailability of Partner account due to maintenance activity at our end.
  8. Partner Account means the web URL for accessing the account Customer has subscribed for with Partner. This is synonymous with Partner Site. Basically, the URL that should matter to you!
  9. Partner means Partner Consulting Solutions.
  10. Issue means a support ticket that has been raised by a Customer or an Authorized User for reporting an incident or requesting service requests.
  11. Services means the products and services that are ordered by the Customer under a Subscription Agreement form or provided to Customer free of charge (as applicable) or under a free trial, and made available online by Partner. More on this in section, Service Levels.
  12. Subscription means the active hosting, server or support plan that the Customer has paid for availing Partner Services.
  13. User means any individual to whom customer grants access for accessing the Partner Account.
  14. User Role means the role granted to the Users in Partner account. Different User Roles have various permissions and access control is exhibited using User Roles.

3. Customer Responsibilities

Customers will be responsible for:

  1. Identifying a Project Champion who will also be the system manager (Single point of contact for Partner in the Customer’s organisation).
  2. Project Champion will be authorized to raise service requests like version upgrades.
  3. User compliance will be done by the Project Champion (User and User Role management is the responsibility of system manager).
  4. Before raising a support ticket, the User is expected to refer to the excellent online resources, documentation, and ERP Video Tutorials.

4. Service Levels

Effective support services are expected to result in maintaining consistent service levels. The following sections provide relevant details on service availability, monitoring of scope of services and related components.

4.1 Support Scope

The scope of this Service Level Agreement includes:

  1. Functional support: Includes support on all standard features of ERP
    1. Configuration support: Support for configuring workflow, print format
    2. Scenario support: Mapping User’s specific business use-case
  2. Issue Investigation: Examine the reported behavior of feature when it is not exhibiting expected functionality.
  3. Bug fix: Fixing verified bugs after Investigation. Bugs will be fixed based on severity and criticality and included in our regular release process. Critical bugs will be taken up on priority and released immediately.
  4. Data fix: Includes support for correcting data if it is an outcome of verified bug.
  5. Upgrade Support: Upgrading and maintaining latest version of app in Partner Account.
  6. Scaling Support: Optimizing database to improve performance wherever deemed necessary.

Partner takes best efforts to provide enriched customer experience to all Users. The scope of this SLA can extend (depending on several parameters) and may include:

  1. Minor feature request
  2. Minor feature redesign

4.2 Support Exclusions

The following items are not included in support. Our consultants may do these activities on a case basis but there is no obligation for us to do these for support. The reason is that these can be time consuming activities based on scale and scope. Our consultants can train you to do these activities but they are to be done by the Customer. These activities include:

  1. Data Entry
  2. Custom Script
  3. Print Format
  4. Data Import
  5. Manual Data sanitization
  6. User Management
  7. Permission Management
  8. Infrastructure
  9. Workflow

4.3 Support Hours

Coverage parameters specific to the service(s) covered in this Agreement are as follows:

  1. Business Hours: 9:00 to 17:00 (Saturday-Wednesday)
  2. Support Email:
  3. Telephone: +967-01-252935
  4. Only email support available on weekends (Thursday-Fraiday).
  5. Emails received outside of these hours will be collected and we will try to ensure solving the issue the same or next business day.
  6. Calls received after specified hours, weekends, will be forwarded to a designated IT Engineer. The best efforts will be taken to rectify the problem as per the business hour response matrix.

4.4 Support Levels

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

Sr. No Issue Priority Description
1 Unclassified
  • All Issues are tagged as Unclassified when they are received
2 Critical
  • System is inoperable / not functioning
  • Impact threatening productivity
  • Server Failure
  • Network down for whole Office
3 Functional Query
  • Issues ranging from functional queries related to various features and modules of ERP, Cloud Subscription Plans, Data import assistance.
4 Investigation
  • System is operational but performance very bad
  • Deep Issues that require investigation in the core such as Stock Balance mismatch, Email delivery and performance, network issue for 3 or more Users
5 Bug
  • System is operational but behaviour of a specific feature or module is incorrect
  • Error Reports reported by User are automatically tagged as Bug
6 Service Request
  • When User reports a service request like major version upgrade, upgrade of subscription plan
7 Dormant
  • Issues are automatically tagged as Dormant when there is no response as from User for 4 days after last response from Partner
8 Discomfort
  • System is operational but behaviour of a feature is not as per expectations
  • Scalability issues that cause mild discontent to Users while using ERP
9 Vulnerability
  • Security vulnerabilities that can compromise Customer Data

4.5 Support Resolution Times

For the above Issue Types, the response and resolution times are as specified below.

Sr. No Issue Priority Response Time Resolution Time
1 Unclassified 12 hours 12 hours
2 Critical 4 hours 12 hours
3 Functional Query 6 hours 24 hours
4 Investigation 6 hours 16 hours
5 Bug 12 hours Next Release
6 Service Request 12 hours 32 hours
7 Dormant 12 hours 32 hours
8 Discomfort 12 hours Scheduled Release
9 Vulnerability 12 hours 64 hours

These hours are subject to:

  1. The matrix shown above is for defined in 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. Partner does not accept any penalty if these support requests are not resolved within the indicative times.
  4. Fixing is subject to release (see Release process below). These levels and support hours may change based on continuous improvement of our services. For latest terms please check

5. Release Process

5.1 Release Cycle

Partner 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 periodically every third month of the year. Issues tagged as Bug, Service Request, Discomfort, Vulnerability are released once a month.

  2. Critical Releases:

    To ensure that there is no compromise on customer experience, Partner will resolve Issues tagged as Critical within 24 business hours.

5.2 Deployment

Deployment of release will be done based on the deploy mechanism that is setup. If you are on Partner Cloud, the deployment is done in off peak hours and usually there is minimum downtime.

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

6. Escalation Matrix

To report an Issue, Users should send an email to

If the Issue is not resolved, they can follow the escalation matrix defined below: