Skip to main content

Ideas portal FAQ

Find, vote on and share ideas for Freshworks products. Here is how it works and what happens next.

1. Idea stages and what they mean

Every idea has a status. It shows where the idea is today.

How does an idea move from submitted to delivered?
  1. Submitted
  2. Under review
  3. Planned
  4. In development
  5. Delivered

Not every idea makes it to the end. Some stay open for votes as Future consideration. Others are Closed.

You get an email each time the status of an idea you posted, voted on or subscribed to changes.

What does each status mean?
Submitted
We received the idea. It is open for votes and comments.
Under review
Product is looking at the idea.
Planned
The idea is on the roadmap. We have not started building it yet.
In development
Our teams are building it. We expect to release it within 12 months.
Delivered
The idea is live in the product.
Future consideration
We are not planning it now, but it stays open. Votes help us see if demand grows.
Closed
We are not taking this idea forward. See "Why was my idea closed?" below.
Does Planned mean a release date?

No. Planned means the idea is on the roadmap. Timing can change as priorities change. We update the status when work starts and when the idea ships.

2. The basics: from your idea to our answer

Six questions most people ask before they post.

What is an idea?

An idea is a request for a feature or improvement that is not in the product today.

Something broken? That is a bug. Please contact Support so they can help you.

Should I search before I post?

Yes. If a similar idea exists, vote and comment on it instead of adding a new one. Duplicate ideas split the votes, so no single idea shows how many people want it.

How do I submit an idea?
  1. Search. Choose Submit an idea and type a title. Similar ideas appear. Vote on one if it matches.
  2. Describe. Tell us the task you are trying to do and what gets in your way today.
  3. Add context. Pick the product area and tell us how much this affects your team. Add a screenshot if it helps.
  4. Submit. Your idea shows as Submitted.
How will I hear back?

You get an email when the status of your idea changes. To follow an idea you did not post, subscribe to it.

Why was my idea closed?

An idea can be closed for one of these reasons:

  • Merged. A similar idea exists. Your votes move to it.
  • Bug. It is something to fix, not a new request. Contact Support for help.
  • Retired. It no longer fits the product.
  • Already available. The product can do this today.
  • Not planned. We have no plans to build it.

Closed ideas stay searchable, so you can still read the comments.

3. Find ideas and share your thoughts

The quickest way to make an impact is to back an idea that already exists.

How do I find an existing idea?
  • Use the search bar on the Ideas page. Try two or three keywords.
  • Filter by product, so you only see ideas for the product you use.
  • Filter by status to see what is Planned or In development.
  • Sort by votes to see the most requested ideas first.
How do I vote on an idea?

Open the idea and select the vote button. Voting shows us which ideas matter to you. You need to be signed in to vote.

How do I add a comment?

Open the idea and add your comment. The most useful comments say:

  • What you are trying to do.
  • What stops you today.
  • How you work around it, if you do.

"I agree" helps less than a short example from your own work.

How do I follow an idea?

Select Subscribe on the idea. You get an email when the status changes or when someone replies.

I could not find my idea. What now?

Submit a new one. Use a clear title and describe the problem, not only the solution. Then we can see what you need, even if there is more than one way to solve it.

Have a bug or a question about how a feature works? Contact Support instead.

Ideas Status Pipeline

Filter by idea status

Filter by product

8947 Ideas

vikrant.tyagiApprentice

Inventory module is too basic that it's actually restrictiveClosed

Hello There, I find the inventory module to be very basic and hence limiting in terms of use cases that it can serve. For example, It's only obvious that I would want to hide some of the assets from some of my agents/users. But the only two ways I could find to do that is by using either of these 2 flags (see screenshot below). while defining my `Roles`  Now, firstly this is a non-feature disguised as a feature. Because the combination of two flags only allows you to either:-- show everything to everyone or - Show agents only the assets that are assigned to their Group.  There is a reason ITIL defines Asset Management specific roles. You cannot disregard them completely and still call a product ITIL compliant. This all or nothing approach for Asset Visibility is not only limiting, it starts dictating (as a side effect of missing adequate Asset Roles) how I should design my Support Groups. In our setup, we have created Groups so that I can hide certain assets from other agents. I don't want my Asset Visibility feature to start dictating the design of my support group, I am forced to do this because the tool doesn't have a sophisticated asset visibility mechanism. I guess I'm repeating myself here, I hope made the point!?!Not only this, the tool assumes that a `Group` is a way to segregate ’items’ in ITSM tool. A complete misappropriation of the concept of Groups in ITIL. A Group (Support Group) should only be to segregate tickets. Assets can be managed at different levels by different people in different ways. Few examples, I might want to give different levels of visibility to people in the same Support Group. A team lead might have access to all the items on the Group while a team member may only need access to fewer assets. This applies to the "Asset" level as well as "attribute" level. Say a team member can only see the serial numbers but not the asset ID or something like that. At the attribute level, it might look too specific but still desirable. There is a fundamental design problem here that is handled in a “let’s reinvent the wheel” way. We don’t have to. ITIL has already done that for us, so let’s just stick to what works. Why should my use case to hide assets govern how I design my support system? (Support Groups in this case). Support Groups and Asset Visibility are two different concepts and should be decoupled.  It pains me so much that basic things like these have to be reported in order for FS to consider it as a feature. I am obviously pointing out only the Inventory Module here but these patterns (or rather lack of it) are spread across all the modules. Problems that ITIL has solved are being tackled very wild-west ways. This sets the product on a very unpredictable trajectory, a roadmap that is anything but ITIL/ITSM. And this scares me. Some day when I run out of patience I might write a long post for all the other modules as well. But for now, this should serve the purpose I hope. Is it just me? Or others feel the same way? Feel free to call me out if I sound like a snowflake. 

This ideas board reflects customer feedback and our current thinking, and is provided for informational purposes only. Roadmap decisions, including AI-related capabilities, are influenced by many inputs beyond customer votes, such as technical feasibility, security, compliance, and market conditions. They are subject to change without notice. Idea status labels (such as “Under Review” or “Planned”) do not constitute a commitment, promise, or legal obligation to deliver any feature, functionality, or timeline, and are not part of any agreement with Freshworks. Development and release of any product or feature remain at Freshworks’ sole discretion.