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

UniSC Systems
Apprentice
UniSC SystemsApprentice

Bring Contract customization to parity with Assets (columns, fields, layout, reporting)Submitted

Contracts and Assets appear to run on the same module, yet Contract customization is noticeably shallower. We can create custom Contract Types and add custom fields, but the tooling around those fields hasn't kept pace with Assets.Key gaps:Fixed list view columns. The Contracts list won't let us add, remove, or reorder columns, and custom fields can't be surfaced as columns at all. Asset views already do this. No filtering/sorting on custom fields. Because those fields can't reach the list view, we can't filter, sort, or build saved views on them, all standard on Assets. Basic field types. Contract dropdowns can't pull from data sources, so we maintain static values by hand. The Asset/ticket field types (incl. data-source dropdowns) should apply here too. Flat form layout. Asset Types support tiers and grouped sections; Contract forms are flat and get unwieldy fast. Weaker reporting/automation. Contract custom fields aren't readily available in reports or workflows the way Asset fields are.The ask: bring Contracts to parity with Assets, customizable columns (including custom fields), filtering/sorting/saved views, richer field types with data-source support, sectioned layouts, and full reporting + automation. Since it's the same module, this should extend existing functionality rather than build something new. Right now we either can't capture contract detail usably, or capture it and then can't view, filter, report, or automate against it — which pushes us back to spreadsheets.

ASHill
Contributor
ASHillContributor

The ability to see Restricted Group Ticket Properties and/or Report on Restricted TicketsSubmitted

The ability to see Restricted Group Ticket Properties and/or Report on Restricted Tickets In our org, we have several restricted groups due to the sensitive data within specific tickets. These tickets become hidden entirely, where even sys admins cannot see that the tickets themselves exist, and if our Help Desk tries to assist a customer with a ticket assigned to a Restricted Group - they also cannot see that the ticket even exists. What we need for restricted tickets: The ability to see that the ticket exists with a ticket ID and a Group Assignment. Right now, if an agent searches for a Restricted ticket, they get 0 search results. If they try to click a link to go directly to the ticket, they are presented with an error that says they are not allowed to access the page. Agents at the very least, should be able to see that the ticket exists and which group it is assigned to. They do not need to see Ticket Details. This could be resolved with Role specific access, that only agents with "X Role" are able to see Restricted Group Ticket Properties. This role would apply to our Level 1 agents that assist callers with tickets across our entire org. The ability to report on restricted tickets. We do not need to see the data within these tickets, but at a basic level need to see:The ticket IDDate CreatedDate Resolved/ClosedGroup Assigned We need to be able to accurately report on the number of tickets we have at a high level. 

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.