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

ShubhamJadhav
Apprentice
ShubhamJadhavApprentice

Why don't we have account inactivity notification triggers to users?Closed

Dear Freshdesk Team,I hope this message finds you well. I am writing to suggest a valuable feature enhancement that could significantly improve the security and user experience across the Freshdesk platform.Feature Request: Account Inactivity Notification TriggersPurpose: Introducing account inactivity notification triggers would help alert agents or users about their inactivity for a specified period. This proactive approach would encourage timely logins, ensuring the system remains secure and active accounts are monitored effectively.Benefits:Enhanced Security: Regular notifications for inactive accounts will prompt users to log in, reducing the risk of unauthorized access or dormant accounts being exploited for malicious purposes. Improved User Engagement: Users who might have forgotten about their accounts can be reminded to log in, ensuring continuous engagement with the platform. Proactive Account Management: Admins and security teams can better manage user activity and take necessary actions for accounts that remain inactive for extended periods.Implementation Suggestions:Customizable Inactivity Period: Allow admins to set the duration after which a notification should be triggered based on their organization's security policies. Notification Channels: Support multiple notification methods, such as email, SMS, or in-app alerts, to ensure users are effectively reached. Automated Actions: Option to automatically suspend or deactivate accounts after a prolonged period of inactivity, with prior warnings sent to users.By incorporating account inactivity notification triggers, Freshdesk can further its commitment to security and user experience. This feature will not only safeguard the platform but also enhance the overall productivity of its users.Thank you for considering this request. I believe it will add significant value to Freshdesk, and I look forward to your positive response.

jennevaContributor

Problems FunctionalityClosed

UI Suggested Updates for Problems We are presently using PROBLEMS quite heavily in our Org. One thing our teams have noticed is the restrictive functionality with Problems. Here is some feedback on some pain points for our teams When you are trying to do a Bulk Update on tickets, there is no way to assign Problems to multiple tickets at once. When Bugs come in, we see a high increase of tickets, so to be able to assign the increase of tickets to a Problem from the Ticket Overview Page Creating a VIEW option within the columns in Problems that showed the PRB ID would be extremely useful.  Currently the PRB number lives within the Subject Column and is at the end of the Subject. depending on the Problem Subject, it is usually cut off When Associating a PROBLEM to a ticket, the Association UI is quite difficult to work with when there are multiple Problems The search functionality is not very good at finding tickets in the picklist. eg. typing “payment issue” in the search, we may get back 0 Results found, when there are a few different tickets that have the keyword Payment in the Subject Line - Where is this SEARCH BAR pulling the query from? (eg. Decription, Subject?) The list shows Closed problems. So if we are unable to find our PRB via the SEARCH option, we are stuck scrolling through all tickets within that Group. Piggybacking off of 3.2 above, there is no way to set Business Rules and the Workflows are very limited in the Admin options. When looking at ALL PROBLEMS, the system standard autofills to 6 MONTHS. It looks like this can only be edited by saving a new view of ALL PROBLEMS and setting that filter - this has resulted in many teams asking why their Problem has disappeared, and me needing to continuously explain why that happened and how to see the Problems outside 6 months. And finally, this is more of a wishlist item for myself, but removing the mandatory Due Date field. For our developers. Our developers work in Sprints and pull in Bugs into their sprints (into ClickUp...via an integration with Zapier) as they have time/space to work on them. Within Freshservice, this Due Date is not managed at this level, but once it reaches their queues. Thanks!

ViniciusMaiaPT
Apprentice
ViniciusMaiaPTApprentice

Features request in FreshdeskClosed

1. Save filters in advanced searchSometimes, a user searches for specific information in the search bar and uses the filter pane to make a granular research. The point is that they'd like to keep those filters + the research in order they could use it again if they needed. 2. Add "Subject" in the ticket filtersCustomer would like to filter tickets by its subject, but in the filter pane, we do not have the option "Subject" to filter by. 3. Order tickets by category/subcategory in table view.We can see that we can order to tickets by Subject and Priority, for example, but we cannot order them by Category/Subcategory. It would be of much help for the customer to enhance productivity. 4. Merge tickets in the search barCustomer need the option to merge tickets in the search bar, but as you can see, it's impossible to select them and merge from the search list. They only can do this in the tickets view. 5. Update tickets automaticallyAs you know, every time we change any information in tickets, we must press "update" bottom in order to save changes. The customer would like to know if there is any change to save information automatically once the changes are made. 6. Update tickets list automaticallyWhen a ticket is updated, others agents see the tickets list with the option to update the page. Customer would like to know if there is any way to update the page automatically after some time, because, for now, the page is only updated manually.

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.