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

Josh US COApprentice

Functionality Gap: Business Hours in Alert WorkflowsSubmitted

Currently, the Alert Workflow Module doesn’t have native support for determining “during business hours” like the Ticket Workflow Module does. This is a huge opportunity as creating incidents from an alert and routing them to Ops Teams or Oncall Teams based on alert creation timing is what I would consider basic functionality for Alert Workflows. We can use Web Request and Parser nodes to gather the time value from the alert and what the business hours are in our environment but there is no way that I’ve found to build a condition to compare the values indicated and there isn’t a Boolean value for inside/outside business hours in the current API return values. Is there a known workaround that doesn’t require a 3rd party system to determine this? All the data is already in our Freshservice environment we just don’t appear to have the tools to complete this simple evaluation in the Alert Automator module yet. Again, this is a built-in function for the Ticket Automator. Potential Solutions:Add the Business Hours condition function already available in the Ticket Automator, available in the Alert Automator. Add a Boolean value to the /api/v2/business_hours or /api/v2/ams/alerts endpoints. Add custom expression functionality to the Alert Workflow condition node. Example: {{Alert Creation Time Placeholder}} > 18:00 AND < 07:00 Allow for Alert Workflows to directly call Ticket Workflows Example: Trigger > Create INC > Call Group Specific Ticket Workflow Enable Child Workflows across Automator Modules, then a Child Workflow could be created to evaluate business hours and provide the True/False output which can be fed back into the Alert Workflow.In my opinion, we shouldn’t need to create/provide a 3rd party solution to solve this functionality gap in the Alert Automator.

Lindblom
Apprentice
LindblomApprentice

Cross domain Google Analytics TrackingClosed

With your google analytics app set up, we get analytics data for the customer portal. This is good, but it could be better.The problem with the current solution is that one customers journey is divided in two sessions, even if we give the same analytics property, they show up as two sessions. Due to the customer portal and the website being on different domains.There is a work around for this, documented by google here: https://developers.google.com/analytics/devguides/collection/gtagjs/cross-domainMy proposal is that you allow us to include a query parameter name in the analytics app, and if we include that query parameter when we link to the customer portal, you will take the value from the configured query paramter and send it to GA to use as the client id for the session. This would link the customer portal session to the session the main website, and provide a more seamless analytics experience. Also, this feature would be totally opt in, if you dont add a query parameter or do not provide one, your original functionality is unchanged. The second part to this would be to add a query parameter with the client id when sending traffic back to the main website. I dont know exactly hot to best fit this into your product, maybe a domain filter input on the google analytics app, If the link goes to that domain, include the client id as the parameter already configured. If the end user journey started on the main website, then customer portal and back to main website, it would be client id from the original main website session that came back. If the session was started on the customer journey, it would be the client id from the customer portal that propagates over to the main website, which is fine, they are the same property.

JEM
Contributor
JEMContributor

Allow Account Admins to Manage Team Dashboards Without Group MembershipSubmitted

I am running into a limitation with Team Dashboards that makes centralized administration difficult.I am an Account Admin in Freshservice, and we currently use one workspace. I am responsible for managing dashboards for multiple support teams, but Freshservice only allows me to select an agent group under Dashboard Visibility if I am a full member of that group.For example, I may want to create and manage separate dashboards for:End User Support Desktop Support Applications Other support teams as neededI would like the End User Support group to see the End User Support Dashboard, the Desktop Support group to see the Desktop Support Dashboard, and so on.As the Account Admin, I should be able to create and manage these dashboards without having to become a full member of every group.Freshservice Support confirmed that this is currently expected behavior. They also confirmed that being added as an Observer does not work. The Account Admin must be a full member of the group before that group can be selected for dashboard visibility.This creates an unnecessary issue because I do not need to be an operational member of every support group just to manage their dashboards.Suggested improvement:Allow Account Admins, or users with the appropriate Manage Team Dashboards permission, to:Select any agent group within the workspace when setting dashboard visibility. Create, edit, clone, and manage dashboards for those groups without becoming a full member. Keep normal group membership and ticket assignment rules in place for regular agents.This would allow Account Admins to centrally manage team dashboards without having to join groups they do not actually work in.Please upvote if your Freshservice administrators also manage dashboards for multiple teams.

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.