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

Sundaramk
Apprentice
SundaramkApprentice

Creation of Net Promoter Score reports ( NPS) in AnalyticsClosed

We would like to report on our Net Promoter Score ( NPS)It would be great if this could be added as a report in FD Analytics.Look forward to hearing from others in the forum on this topic. Some details of NPS for those who are unfamiliar with this. ( courtesy Survey Monkey). Let’s say you’ve sent out an online poll with the NPS question and the 0-10 scale, and you’ve received 100 responses from customers. What do you do with the results? Is it as simple as averaging the responses? Well, not quite. But it’s almost that easy.The NPS system gives you a percentage, based on the classification that respondents fall into—from Detractors to Promoters. So to calculate the percentage, follow these steps:Enter all of the survey responses into an Excel spreadsheet Now, break down the responses by Detractors, Passives, and Promoters Add up the total responses from each group To get the percentage, take the group total and divide it by the total number of survey responses Now, subtract the percentage total of Detractors from the percentage total of Promoters—this is your NPS score Net Promoter Score (NPS) formula  (Number of Promoters — Number of Detractors) / (Number of Respondents) x 100NPS calculation example  Example: If you received 100 responses to your survey:10 responses were in the 0–6 range (Detractors) 20 responses were in the 7–8 range (Passives) 70 responses were in the 9–10 range (Promoters) When you calculate the percentages for each group, you get 10%, 20%, and 70% respectively.To finish up, subtract 10% (Detractors) from 70% (Promoters), which equals 60%. Since an example Net Promoter Score is always shown as just an integer and not a percentage, your NPS is simply 60. (And yes, you can have a negative NPS, as your score can range from -100 to +100.)

MatthiasGuz
Apprentice
MatthiasGuzApprentice

Feature Request: Display Average Number of Tickets on Group and Team Level in AnalyticsFuture Consideration

Hi everyone,I would like to propose an improvement to Freshdesk's Analytics functionality. Specifically, I suggest adding the ability to directly display the average number of tickets created and resolved per team or group in Analytics.Currently, in the Helpdesk Ticket Volume Reports, I can only see the total number of tickets per agent or group. However, for our evaluations, the average value is crucial. For example, the calculation:(Number of tickets resolved by Agent 1 + Agent 2 + Agent 3 ...) / Number of agents.I’ve tried to achieve this using a custom metric, but unfortunately, I encountered syntax and aggregation issues. Freshdesk doesn’t seem to provide direct access to the number of agents within a group. Formulas such as SUM(Tickets.Tickets resolved) / COUNT(Tickets.Agent name) or AVG(Tickets.Tickets resolved) always result in errors.My suggestions:Introduce a metric that considers the number of agents within a group, enabling calculations like the one above. Alternatively, integrate a standardized feature in the Helpdesk Ticket Volume Reports that outputs the average number of tickets per group or team. Additionally, allow the anonymization of agent names to comply with data protection requirements. This is particularly important for larger teams, where individual performance should not be identifiable.Why is this important?Teams and groups operate with varying efficiency. Average values provide a clear overview without directly comparing individual agents. Especially in larger organizations, where data protection plays a critical role, these metrics are vital for evaluating team or group performance.If there are any workarounds I might have missed, I’d be grateful for your suggestions. Otherwise, I hope other users will also find this functionality valuable and support this idea.Thank you in advance!

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.