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

DcurtContributor

Add KB/Solution Article Linking Inside Resolution NotesSubmitted

I think it would be extremely beneficial if agents could link Solution or Knowledge Base articles directly from within the Resolution Notes field. Right now, you have to open a second tab, search for the article manually, and then copy-paste the URL. That works only if you already had the article open. But if you solved the issue from memory, you still should reference the correct article for documentation, and there’s no streamlined way to do that as it stands.Even when you paste the URL into the Resolution Notes, it provides no information at all about the article.For example:https://domain.freshservice.com/a/solutions/articles/17000176771There’s no title, no context, nothing readable. The only workaround is to use “Insert Link” to manually add a name, which takes extra steps and extra time. The Problem• No easy way to tag or reference the KB/Solution used• Makes ticket audits harder• I would assume it makes it impossible for Freddy to understand which documents were relevant• Agents must paste links manually, which is inconsistent• Knowledge sharing is reduced The Proposed Solution: KB/Solution Article LinkingAdd a feature inside or directly below the Resolution Notes field that allows agents to quickly search for and attach relevant documentation. How the Feature Would WorkAgent clicks a “Link KB/Solution Article” option inside or under the Resolution Notes field. A searchable list of Solutions/KB articles appears. Agent selects the relevant article. The article link is auto-inserted into the notes with a clean, readable title, not just a raw URLThis would let agents quickly reference the exact procedure used and improve documentation quality.I feel like this would make the Resolution Notes section a true one-stop shop for everything that happened in the ticket. It would give agents a complete picture in one place, making it much easier for anyone in the future to understand how the issue was handled and what documentation was used.

Joshua.Lawrence
Top Contributor ⭐
Joshua.LawrenceTop Contributor ⭐

Bulk Update ModernisationUnder Review

Current Challenges with Bulk UpdatesLimited ticket selection: Freshservice currently restricts bulk updates to 30 tickets at a time, which slows down large-scale changes. Private Updates: Unable to add private updates to tickets via bulk update tool, which is difficult for admins to manage large numbers of tickets without using a workflow tool. Bulk Updates in Change Requests: Having the ability to bulk update change requests is also only possible via workflow tool but doesn't allow for dynamic questioning or notes. Mandatory fields frustration: Users often need to export, reformat, and re-upload data for fields they don’t intend to modify, leading to inefficiency and errors. Rigid workflows: Existing options (Bulk Action, Scenario Automation, Supervisor Rules, Scheduled Workflows) lack flexibility for dynamic conditions and large datasets.  Modernisation Ideas 1. Dynamic Field HandlingAllow users to skip mandatory fields if they are not being changed. Introduce smart validation that only checks modified fields, reducing unnecessary errors.2. Enhanced UI/UXReplace the current pop-up with a multi-step wizard: Step 1: Select records. Step 2: Choose fields to update. Step 3: Preview changes before applying. Add inline error handling and real-time feedback for formats (e.g., date fields).3. Scheduled & Conditional UpdatesIntroduce conditional bulk updates (e.g., “Update all tickets older than 30 days with status = Pending”). Allow scheduled execution during off-peak hours to minimise impact.4. AI-Assisted UpdatesUse AI to suggest field values based on historical patterns. Implement predictive checks for common errors (e.g., incorrect date formats).5. Improved Asset & Service UpdatesEnable nested field updates and bulk clearing of values without re-uploading CSV files. Support dynamic filtering so only relevant fields appear for selected asset types.

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.