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

jrodierContributor

Show all fields when creating new Problems, Changes & ReleasesClosed

Currently, when creating a new Problem, Change, or Release, the form fields are limited. Yes, you can create custom fields and this and that, but you cannot re-use fields that are already part of the particular entity. What I mean by this is that once you create a new PRB/CHN/REL, you are given new fields to fill in - For Problems, you are given the "Analysis" section with the "Root Cause," "Impact," and "Symptoms" fields available for filling in. For Changes, you are given the "Planning" section with the "Reason for Change," "Impact," "Rollout Plan," and "Backout Plan" fields. Lastly, for Releases, you are given the "Planning" section with the "Build Plan" and "Test Plan" fields. We are looking to see if we can get these sections to be a part of the initial creation of the PRB/CHN/REL. Right now, we have it set up so that whenever one of those things is created, our whole team is emailed with the context of the submission. We would like to be able to fill in these additional fields before the email is sent out to our team. This way, everyone can also be made aware of the additional information as a part of the main info without having to go to visit the actual record. We also have seen agents just create the PRB/CHN/REL from the main form, and never go back to fill in this data, so we are hoping that this will help us get these fields filled in more often than not!If you have any questions, please ask!

thanos.massiasContributor

Individual class identifiers for custom ticket fields and custom company fieldsClosed

This is a sample list element (<li></li>) created for the 'My Test' custom ticket field:<li class="text custom_text field"><label for="helpdesk_ticket_custom_field_my_test_276082">Test text</label><input id="helpdesk_ticket_custom_field_my_test_276082" class=" text" type="text" size="30" name="helpdesk_ticket[custom_field][my_test_276082]"></li>This is a sample list element created for the 'My GUID' custom company field:<li class="show-field"><p class="field-label break-word">My GUID</p><p class="field-value break-word">6d2d2107-3112-4d47-a439-1b3b8ffd6e83</p></li>Neither list element has identifiers unique to the specific custom field. For example:If I have a 'My First Test' and a 'My Second Test' custom ticket fields I cannot use jQuery to hide just 'My Second Test'.I propose that an extra argument is added to the class of the list, probably based on the ID that Freshdesk internally uses for each custom field (and definately not based on something that might change like the name of the field).In this way, instead of 'My First Test' and 'My Second Test' both having the same list class identifiers:<li class="text custom_text field">each will have distinct list class identifiers, like:<li class="text custom_text field ctfid_345678">for 'My First Test' and:<li class="text custom_text field ctfid_743743">for 'My Second Test'(ctfid = custom ticket field id)When that is in place, I can use jQuery to its full power. I can hide/show elements, read/write option values, change css or whatever. This is really useful.Tip: Since some DOM elements, like the list of custom ticket fields, may not be available upon loading but may take some more time to come into existence, one can use something like https://github.com/uzairfarooq/arrive to watch for element creation. I already tried that and it works fine. If anyone is interested, one only has to include 'arrive.min.js' in her FreshPlug code and then try something like this:-----------------------------<script type="text/javascript" > jQuery(document).arrive(".text.custom_text.field", function() { // 'this' refers to the newly created element var $newElem = jQuery(this); console.log("Element created"); // Either of the next two lines will work (to hide the element) //jQuery(".text.custom_text.field").hide(); //$newElem.hide(); // unbind all arrive events on document element which are watching for ".text.custom_text.field" selector jQuery(document).unbindArrive(".text.custom_text.field"); }); </script>-----------------------------In fact, I would also propose that arrive.js is natively supported, if individual IDs for custom fields are implemented.

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.