How We Handle Feature Requests - SLA Feature Request Policy

How We Handle Feature Requests - SLA Feature Request Policy

Novohit and HotelRSV is a comprehensive ERP Software used by several organizations all around the world. That means we receive a lot of great feedback, suggestions and wishes from customers of all shapes and sizes.

Unfortunately, this means we need to say 'no' a lot more than we would like. In fact, in many cases we are unable to provide a response or timeframe to each feature request. However, we do read all of the feedback and suggestions sent to us and prioritize feature request based on a number of factors.

We want to be transparent about the way we handle feature requests, we have outlined how we handle feature requests below.

General Requests

  • We do not implement features based solely on their popularity - we take a number of factors into consideration.
  • We do not provide ETAs for feature requests or publish long term roadmaps at this time.

Making a Request

We regularly review feature requests and suggestions made on the forum. The forum is where suggestions start out, where they gather popularity and evolve as ideas.

  • Before creating a new feature request, be sure no one in your organization has requested it first. 
  • If you find one, please show your support for an existing request.
  • If you need to create a new feature request, create a new posting in a ticket with the appropriate department. Read How to Make a Feature Request

Tracking Requests

  • When we decide to implement a feature request, we may log it in our notification center at and our official blogs at and
  • When we schedule a feature request, we will set a 'target version' for the entry in the development tracker.
  • Remember that we do not publish long-term roadmaps. We have internal product roadmaps to plan our future releases. Scheduling in the development tracker does not tell the whole story, our blog indicates what is coming up soon.

Requests to Implement

We take into account a number of factors when deciding which feature requests to implement. This is a combination of:

  • feedback from our customers,
  • Novohit and HotelRSV software and field experts,
  • our own market research,
  • Government Laws, regulations and Compliances
  • the availability of our own team and resources and how the feature fits in with our long-term product plans and strategy.

API Integrations

Novohit has API Webservices available. Any connectivity has these three basic requirements:

  1. NDA, confidentiality agreement and commitment to protect confidential data.
  2. Proper Identification of the Third-Party Developer.
  3. Verification process of the integration. The developer must submit the app for review from our staff.

Our APIs are subject to our SLA.

    • Related Articles

    • How to Make a Feature Request - SLA

      Due to high demand on Electronic Accounting and Electronic Invoicing, our development staff will not be reviewing development requests until Feb. 2015. Feature Requests and Roadmap Policy We maintain an official policy document about this on this ...
    • Meetings & Consulting Services Policy - SLA

      In order to support the quality of the dedicated service, the meetings requested may be considered as additional consulting with a charge per man hour, since in most cases they are not included in the SLA Novohit Support, Backups, Upgrades and ...
    • SLA Novohit Support Backups Updates Monitoring SBUM Service Agreement

      The following document details the SLA (Service Level Agreement) of the recurring agreement for Support, Backups, Upgrades and Monitoring Services (SBUM). 1. Services Included Operational support (*) by our multidisciplinary and certified team for ...
    • Test Environment Policy - SLA

      Novohit has test environments that allow operating conditions similar to the current one to be replicated. These test environments can be used by our Support Staff to review cases or requests and test new features before implementing them. Sometimes ...
    • Specifications on EMERGENCY Priority and Extra Charges

      This document is referenced by Operative Support, Backups and Updates Service Agreement (SBU) Since came live in 2012, we've upgraded our support Service Level Agreement and been able to reduce response times by 30%. In average, our ...