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.
In order to include ticket property detail information as part of the Freddy Summary section, I had to create a canned response to pull the data from the ticket details. This was a decent work around for the situation I needed it for however, when adding the canned response, the shortcut option of /c is not allowed in the Freddy AI summary portion. The only way to add the canned response was to click on the canned response icon and select the response from the drop down list. This is not as efficient as the shortcut. Here are my requests:Allow the short cut option for canned responses to be used in the Freddy IA Summary portion Allow data to be added to the summary from Ticket details just like what is available in canner responses.
With a multi-tenant account, currently Teams integration for service bot is only available on the main tenant account. I cannot use it on my tenant. Most of the work I do in Freshservice is on the tenant I manage, not the parent tenant. I would like to be able to integrate Teams and the service bot with the tenant I manage.
It would be nice to have an option to remove “Customer Responded” flag from certain tickets. Current workaround of sending a message or leaving a public note (which logged in customers can see) just to clear the flag is not something that suits my needs. I want to have an option just to remove the flag, without any other additional steps.
I see that there are a lot of translation add-ins for Freshdesk. Is it possible to make these available for Freshservice? We work in a multi-lingual environment and it would be great if the actual ticket content can be translated on the spot.
Our Support Team introduced a Chat Team semi-recently, and we have been utilizing FreshDesk Reports to track our metrics. We’ve created separate reports for Chat and Tickets, and would like to merge these reports together to keep all of our Support Metrics in one place. We are unable to merge created FreskDesk reports together to create a full Support Team dashboard. I would love to see the ability to combine or merge FreshDesk reports, to minimize manual work when introducing new product metrics to track.
Please add the ability to trigger webhooks in hourly trigger automations. This is a basic action that’s possible in both ticket creation and ticket update automations, therefore it should be possible in hourly trigger automations as well. For context, our sales team wants to send satisfaction surveys to our high value customers once per month rather then once for every ticket, as most of these customers make several tickets per week. To do this, we are relying on a contact field that indicates whether or not the customer has been sent a survey that month. In Freshdesk there is unfortunately no way to give an hourly trigger automation a ‘trigger webhook’ action. We luckily have access to Freshsales as well, where time-based workflows with webhooks are possible, so we were able to use this as a workaround (after making a different webhook that sent Freshdesk Contact IDs into the contact’s field in Freshsales). However, it would’ve been much easier if the functionality were already possible through Freshdesk, and many users do not have access to Freshsales and wouldn’t be able to set something like this up.
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...
When viewing a full list of tickets (whether all or for a specific assignment group) it would be handy to see what asset has been assigned to a ticket. Currently I see now option to add a column for Associated Asset Would assist with ticket triage and trend analysis. Also potentially a future Freddy AI to suggest an asset replacement if constantly reported on.
Many a time, our agents need to create a Knowledge Base Solution Article based on the Resolution of a ticket (incident or service request). I understand that ticket Resolutions do not contribute to the search results of the Support Portal. It would be helpful to have an option to convert a ticket Resolution into a KB article whilst creating a link between the two, reducing the double-handling required by the agents. I believe this would also help in error message / ticket / solution correlation, including the Freddy AI side of things.
I have downloaded the export of daily ticket activities, which has been helpful to see agent productivity. However, it doesn’t tell the whole story, since idle time could be explained by an empty queue (i.e., no tickets in “Open” status). It would be great if there was something in Analytics that would automatically ping a certain queue/view for unassigned tickets and compare this against agent activity. For example, we have a goal of monitoring the queue for unassigned tickets every 20 minutes. Analytics could run a check to see if any unassigned tickets were created > 20 minutes ago AND if there was no agent activity during that time. It could show as a productivity violation in a chart or, it would even be ideal to set up an email notification for this. I’m hoping this would solve the problem of agents spending too much time on breaks when we’re drowning in tickets.
Tickets shared with me do not appear in the agent or support portal search results (unless the ticket is assigned to one of my agent groups). Freshworks support have confirmed that this is the case. The only way to access a shared ticket is either via a direct link or on the “Shared with Me” ticket list views (requester on Support portal or agent on Agent portal). In many instances, this creates the illusion that a ticket is not accessible by the agent/requester. I suggest that these are included in the general search results.
The Agent Group Manager should have ability to build preventative maintenance tickets/tasks (Scheduler-Automation-Productivity). These tasks should have flexibility to be weekly, biweekly, monthly, semiannually, and annually. These tasks should be able to be assigned to specific Agent Group members in that group.
When viewing a large list of tickets, it would be useful to sort the tickets by ‘Stage’ based on the stage order I set on the ticket fields, rather than just alphabetically. The sorting order could be something that is configured on the field editor. For example, at the moment, closed tickets are sorted nearer the top before any pending status. Since “Open” is the first status type, I cannot put this first in an alphabetical list view (the field value ‘open’ cannot be renamed either).It would be nice if the defined sort order was an option for viewing the list view of tickets:Thank you,Richard
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.
