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

Simon from Pymble
Top Contributor ⭐
Simon from PymbleTop Contributor ⭐

Filtering for Data Sources on Service Catalogue requestsFuture Consideration

There are many use cases for using the data source feature of a drop-down selector field inside a service request. Currently however, they are too permissive/expansive for our data privacy and simplicity needs. For example, I would like a requester to be able to select a colleague/subordinate from the “requester” data source to make the process more accurate and faster for everyone. But, we only have the choice of a filtering by requester group or other ‘hard coded’ attribute like department. This means If I want to restrict staff in HR to only being able to select a colleague, I’d have to make an SR per department and make them department specific. I think we should have the ability to add dynamic filtering that works in the requester’s context. e.g. the below would let us have 1 form for all staff that shows only the relevant colleagues to them. We are also wanting our parents to only being able to select their child when doing an SR. Currently, if we use the requester group = Students…. they can choose (and see the email address) all our 2700 students. This is far too permissive and forces us instead to use a ‘dumb’ version where they have to type in their child’s name or email. Additionally, agents are often not selectable in these requester filters. We are using Freshservice as an ESM and have 110 agents across many different internal teams. It is not just IT staff as agents. We need agents to be selectable in these filters. Filtering is also needed for the data source “Locations”. We should be able to filter in/out locations so that people can only select relevant locations to the SR and not all. And again, filtering is required in the assets data source. We should be able to add a user-context filter that only let’s them select from the assets assigned to them or their department etc. This way they can accurately select items that might need servicing.  

Georg
Apprentice
GeorgApprentice

Enable fulltext ticket search via API (subject, description, conversations, etc.)Under Review

✨ What is the feature?Allow API access to the same fulltext search capabilities available in the Freshdesk UI. Specifically, enable searching tickets by subject, description, and ideally also conversation content, similar to how the internal /api/_/search/tickets endpoint works with { term: "...", context: "spotlight" } - in the UI, this is what appears when you type in the “search” field (magnifier icon, top right). 🔍 Why is it important? This search is available in the UI but not via the public API, which is inconsistent and frustrating for automation. There’s no way to query these fields via /api/v2/search/tickets or filter tickets by custom fields (if the field is too short, e.g., 255 characters). Automating ticket audits, tracking frequent issues, or building support insights becomes impossible unless you manually export everything or reverse-engineer internal endpoints using cookies/sessions. Has been requested before several times,     📦 What we tried Tried using GET /api/v2/search/tickets?query="subject:xyz" → doesn’t work; subject and description are not valid fields. Tried using internal endpoint /api/_/search/tickets (works in browser), but this requires a session token and CSRF token, which makes it unsuitable for stable automation (e.g. in custom apps using API keys). 🧰 Suggested solution Either open up the /_/search/tickets endpoint for API-Key-based use. Or extend the /v2/search/tickets endpoint to support subject, description, and ideally also conversations.

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.