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

8947 Ideas

eiren.smithContributor

Use Asana-style Inbox instead of Notifications pulldown.Closed

In terms of practical use (including helping users avoid forgetting about things they need to do), Asana's Inbox is an inspired design. Here's a brief comparison of Asana's Inbox to Freshdesk's Notifications pulldown: Notifications go into Asana's Inbox. Not really different so far. Asana's Inbox list (notifications) are a central focus of the page, not a tiny pulldown. Asana Inbox entries (notifications) have an X button next to each so user can remove the entry once he's done with it. This is beautiful! Empty list = no more notifications to attend to. Freshdesk notifications are bold until clicked on. If you accidentally click on one, it will be un-bolded, increasing the risk you will fail to attend to it. This is avoidable, inherent risk of error — broken UX. There is no way to remove just one entry from the list and, less importantly, no way to mark an entry bold again. These may seem like minor differences. They are in fact major differences. The Asana Inbox approach creates a framework that inherently reduces the chance of errors (the primary error being thinking you attended to a notification, but you actually didn't attend to it, resulting in reduced quality of customer service). This is a case where the SaaS vendor (Asana) really considered the problem and found a solution that delights, rather than settling for a solution that seems okay on the surface, but which is actually pretty shallow.

s.de.jongContributor

Communication within ChangesClosed

In order to improve our change process and include\inform our customer in this process (if the customer is the initiator of the change) we want to have some of the communication options in a change as we do have in an incident. We need to be able to send a reply to a customer from a change, and if the customer replies to that message, we want it to be added to the change as a note. This would really speed up our change process and would eliminate the work we now have to do to communicate about a change with a customer. For example, if a customer ask us to implement a new module on his website, he is the initiator of the change and will request this by submitting a Service Request. After an agent does the intake of the Service Request there he will create a change, close the Service Request and start building the new module, test it and implement it. If there needs to be any communication to the customer regarding the new module (design questions,  verification that is works, other questions) it has to be done by an email from the agent to the customer outside of Freshservice. This is a lot of work and should be done in the change for better overview on what is done in the change, what is communicated and what not. If you add a note to the change to ask a customer a question it is possible to use the notify an agent option. If you enter the email address of the customer here he will get an email with that question. But when he answers the question there is no update to the change, it is registered as a new incident instead. The solution for this is that it should be possible to send a reply from a change to a customer, and when the customer responds to that message, the response is added to the changes as a note. This should work in the same way as it does in the incident module of Fresh. So send a reply, and if the reply is answered add it to the change. This is something that is requested by our customers as well, as they want to be involved in the changes we do for them.

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.