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

jcapitan-shoreline
Skilled Expert
jcapitan-shorelineSkilled Expert

Attaching Existing Assets to Purchase OrdersFuture Consideration

The current process for associating existing inventory assets with Purchase Orders (POs) in Freshservice is a significant pain point. We need the flexibility to add assets already in our inventory to an existing PO, rather than being forced to create them from scratch within the PO or resort to cumbersome workarounds.There are two primary scenarios where this limitation becomes particularly problematic: Expedited Asset Entry: Sometimes, we need to get assets into the system quickly. Using the bulk upload option directly within the inventory module is far more efficient than individually adding assets to a PO. However, if these assets are meant to be part of a PO, there's no streamlined way to link them later. Addressing Oversight and Duplication: It's not uncommon for users to forget an active PO exists. They might create, assign, and meticulously log all relevant information for an asset directly in the inventory. Currently, the only way to link this asset to its corresponding PO is to delete the existing asset, losing all its valuable associations and meticulously re-entering the data within the PO. This is a time-consuming and frustrating exercise that leads to data loss and inefficiencies. Allowing users to simply attach or associate an existing inventory asset to an active PO would save considerable time, prevent data duplication, and maintain the integrity of asset records and their associations.

michaelrContributor

Force agents to comment when closing ticket + Mail-submit as a different userClosed

I have two requests / questions - these might already be possible, but if not would sure be a nice addition. 1. Is there a way to force agents to fill in a comment when closing a ticket? Currently some of our agents are replying with final details on how they solved the issue, and then close the ticket, so the user gets two emails at the same time.. I would cancel e-mail notifications for closed tickets, but other agents might not respond at all when closing a ticket, trusting the ticket-closed-notification to let the user know the problem has been solved.I'm trying to minimise the amount of e-mail notifications the users get, so I would like to be able to either force agents to send a comment before closing a ticket (so I can cancel the closed-notification for users) or send a comment and close the ticket at the same time, so that the user will only get one mail notification.2. Is it possible to mail-submit a ticket as a different user? or alternatively, is there a way for the requester of forwarded-mails to be the original sender and not the person who did the forwarding? We are constantly getting user-requests to our personal or work mails, and when forwarding them to the help-desk, the requester listed for the ticket is the agent who did the forwarding and not the user who originally made the request. Any info on how I can do either of these, or if they are in the future road-map for Freshservice, would be very much appreciated. Thanks, Michael

TomKApprentice

Improve New CSAT response view and dashboard accessSubmitted

We have recently moved to the New CSAT framework in Freshdesk. While the Advanced CSAT report provides the main CSAT metrics, the experience for reviewing individual customer comments and response-level feedback is now less practical than it was in the older CSAT report.At the moment, customer comments can be accessed through the Underlying Data option. This does work, and it allows additional fields such as Ticket ID, requester details, agent, group, and survey name to be added. However, this process is more cumbersome and less intuitive than the previous CSAT response view.The previous CSAT response view was more visual, interactive, and easier to use. It was much better for quickly reviewing customer comments, presenting feedback internally, identifying trends, and following up on specific service improvement opportunities.The current New CSAT response-level view is mainly presented as a standard table, which makes it less effective for quick review and presentation purposes. I also cannot see a straightforward way to add this response-level comments view directly to a dashboard for quick access and visibility.Requested improvement:Please consider adding a dedicated response-level view for New CSAT, similar to the older CSAT response view, with the ability to:View individual customer comments in a clear, visual, and interactive format See associated details such as Ticket ID, agent, group, requester, company, survey name, and response date Add the response-level view or a useful summary widget directly to a dashboard Export the response-level data, including customer comments Make customer comments easier and faster to access from the Advanced CSAT reportFrom a user perspective, the old CSAT response view was significantly better for day-to-day service review work. The New CSAT reporting framework provides the metrics, but the comments and response-level review experience feels weaker and less accessible.I believe this would be a valuable improvement for many Freshdesk customers, especially those who use CSAT comments for service reviews, presentations, customer follow-up, and continuous improvement activity.

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.