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

8948 Ideas

thanos.massiasContributor

Threading by subject ( to avoid multiple new tickets )Closed

Proper email threading is well described in https://www.jwz.org/doc/threading.html and relies heavily on the In-Reply-To and the References headers of an email and, if all else fails ( and this is extremely IMPORTANT ), on the Subject of the email - a technique called threading by subject. "Threading" means that when Freshdesk receives a new email it has to decide if it belongs to an existing ticket ( in which case it add the email to the thread of that ticket ) or not ( in which case it generates a new ticket ). We have a good number of customers that use exotic mail systems. These systems send replies that don't provide proper In-Reply-To and References headers ( if they provide them at all ). We also have customers that compose new emails and just use the Subject of our reply as the Subject of their response email in the belief that this is enough. Judging from the fact, that other Freshdesk users also mention such cases, I believe that my problems are not unheard of but just more prevalent. We have past experience with systems that used threading by subject and could handle these emails. My understanding from testing competitive products, is that a number of other helpdesk platforms, also implement decent threading by subject. In most cases, the threading by subject implementation in helpdesk platforms relies on searching the Subject of the incoming email for a string that can be matched to a ticket number.  For example, it can be configured to look for the first occurrence of  SometextSomenumber and use Somenumber as the ticket number. Example Subject of a customer reply, with COMPX used as Sometext:    Subject: Re: [ Case: COMPX674591 ] My gizmo is not working. A threading by subject system that works as described above, will conclude that 674591 is the ticket number and, if a more reliable match cannot be made on the basis of In-Reply-To and References headers, will add the email to the thread of that ticket. My understanding is that Freshdesk does not implement threading by subject ( but I would be very happy to be proven wrong ). I REALLY want Freshdesk to implement threading by subject ( and give the admin the option to enable or disable this feature and select the Sometext value they want ). If you are a fellow Freshdesk user that has faced problems with multiple tickets been created when customers with problematic email systems reply, please support this feature request.

carltContributor

Better Development Process and More Transparency Of TimelineClosed

I like many in this feature request forum are frustrated to see ideas with strong support sit un implemented for many years. And then also some features that are implemented feel half baked and incomplete. eg. Slack integration I don't know what your current internal resourcing and development process is and how it works but as an outsider it feels like it needs to be better. Having dedicated teams to specific features so that development can be continuous and the product keeps getting better and better as feedback comes in and not have one feature take all the developers away from other features getting worked on. Maybe you already do this but it doesn't feel like it. Also I'd like you to re-look at transparency and seek your customers feedback more in your plans for the development. A previous company I used to use software from would provide us a whole document outlining the scope of the feature they planned to implement and got customer feedback on it before they even started development to ensure they got the right use cases and features needed for the initial launch. This was great. They then updated us with delays and problems every single month once development started so we knew a feature was being worked on even if late and understood why it was taking longer than expected. I often see features being released that I cant' even find in the feature request forum, or have very little votes while other highly commented and voted for ones ones sit lacking. This is probably my biggest feature request :)

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.