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

Frans De Wet
Apprentice
Frans De WetApprentice

Freshservice Asset Types & FieldsFuture Consideration

I think we can all agree that the management of custom fields in Freshservice is pretty basic and not very well thought through. This has caused much pain and suffering with Asset management.Use Case:We need to keep track of Assets classified as Information Assets for our Cybersecurity Framework to use in reporting, operational workflows and a number of other functions. These assets are potentially of any types: Hardware, Software, Applications, Services, etc. All of these types and categories already exists of course.The logical approach would be to have a field that can be applied to all assets at root level, as any asset could have this classification. Ideally one would expect the Custom Field to indicate that classification should be applied at the top of the Asset hierarchy, so that one can filter on that field first, but of course the Default Fields cannot be edited. I understand why (however, it would have been nice to have a limited number of fixed custom fields one could use at this level for such a purpose) and now one is forced to apply this classification on one of the lower tiers of the Asset Hierarchy.Considering this is needed on many Asset Types (this is a universal indicator: is the Asset Classified as an Information Asset?), it incurs duplicate custom fields all over the place. Furthermore, the query engine cannot filter on custom fields on Tiers and Assets at the Root level (these are not available unless the lower Tier(s) is selected first). Also true for the workflow automator query capabilities, unless you write Readers & Parsers (even then, it remains a nightmare as assets change over time).Things gets more complicated if one considers that we have a large number of Information Asset related custom fields that needs to be added to all assets classified as Information Assets and this must now be done at 2nd Tier level at minimum to trickle down the hierarchy, causing even more duplicate custom fields.What we’ve tried:Adding the required custom fields to each Root level Tier: Works, but one has to write queries on every Root Tier used, including new Root Tiers to get the full view of impacted Assets. This only works in the interactive Inventory filter. Trying to achieve this in automators, analytics queries & automated data exports (which seems to be another nightmare of note) is just impossible. Of course, remember that every Root Tier now has to have duplicate custom fields as well… Creating a new Root Tier called Information Assets and adding all the the types there and simply populating these as lists. Works perfectly, but you end up with a (not) glorified spreadsheet. Not to mention you lose all associations & links, relationships, ownership and automatic changes to the other tracked assets (consider having to duplicate an entry and maintaining changes for every asset that happens to be an Information Asset?)Proposed Solutions:Allow custom fields in Default Fields (even if limited to 10-15 custom fields). Create a secondary Default Fields section for use as root level custom field table reference.I love Freshservice, but sadly, it stays stuck in the “can almost do it perfectly” stage, leaving one to return to good old Excel.I have another bugbear I will write about in a different post, which I have seen maaaany complaints and comments about: The inconsistency of custom field functionality across the product. The ticket module is close to perfect, yet none of the field capabilities/functions are available in the other modules... 

sultanaliApprentice

E-commerce Delivery System Proposal: Reducing Order Returns with Smart NotificationsClosed

The Challenge: The Last-Mile ProblemIn the fast-paced world of e-commerce, the final stage of delivery—known as the "last mile"—is the most critical and often the most problematic. A significant number of orders are returned or delayed because the courier arrives at the customer's doorstep when the customer is not available. This creates a cascade of issues: Increased operational costs: Companies spend more on re-delivery attempts and reverse logistics. Wasted resources: Fuel, time, and labor are lost on failed delivery attempts. Poor customer experience: Frustrated customers are less likely to make repeat purchases. The Solution: Real-Time Shipper Notification SystemThis project proposes a new feature for an e-commerce delivery application that directly addresses this issue. By implementing a real-time notification system, we can alert the shipper the moment the courier rider arrives at their specified address, ensuring the shipper is ready to receive the package.Key Features and Functionality Precise Geolocation Tracking: The app will use the courier rider's device GPS to accurately pinpoint their location as they approach the delivery address. This information will be used to trigger the notification. Automated Notifications: The moment the courier's GPS location matches the delivery address, an automated push notification will be sent to the shipper's mobile device. The notification will include a clear message, such as "Your courier has arrived!" Two-Way Communication: The system will allow for a quick, two-way communication channel. The shipper can instantly confirm their presence with a single tap, while the courier can indicate that they are waiting. This reduces ambiguity and miscommunication. Proof of Arrival: For accountability, the system can log the exact time of arrival and the time the shipper received and acknowledged the notification. This data can be used to resolve disputes and track performance. Benefits of the System Significant Reduction in Order Returns: By ensuring the shipper is available, the system will dramatically lower the rate of failed first-attempt deliveries. Improved Operational Efficiency: Couriers can complete more deliveries per day, and businesses can reduce costs associated with re-delivery and reverse logistics. Enhanced Customer Satisfaction: A smooth and reliable delivery process builds trust and loyalty, encouraging repeat business. Data-Driven Insights: The system will generate valuable data on delivery performance, allowing businesses to identify and address bottlenecks in their last-mile operations.

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.