Service Level Agreement

Policy last updated on June 13 2021 12:06:44.
  1. Home
  2. Service Level Agreement

Workberri Cloud and Self-Hosted Service Level Agreement (SLA)

1. General Regulations

1.1. Workberri provides support services to the company's partners and customers. The Workberri technical support service helps to settle problems outlined in this document according to the established Service Level Agreement.

1.2. Questions that are beyond the scope of technical support should be directed to the specialists of hosting companies, third-party software developers, etc. The technical support service cannot resolve problems that concern the maintenance of a web project created by Workberri partners for an end user unless these problems are in some way related to errors in Workberri products.

1.3. Workberri does not provide web design, development or hosting services. We provide only general consultation for problems concerning hosting server configuration and server software installation by giving references to the Internet resources and the related documentation.

2. Working Hours and Response Times

2.1. Workberri Helpdesk operates between 10:00AM and 5:00PM IST on business days. A business day is considered every official working day of the week, excluding public holidays and weekends.

Technical support requests are processed on a first-come, first-served basis. High urgency level requests that require immediate response or the direct help of tech support specialists may be processed out of turn. High-urgency requests are those concerning the full or partial recovery of web projects.

The problem-solving period depends on the request urgency level, problem complexity and the potential need to hand the request over to the development department.

2.2. Problems that cannot be resolved in the context of the current software version are sent to the Workberri development department, which means that the fix will be included in the subsequent update. The planned term of the software update release is defined during the problem diagnostics respecting the general software development plan.

2.3. The technical support service cannot guarantee a fixed problem-solving period because there are a number of influencing factors: client's timely replies; response time of a hosting company; the need to prepare and release a software update, etc.

The response period depends on the current technical support service workload and can vary from a few hours to a few days, depending on the complexity of the issue. Sometimes, a problem can be solved immediately upon the receipt of a request or additional information from a client or user. The response of technical support specialists to additional information can take more time, especially if the issue in question will require the involvement of a software engineer or web developer. In this or a similar situation, making a phone call to the sales department has no practical consequence because it will not accelerate the problem-solving process.

3. Scope of technical support issues

3.1. Installation And Configuration

The following problems are within the technical support scope:

  • Server-side installation assistance for both demo and commercial versions. The consultancy coverage is limited to a product installation guide.
  • Recommendations on resolving typical problems occurring during the installation.
  • General recommendations on using the back-up software and scripts for the server-side project deployment; migrating from a local to a remote server.


The following problems are beyond the technical support scope.

  • Server-side software installations.
  • Preparation or moving of back-up files to server.
  • Diagnostics of software installed on a client's server or local computer.
  • Installation of server software on a client's server or local computer.


3.2. Enhancement of product performance

The following topics are within the technical support scope:

  • General recommendations on choosing proper server software to enhance the web project performance.
  • Recommendations on configuration parameters for a given software product, as provided in the "Recommendations on Configuring Web Systems" downloadable manual.
  • Assistance using the built-in caching mechanisms and other features, allowing reduced site load.


The following topics are beyond the technical support scope:

  • Configuration of software on the client's computer or server.
  • Diagnostics or stress tests on the client's server.
  • Optimization of the code or algorithms of any components or modules on demand.


3.3. Product Updates & Maintenance

The following topics are within the scope of technical support:

  • Investigation and elimination of license key problems occurring during software update.
  • Detection and elimination of problems that might be caused by an incorrect product update installation process.


The following topics are beyond the technical support scope:

  • Assistance with server connection problems or proxy connection configuration.
  • Configuration of the client's server or server software for compatibility with an updated system.


3.4. Workberri Products Errors

The following topics are within the technical support scope:

  • Workberri product runtime and operation errors; operation failure and system recovery. Assistance with system failure trouble-shooting and correction.
  • Workberri software errors. Diagnostics aimed to determine the reason of software error. The identified error, if any, can be eliminated either through diagnostics or in the forthcoming updates, depending on the nature of the error.


The following problems are beyond the technical support scope:

  • Software installation error detection and elimination. (Only general installation recommendations can be provided)
  • Database errors. (Only general instructions or recommendations can be provided).
  • Server configuration or a product update installation directly to the client's web server. (Only general instructions or recommendations can be provided).
  • Server software error detection and/or elimination.


3.5. Development Questions

The following problems are within the technical support scope.

  • Workberri API usage consultation.


The following problems are beyond the technical support scope:

  • Consultation on general principles of programming.
  • Implementation of custom, user defined logical operations and algorithms.
  • Diagnosis of any 3rd party software code or any of its components.
  • Development of custom components or scripts, software modules, or website scripts.
  • Modification of code of the existing system modules or components to adapt them for specific business tasks (unless such modifications are in some way connected with essential bug fixes).
  • Development of custom payment system integration scripts.



4. Technical Support Procedure

4.1. The technical support procedure is initiated by a technical support request. A technical support request can be submitted in a number of ways:

  • by submitting a request via the webform on the CWS official websites;
  • by contacting Workberri staff via Workberri live chat.


After a request is submitted, it will be processed by the Workberri Helpdesk and Workberri Technical Support Department staff.

4.2. Each technical support request should include the following information in order to reduce the resolution time.

  • The problem description and the step-by-step procedure to reproduce the error (if possible).
  • The URL of a site where the problem occurs.
  • The software edition name.
  • The technical support specialists may inquire about information concerning the server software configuration and versions, and the configuration of a client's software (browser).
  • All problems should be described using commonly accepted web programming, software or hardware terminology.


4.3. If a certain action is required to be performed on the client's web server to resolve the problem, the support specialist may require the Workberri product license key and the web server authorization information for administration access.

Note that additional information like FTP, SSH or the hosting server Control Panel login and password may be also requested in some cases, for example, when additional measures have to be taken in order to recover the project operation or to diagnose update problems.

The authorization details (login and password) submitted to Workberri technical support team should be changed immediately after the problem is resolved. The technical support staff cannot and will not be responsible for the client's web project, personal data, or hardware and software performance after the problem is resolved and/or when the corresponding technical support request is closed.

4.4. After the Workberri technical support staff has received a request, the client receives a notification, which includes the technical support request information with a unique identifier (ID). If technical support is done via email, clients have to preserve the ID in the e-mail message subject field during the whole period of correspondence with the Workberri technical support staff. The forthcoming messages are appended to the initial message automatically. Clients can view the full correspondence in the technical support section on the Workberri website.

4.5. When you submit a support request, you can include screenshots and other images that can help to identify and resolve the problem. Screenshots are to be created in PNG, GIF, JPG formats (graphics in BMP format must be compressed using a ZIP archive software).

4.6. There are a number of circumstances that can delay or even abort the problem-solving process.

  • Lack of information required to resolve the problem.
  • A problem cannot be reproduced using a similar hardware configuration, or a client's website cannot be accessed using the authorization information provided in the technical support request.
  • The problem requires custom improvements of Workberri products that are currently being developed or not planned to be included into a later product release at all.
  • Improper use of Workberri products, including product kernel modification, exceeding of the allowed number of software installations, or general violation of terms and conditions of Workberri EULA (end User License Agreement) and/or Workberri SLA (Service Level Agreement).
  • Use of unlicensed copies of Workberri products.
  • The question is beyond the Workberri technical support service scope.
  • Incorrect, incomplete or misleading information given by the client
  • Use of foul language and insulting Workberri technical support staff.


5. The Technical Support Quality Rating

Workberri places high emphasis on the technical support service quality and provides the highest possible support service for all categories of users. After resolving a problem, we kindly ask you to evaluate the quality of our service.

If you suppose that your request has been prematurely closed, you can re-open it and define your question more precisely. You can send a message to the technical support service supervisor asking for accelerating the resolution of urgent questions or for comments on the request.