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

Leadsflex
Apprentice
LeadsflexApprentice

Improving CRM + Automation Insights with GoHighLevel in Service WorkflowsSubmitted

Hi everyone,I’m working with multiple service teams on CRM and workflow automation, and wanted to share some technical insights from my experience with GoHighLevel Automation & CRM that may benefit others here.1. Unified Automation Logic Improves ReliabilityWhen building automations across lead capture, follow-up, pipeline movement, and revenue tracking, keeping your logic inside one platform (rather than splitting it across multiple connectors) significantly reduces failure points. Consistent identifiers (like standardized email and phone fields) help ensure triggers fire reliably.2. Explicit Workflow Transitions MatterIn complex service workflows, implicit transitions often behave differently under high load or after changes. Wherever possible, explicitly define status changes, ownership assignments, and trigger conditions in your automation logic rather than relying on inferred behavior. This makes testing and validation more predictable.3. Validate With Real Data ScenariosTesting with synthetic or “happy path” data seldom reveals edge cases. Build test cases that mirror real user behavior — incomplete records, duplicate submissions, or rapid repeated actions — before deploying automations live.4. Keep Rule Logic Simple Before ScalingHeavy branching logic and conditional rules increase maintenance overhead and risk unknown side effects during platform updates. If a rule doesn’t directly support a clear outcome (e.g., conversion, retention, hand-off), consider deferring it until there’s measurable value.I’ve applied these principles at leadsflex while optimizing automated CRM processes, and it has noticeably improved lead responsiveness and pipeline accuracy. Looking forward to hearing how others are handling similar challenges with Freshworks tools.

eeha0120
Top Contributor ⭐
eeha0120Top Contributor ⭐

Analytics (FreshDesk, FreshService): Ticket Lifecycle - streamlined report according to time eventsPlanned

Hi.Currently, we have a curated report called Ticket Lifecycle.In the Ticket-wise Split widget, for instance, you can have a view of how long (both, in Calendar and in Business hours) a ticket stayed in a status, in a group or assigned to an agent.That is actually pretty good. But it is missing something very important for the ticket lifecycle itself: The timestamp of any of that points changed.I’ll use a real example for elaborating this.This specific ticket has passed several status changes, group changes and agent changes:The correct order of events was:Ticket created with status “Sin Datos” (Without Data). Data was filled, so it changed to status Open. Auto-assignment assigned it a group and an agent (and was kept in status Open). I changed the group and assigned it to myself, and set it to status “En Proceso” (In process). I worked on it and sent a reply to customer asking for further information, setting it on status “Waiting on Customer”. Customer replied back with a response, changing the ticket to status Open. The information of how long a ticket stayed in a status | group | agent combination is perfect, but it is missing the timestamp of such events, making it impossible to view in a streamlined way the lifecycle of this (or any) ticket, as you can’t currently have the proper sorting of those events.That example Report / Data should be shown in this way: That’s the chronological order of the events, as seen on Ticket Activities, If having a timestamp column in such report, we could sort that data as expected. I tried / thought of creating a custom object in order to store that data and then retrieve it from Analytics, but Custom Objects are basically readable-only in Workflows and we cannot write data onto them from Workflows. This is very much needed for auditing. This applies for FreshDesk and FreshService (and I guess all products that uses Analytics).  Hope this gets considered, approved, developed and delivered soon. Elvis.

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.