Find, vote on and share ideas for Freshworks products. Here is how it works and what happens next.
Every idea has a status. It shows where the idea is today.
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.
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.
Six questions most people ask before they post.
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.
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.
You get an email when the status of your idea changes. To follow an idea you did not post, subscribe to it.
An idea can be closed for one of these reasons:
Closed ideas stay searchable, so you can still read the comments.
The quickest way to make an impact is to back an idea that already exists.
Open the idea and select the vote button. Voting shows us which ideas matter to you. You need to be signed in to vote.
Open the idea and add your comment. The most useful comments say:
"I agree" helps less than a short example from your own work.
Select Subscribe on the idea. You get an email when the status changes or when someone replies.
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.
Freshdesk’s current Round Robin ticket distribution often results in uneven and inaccurate assignment, which creates workload imbalance across agents and adds unnecessary management overhead.In real-world usage, agents frequently end up with dramatically different ticket counts (for example: Agent A = 5 tickets, Agent B = 1 ticket, Agent C = 0 tickets), even when all agents are actively in the queue. This occurs despite automation rules and consistent queue usage.Proposed ImprovementsRound Robin distribution should account for true agent workload and participation, not just queue order. Specifically, it should track: Agents currently in the queue Number of tickets assigned to each agent per day Exclude tickets that were deleted or merged (these should not count toward distribution) Optional consideration of total active/open tickets per agent (load-based distribution) Reset daily distribution counts at midnight This would ensure assignments are fair, predictable, and aligned with actual work performed.Common Scenarios That Break Distribution Today From day-to-day support operations, these situations consistently disrupt Round Robin accuracy from my testing. Auto-generated email tickets Some systems send unavoidable automated emails (delivery failures, out-of-office replies, etc.). Even when these tickets are immediately auto-deleted via automation, they still appear to affect Round Robin distribution. After-hours ticket intake Tickets received overnight are assigned automatically to agents who remain in the queue. This is intentional to prevent missed assignments, but it skews distribution the following day since those tickets already counted toward Round Robin. Ticket merges When a new ticket is merged into an existing one (for example, when a customer replies incorrectly, creating a new ticket), the merged ticket still appears to count toward assignment totals, even though no new work was created. Queue re-entry behavior When agents leave the queue for lunch and rejoin, they appear to be placed at the “top” of the rotation, receiving the next ticket regardless of how many tickets they’ve already handled that day. Tracking daily assignment counts per agent would make Round Robin significantly more transparent and fair in these scenarios.Bonus / Advanced Options (Optional but Powerful) Load-aware distribution Prefer agents with fewer open tickets when assigning new ones. Resolution-time awareness Very short-lived tickets (e.g., opened and closed within 30–60 seconds) should optionally not count toward Round Robin distribution totals, as they don’t represent meaningful workload. Expected Benefits Fairer ticket distribution across agents Less manual intervention by managers Improved morale and perceived fairness More accurate reporting and workload balancing Better alignment with real-world support workflows
The ability to administer roll assignments for agents directly from the role editing screen would be a good convention to make managing role assignments more streamlined and consistent.When every agent has to be individually assigned roles, this invites inconsistency and misconfiguration, leading overall to more risk. Role/Permissions management should allow standardized assignment. The system would benefit from a way to assign roles in a standardized way
On an IT team, it is often helpful for members of the team to have the ability to see on-call calendars even for groups they are not a member of. Suggest adding a permission which will allow viewing of all (or some, if possible) on-call calendars even if not a member of the assigned group.
Location management in Freshservice is still a major problem for administrators and customers. While it improved with the ability to use Locations as a Data Source field in tickets and service requests, there’s a lot of work that still needs to be done to make it not agonizing to use in practice.You cannot report on Locations in Analytics, because you can’t report on a data source field. You can report on Requester location, but not on Location itself. There’s no practical provision to close a location. If you close a location, you have two primary options: remove the location from the location list—which removes the Location field information for any Incident or SR ticket that was ever assigned there, and rendering the prospect of reporting on ticket history by Location useless; or hide the location from requesters and agents—which requires one Business Rule for Forms for the Incident form, and one ticket for each and every SR that uses Location as a field. SR BRFs cannot be cloned, so each of those rules must be created and maintained by hand. I’ve done it, and It’s a nightmare! There’s also no documented method to move a location. Say a company uses areas and regions to organize stores within a country instead of (or in addition to) states/provinces. How do you move a location from one area or region to another? If you import a new set of Locations via CSV, does it look for existing locations by name and update the existing set like it does for requesters, or will it just overwrite the current information and disassociate your existing tickets? The KB article has no information on this process. I did just discover that you can move a location by changing the Parent Location field and updating it, but this isn’t documented as far as I can tell, and it should be. Furthermore, if a company is reorganizing its locations en masse, handling this one-by-one by hand will be another nightmare: it doesn’t scale well at all.Feature requests to correct these issues:Allow reporting on data source fields, including Locations. Provide a toggle switch (or some similar function) to hide any specific location from new forms of all types, but still allow it to be visible and reportable in Analytics. Let us just… turn Locations on and off! In one place! Alternatively, provide the option to make a Location-related BRF that can be applied to all SRs. This isn’t as good as a toggle switch because we’re still then responsible for hiding locations across multiple BRFs, but it’s better than what we have now. Provide a useful, non-destructive, and documented method to batch-update existing Locations.Thank you for making such a useful product; implementing these ideas will make an overlooked-yet-critical feature vastly more useful and flexible. I appreciate your time and attention! 😊
We are just starting to use FreshService to gather alerts from several disparate applications - However, I noticed during my normal utilization that there is no way to search an alert using the bar at the top of the FreshService page. Normally, when you put a search term in there and hit enter, you are met with a second screen where you can use the bubbles to filter by the specific type of item you are attempting to filter - however, Alerts aren’t in that list.Ideally, we should have a bubble for Alerts, that would allow us to search them using the search term we have provided.Additionally, I feel like the Message and Additional Info fields should be indexed and searchable - but it appears that they are not. Making these changes will make the Alerts page a much better product that can be used in production environments.
I’m really interested in how Freshdesk integrations can streamline customer interactions and improve overall service quality. For example, many businesses like car rental and transport services rely on fast response times and clear communication to keep their customers happy. I’ve seen companies improve workflows by connecting Freshdesk with their booking systems, which makes the whole process smoother for both staff and clients.One great example is in the car hire industry—platforms like Purple Diamond Cars focus on reliability and customer satisfaction, and integrations like these can make customer support even more seamless.What integrations have you found most helpful in improving customer engagement?
The ability to query knowledge base articles using Freddy AI insights would be very helpful. Examples of queries:Articles which have not been updated since creation grouped by year Total articles by author Total solution views in the last X, grouped by category
To improve the usability and efficiency of our knowledge base, I propose adding advanced filtering options that allow users to filter articles based on at least the following criteria: Status: Users should be able to filter articles by their status (e.g., Draft, Published). This will help users quickly find the most relevant and up-to-date information. Author: Allowing users to filter articles by author will enable them to find content created by specific individuals, which can be particularly useful for locating expert opinions or following contributions from key team members. Benefits:Improved Search Efficiency: Users can quickly narrow down search results, saving time and increasing productivity. Enhanced User Experience: Providing more granular filtering options will make the knowledge base more user-friendly and intuitive. Better Content Management: Authors and administrators can more easily manage and track the status of their articles.
There should be an field to select the existing group as an owner or reviewer of the Knowledge base.This will help the Knowledge Manager to reach out to group of people, when it’s time to review the article, instead of just 1 owner,
When we create a note and want to upload an image to it, the “Add Note” button does not get blocked. This causes the image to be removed if we click the button before the upload is completed. My suggestion is either to disable the “Add Note” button until the image finishes uploading, or to queue the actions in Fresh so that images upload first and only then the system adds the note.
From a troubleshooting perspective, similar to the Workflow automator execution logs, it would be nice to have some sort of supervisor rule execution log that shows all tickets a supervisor was run on. This would allow us to see if things are triggering more/as/less often than desired for a specific rule more proactively after implementation into production rather than having to wait for a user to complain about something not happening when desired OR something happens every hour (and being able to isolate if it is a specific ticket issue, or a global config issue).
Creating a Calendly feature, so I can send a public link for people to book meetings with me
When writing articles in the Solutions or knowledge base section of FreshService, it can be a dangerous game there is no auto save. Not sure why in 2025 there is no autosave but it sure does suck when you spend an hour working on something and lose it. You can’t even write it in a Google Doc and copy and paste because it loses the formatting. An auto-save feature should be top of the list, but the entire screen could use some modernization and formatting features.
I would like to request a feature that allow us to mandate certain field in Asset module when asset state is set to certain value. It caused incomplete data record and improper asset tracking. Due to our business operation, we have more than 10 site office. Thus, i need every asset assigned with a site office detail when asset is set to “In Use”Currently the Asset module doesn’t provide any way to enforce required fields. Unlike the ticket, change or service item that we can configure through business rule. This creates issues where assets move from one state to another, but important fields are left blank because there’s no validation.For example, when an asset moves to “In Use,” we may want to require “Assigned To,” “Location,” or other key fields — but we can’t enforce this today.Adding conditional mandatory fields would help: Improve data accuracy and completeness Ensure proper asset tracking throughout the lifecycle Reduce manual follow-up and errors This would be extremely useful for us who rely heavily on asset data to ensure accurate tracking.
I am reviving another idea from the past as it has not been implemented:Please allow us to duplicate solution articles and folders with one simple button. Same as it is possible with workflows/service items and so on.Currently we need to create a new article and copy past all the contents - no good uxThis is a must have feature. Thankstag: @afautley @Daniel Söderlund idea from:
The current implementation of the requester widget and flyout needs to be expanded to be able to customize the fields shown both in the pinned (in widget), and in the flyout state. The current stance doesnt allow for important fields to be shown. In addition, it seems odd that Freshworks has created multiple renditions of apps that provide overlapping functionality for some of this, but they are all separate apps. If the feature was advanced and expanded, it would likely remove the need for an additional 2-4 apps!
Loading your ideas...
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.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
