How we handle BR requests

Smart-Acc Solution has advanced software used by thousands of organizations, all around the Malaysia. That means we receive a lot of great feedback, suggestions and wishes from our 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 time frame 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, so have outlined how we handle feature requests below.

 

Feature requests in general

  • You are invited to share your feedback and suggestions about feature requests in the feature requests section of the community forums.
  •  We do not implement features based solely on their popularity - we take a number of factors into consideration.
  •  We do not provide estimate time for feature requests or publish long term road maps at this time.

 

Making a feature 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, search the feature requests topic to see if someone else has requested it.
  • If you find one, please show your support for an existing request (it is more likely to gain attention than if you post a duplicate one) by saying how you would use a feature rather than simply saying "me too!" or "+1" on the request.
  • If you need to create a new feature request, create a new posting in the appropriate product section.

Creating a feature request

We will recommend follow our guideline to create a new feature request on the forum. It will help us to understand and gain the chances in development list.

  • Please focus on one suggestion and submit a separate report for each suggestion you have.
  • Key point on your feature request content
    • What will this feature request accomplish?
    • What is the benefit of this feature request?
    • Who are the key person? ( Etc. Sales person / Accountant )
    • How is the presentation of the feature request? ( Etc. Interface / Report Format )
    • When is the timing on using the feature request? ( Etc. Year End / Monthly )
    • Attachment for screenshot will be great.

 

Tracking feature requests

  • When we decide to implement a feature request, we may log it in our development tracker.
  • If a feature request has a tag such as [PLANNED] that means it may make into a future update. This is not a guarantee.
  • Remember that we do not publish long-term road maps. We have internal product road maps to plan our future releases.

 

What goes in, what stays out

We take into account a number of factors when deciding which feature requests to implement. This is a combination of feedback from our customers, people we consider power-users, our own market research, the availability of our own team and resources, and how the feature fits in with our long-term product plans and strategy.

 

Terms and Conditions:

You agree that by submitting your Idea, you acknowledge and agree that any such Idea is non confidential, and that Smart-Acc Solution has no obligation to return anything submitted, respond to, or confirm receipt of your Idea. Smart-Acc Solution shall be free to use any Idea that you submit on a perpetual, royalty-free basis, for any purpose.