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

info_14223Apprentice

2 or more agents working on same ticket, Problem with notification when adding notesClosed

Hello Guys, hello freshdesk support team, we have got a big problem if two or more agents are working on the same ticket.the notification fails when we add a private note to another agent. Therefore we started to switch a ticket among each other anytime when a comment was added, so that the other agent is able to see the note. very annoying. Let's have an example: Person A is Agent of a ticket. He or she can only solve it by getting feedback of Agent B. So he or she leaves a private note in the ticket and notifies the Agent B. but the email notification fails in many cases, so we must change the assigned agent, so that Agent B can see the ticket and the added note. Then let`s say agent B is also adding a note for Agent A... so again also the assigned agent must be changed into agent a. There is no direct notification within Freshdesk. please guys take some minutes to read this topic here. i guess it is important, not only for us. meanhwile i have found many topics from other users, which seems to have the same problems. take a look below to these topics and postings: https://support.freshdesk.com/support/discussions/topics/311631 https://support.freshdesk.com/support/discussions/topics/110 https://support.freshdesk.com/support/discussions/topics/2787 https://support.freshdesk.com/support/discussions/topics/311394 https://support.freshdesk.com/support/discussions/topics/332 https://support.freshdesk.com/support/discussions/topics/307936 and forsure there exist much more postings from other users with the same question. But ofcourse each customer is writing in his own words and you guys from the freshdesk support seem not realize that they all talk about the same problem. Me and and my team we tried a lot of settings and scenarios out. we tested several email notification settings, we also tested several dispatchr rules scenarios.. and also we tested observer scenarios like mentioned by Freshdesk Admin Janani in the topic id#307936 but it does not work ! it fails for some reasons. i would like to write down here the facts again. more clearly: Main target : we want to notify other agents when a comment was added. ( ofcourse this should be done in freshdesk internally. not outside by a thirdparty mailbox or mail software... in easy words: the affected agent must be notified in some way when a private note was added to his or her tickets... and that agent must be also able to see this ticket in his dashboard. Idea: the best solution would be if the ticket comes up with an icon to indicate that a note was added... but even an email notification related to to affected agent would be fine. but it fails in freshdesk ! the problem is: once we use the "notify agents" functionality, an email will be sent out in real. it will also arrive to the email mailbox in external mailserver and mailsoftware like gmail etc... but these emails does not come into freshdesk. At least not in all cases. very often it fails. like you can see in the other topics reported by other users. Maybe it fails because of conflicts on different dispatchr rules. ok. maybe that is the reason. But it doesnt matter. we need a stable and good working solution. and the very best solution would be an internal solution in freshdesk itself. without email notification and without emails forwarding. Example: when an agent ( Agent A ) is adding a private note to a ticket and chooses another agent to be notified ( Agent B ), then this Agent B should see this specific ticket in his dashboard with an icon or any other indication that a comment was added. also when Agent B is adding a private note, and wants to inform Agent A, then that ticket should come up on the dashboard of Agent A again,with an indication that a comment was added. But the key is, this should be possible without changing the assigned agent! @ the whole community and @ the freshdesk support: please share with us your suggestions, your ideas and solutions and your experience. i really hope we can this done. Freshdesk is a great software, lets make it more better for the future. Thanks

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.