Some seem to be in high demand and are extremely useful, yet no action taken.
Based on the above:
How often are the “Wishlist” feature requests reviewed by Team Elfsight before a final decision is made? (i.e., Go/No-Go)
How many votes are needed to ensure a “Wishlist” feature request becomes a scheduled, release item?
Does Team Elfsight have a Product Roadmap (public version) they can share and post? It would be extremely helpful and keep your customers quite happy. Our company does that for our customers and they love it.
Please Note:
There are many “Wishlist” feature requests posted in this community forum that are already offered by other AI chatbot widgets. As you know, falling behind in releasing the most-popular (and “common sense”) feature requests will impact sales. Please don’t let that happen. You guys have an awesome platform and products to build from.
As much as we’d love to release new (and highly anticipated) updates and features, we need to keep a lot of factors in mind.
I’ll try to break down the idea behind the Wishlist category and the way we handle all inbound suggestions.
First off, the Wishlist category is open for any Elfsight user to share any idea, suggestion, or request, and we try our best to consider them. However, we cannot guarantee (and never do) that a suggestion, no matter how popular it might become, will be released 100%.
And these are the main reasons:
Team involvement in urgent tasks: We also focus on infrastructure maintenance, global updates (like overhauling the dashboard or updating billing workflows), which may shift priorities or delay release dates.
Model considerations: Not every request aligns with the model we follow. We aim to provide the best tools, but we also need to keep them affordable. This puts limits on what we can do.
Prioritization by technical complexity: Some features that seem simple might require months of preparation, and we need to factor that in when deciding what to add to the roadmap.
Now, circling back to your questions:
We review our Wishlist category once a quarter to add new suggestions to the roadmap. Usually, such requests get marked as “Planned” here on the forum, so you’ll know what we’re currently focusing on.
There’s no fixed number of votes required, but we do consider the most popular requests first. Typically, “most popular” ones start with 50-60 upvotes.
While public roadmap sounds like a great idea, we don’t have one just yet. Even having a roadmap doesn’t ensure everything will go according to the plan, and we don’t want to create false expectations. If anything changes in this regard, we’ll reconsider sharing a public roadmap with the community
For now, you can keep tabs on In-Progress and Planned tags - these indicate what we’re currently working on.
As for the AI Chatbot widget, we’re on the same page - I know the dev team is giving it special attention, so let’s see what new updates we can expect
Thank you for your involvement, Petar, always happy to hear from you!
Great explanation. Since your AI Chatbot widget is one of the most-recent ones released by Elfsight, it would be nice to see key feature requests released soon (say, within the next 30-60 days).
PS: Not trying to bump any feature requests via this topic, but implementing the “upload attachment” and “voice command” feature requests to the widget would be nice. They are popular, too (i.e., competitor widgets already offer these features).
It would really help to know how often wishlist requests are reviewed and what actually drives a feature decision—votes, demand, or feasibility. Some highly requested items have been sitting for years, while competitors already offer them.
A simple public roadmap or status update (under review / planned / not planned) would add a lot of transparency and trust. Elfsight has a strong product—clear communication here would only strengthen it.
Thank you for your interest, @Sophie_Clark, and welcome to the community!
In short, when we look at feature ideas, we try to balance their potential, technical complexity, and our current workload. A public roadmap is a really nice idea, and we’ve actually talked about it before — but for now, we decided to pause on it so we don’t create false expectations if things don’t go according to the plan.
