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

Grace0409Apprentice

Gravity Forms Freshsales Integration Premium Add-onClosed

Seamlessly Connect Gravity Forms with Freshsales CRMIf you're using Gravity Forms and need a streamlined way to manage leads in Freshsales, the Gravity Forms Freshsales Integration Premium Add-on is the ideal solution. This powerful add-on allows you to automatically send form submissions directly to your Freshsales CRM, helping your team respond faster, stay organized, and focus on closing deals.What is the Gravity Forms Freshsales Integration Premium Add-on?This premium add-on enables real-time integration between your Gravity Forms and Freshsales account. With just a few simple configurations, you can map form fields to any Freshsales module, ensuring that your lead data is sent to the right place instantly. Whether you're collecting leads, managing contacts, or tracking new accounts, this add-on keeps your CRM updated without manual entry.Key Features:Multiple Feed Support – Create and manage multiple feeds to send submissions to different Freshsales modules, such as Leads, Contacts, or Accounts.Custom Field Mapping – Map any Gravity Forms field, including custom fields, to your Freshsales fields for precise data capture.Module Flexibility – Choose the target module for each feed based on your CRM workflow needs.Conditional Logic Support – Use Gravity Forms' built-in conditional logic to determine when and how data should be sent to Freshsales.No Coding Required – Easily configure your feeds and field mappings through a simple, intuitive interface—no technical expertise needed.This add-on is perfect for teams looking to simplify their lead capture process and maintain clean, organized data across platforms.To learn more about the Gravity Forms Freshsales Integration Premium Add-on and how it can optimize your CRM workflow, visit the product page.

RobinHenSkilled Expert

Prevent Offboarding Requests from Auto-Closing Upon User DeactivationSubmitted

The Use Case:I have set up an offboarding journey for users leaving our company. This journey includes tasks that need to be completed before the user leaves, as well as tasks that must be executed after their departure date. By default, it makes the most sense to use the native "Requested For" field to identify the user who is leaving.The Problem:Currently, using the "Requested For" field makes post-departure tasks impossible to complete.Imagine John leaves the company on April 30th. His AD account is automatically disabled on May 1st at 00:00. This status syncs to Freshservice, resulting in John’s Freshservice requester profile being deactivated. Because of this deactivation, the system automatically closes his offboarding journey and abruptly cancels all outstanding post-departure tasks.The Workaround:As a workaround, I am currently using a custom text box to capture the leaver's information instead of using the native "Requested For" field. However, this comes with significant disadvantages: it limits native automation capabilities, impacts reporting, and opens the door for manual entry mistakes and confusion among agents. The Ask:It would be highly beneficial to adjust the system logic so that offboarding requests (or tickets tied to the offboarding module) are exempt from auto-closure when the affected user gets deactivated. The journey should remain open until all dependent child tasks are completed. 

EmmCHApprentice

Ability to delete Reporting/Analytics Widgets from the Existing Templates listClosed

As a first time Freshdesk user, I had some issues when using Reports & Analytics for the first time.I realise that the Analytics feature is really designed to be used from within the tool, and be interactive, so you can filter and sort data in any way you would like to from within Freshdesk (slice & dice ‘on the fly’!).However - we need to produce reporting packs for our Execs & Customers who don’t have the ability to go and look at Analytics, so it is necessary for us to create certain bespoke reports (which contain Analytics graphs) and schedule exports out as PDFs from the tool, in the form of ‘reporting packs’.When creating these ‘reporting packs’ I inadvertently created multiple duplicate copies of one of the Analytics Widgets - this is because I cloned it, but nothing appeared to happen, so I tried it multiple times, with the upshot being that I was left with 5 copies of the same Widget, which I could then not delete.To try and get round the issue, I attempted to make each of the Widgets do something different from each other, to give them each a purpose, and then I attempted to ‘rename’ then at the same time. Instead of renaming the EXISTING Widget though, this activity created yet another new Widget, and the previous Cloned Widget still existed. Then I repeated the operation several times, including as part of testing conducted on a call with Freshworks, to demonstrate the issue I was having. This ultimately resulted in me having essentially 15 copies of (more or less) the same Widget, which is clogging up my ‘Existing Templates’ list, and slowing down performance - on one occasion it took 15 minutes to load the list up.Also on the call with Freshworks I asked if their Admins (once granted a Day Pass to access our instance) could delete the unwanted Widgets on my behalf (since there was not an option for me to do this, despite being Account Admin), however I was told that this was not possible and to raise an Ideal.Therefore - this is the Idea that I am raising - which essentially is to ask for the ability to delete unwanted Widgets (I will refrain from creating any more new ones too, now that I know that feature is broken too).Many thanks,Emm

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.