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

raja.pavankumar
Active Contributor
raja.pavankumarActive Contributor

Freshservice - Understanding relationship between custom objects, workflow automations and service cataloguesClosed

As a Freshservice administrator and application owner, one of the major challenges is to build a scalable service management architecture for your teams, especially with enterprise service management and workspaces in Freshservice, administrators will need to understand divide and conquer strategies, system dependencies and integrations with other enterprise applications available in their IT ecosystem.One such challenge is the ability to understand the relationship between your custom object databases, workflow automations, service catalogue items and forms. As businesses evolve, employees sunset their journeys, your operational platform should be upto-date.We recommend our customers to leverage custom objects in the first place for the below advantages.  Remove the need to hard code information in your automations. Minimize duplication of configurations such as duplicating form data in service catalogue forms and ticket fields. Manage configurations via APIs by integrating Freshservice custom object databases. Example: Lets imagine a service management process involving approvals for governance. Automations seize to trigger approvals to the concerned user or delegate approvals to authorized personnel, when they are no longer with your organization. Understanding which custom object databases to update, automation services and service catalogue forms that are leverage these databases need to be identified to ensure changes are in place before service management takes a hit ! Solution:Review automations and export all variables to custom objects. This will help you identify automations that have a static business logic, all variables leveraged in the automation can now be managed using Custom Objects and credentials using the credential store in Freshservice.   Build a CMDB and service management framework to manage the lifecycle of your custom objects. Consider Custom Object tables as databases managed in your asset inventory and Workflows as microservices.   Below is an example of a dependency map documented as a CMDB entry. If a change is needed to be made to a custom object, govern the process via a change request.Now, lets look at an employee offboarding process that is operational in Freshservice and a user that is part of the custom object table leaves the organization the request may not move forward as the approver is no longer with the organization, automations can now be designed to perform custom object validations and notify agents about changes needed to operations in Freshservice. Custom object databases can be managed easily by automatically create a change request in such scenarios and ensure the offboarding processes continue as defined with minimal outages and maximum visibility. The change request can now yield the below results, that will help you identify the related services that are associated to this custom object table.  Automate the process further by defining workflows that update these custom object tables via API and easily manage these routine tasks that are required to manage the sanity of your databases. Hope this helps you manage Freshservice better ! 

David-FlintoffApprentice

Convert Live Conversations into Freshdesk Tickets Using Voice-Based InputSubmitted

Hi Freshworks community,I’d like to suggest an idea focused on improving how support interactions are converted into structured tickets inside Freshdesk.The challengeSupport agents often handle conversations across calls, internal discussions, or quick handoffs. Important details issue summaries, next steps, or follow-ups—are usually typed into Freshdesk after the interaction, which can slow agents down and sometimes lead to incomplete ticket context.The ideaIntroduce voice-based input as an optional layer through integrations with tools like Gennie, allowing agents to speak ticket details naturally and sync them into Freshdesk.Potential use cases include: Converting call conversations into ticket descriptions using voice Adding internal notes or summaries hands-free Creating follow-up tasks or reminders without breaking flow Capturing key customer context immediately after interactions Freshdesk would continue to be the system of record, while voice acts as a faster input method during high-volume or real-time support scenarios.Why this could help Faster ticket creation during busy support hours More accurate and complete ticket context Reduced agent fatigue from repetitive typing Improved response quality and follow-through Would love to hear from other Freshdesk users: Where does ticket creation or updating slow agents down most? Would voice-based input add value to your support workflows?

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.