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

8951 Ideas

jcapitan-shoreline
Skilled Expert
jcapitan-shorelineSkilled Expert

Streamlining Bulk Updates: Less Frustration, More EfficiencyClosed

The current bulk update process in Freshservice, particularly concerning required fields, is a significant source of frustration and inefficiency. Users should not be forced to engage with data they don't intend to modify, especially when it leads to a time-consuming and error-prone experience.Consider this common scenario: I needed to update a set of assets. The process required me to have two tabs open simultaneously – one to identify the mandatory fields and another for the export settings. I had to constantly switch between them, meticulously checking off all the required fields for export, even if they already contained the correct data.After a painstaking export and extensive data manipulation, I attempted to upload the updated assets, only for the upload to fail because I had missed a required field. This meant repeating the entire export process, this time including the newly identified field.The frustration didn't end there. Upon the second upload attempt, the process failed again due to an incorrect date format in a field I never even intended to modify. This forced me to reformat an entire column of data, further extending a task that should have been straightforward.This convoluted process significantly hinders productivity. We should be able to perform bulk updates without being coerced into exporting, reformatting, or re-uploading data for fields that are either already accurate or irrelevant to our intended changes.

travisbondApprentice

Ticket Threads - Notifications and VisibilityClosed

  After a couple of years with Threads and moving over from “Discussions” I have these suggestions for “Threads” that would be great to implement. They were already involved in Discussions, so it seems like a step back to not have this feasibility.Would it be possible for us to have a view of all tickets in which we are mentioned in threads, with a task? For example, in the notification bell, might we be able to “filter” notifications in which we are specifically mentioned in a thread? As was the case in FreshConnect, having the little widget in the bottom, right-hand corner provided a handy method of returning to previous tickets in which we were mentioned, in the event we weren’t able to tackle a project immediately in which we had been mentioned. Currently, we are notified on the bell, as well as email; however, our company relies heavily on this internal communication/collaboration within Threads and discussions for teamwork, so it’s easy for them to get buried or lost in emails if the notification is just a single instance notification without a designated placed to return later. Having something like the attached would be handy to be able to revisit those later. Doing the “highlight” feature in FreshConnect was handy, being able to isolate a particular part of the conversation within a discussion. Is there any possibility that functionality could be incorporated into the “threads”? PLEASE can we set a preference to MUTE a thread unless we are specifically @mentioned within it? I cannot express how many times I have been notified of a response in a thread that has nothing at all to do with me. It’s very distracting!

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.