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.
We would like the ability to tag assets to be able to create lists of assets with different roles. we are currently doing this with custom fields but this limits the asset to 1 role. Tags would allow an asset to be tagged with multiple roles.
I have custom ticket field that I'd like to get reset every new day.Basically there can be tickets that are waiting development and I check them every day to see if anything has come up. When I've checked them I set a status field to something "checked". Now, I'd like that field to get reset at midnight every day so I can re-check the tickets every day.Is it possible to have such an automation?Everyday at x hour -> set field to blank
You have some many nice and useful features in Freshdesk which can really help customers in Freshservice as well like:- Enhanced Bot- Forums- Field Service Management- Omniroute- Proactive outreachDo you have any plans to shift such features to Freshservice?
Curious if there's been any thought/discussion around restricting or silo'ing visibility of Tags to specific Groups in Freshservice?Currently, when using the Filter section within the ticket list view (or within a ticket itself) you can see every tag available on the portal. Ideally, we would love to be able to scope certain tags to Agent groups so that when the list populates our Agent groups will only see the tags relevant to them. We would still want the ability to apply GLOBAL tags when needed, but this would greatly reduce the amount of scrolling our Agent groups have to do/the number of tags they have to remember by maintaining a lengthy legend elsewhere.
When creating a dropdown field for tickets and adding items to it, there doesn't seem to be any option to automatically order the items (alphabetically).This is very necessary and can save a lot of manual work when a dropdown field contains many items.I hope this will be added as a feature soon.Thanks!
we need to filter the trigger initiator with exclusion, not inclusion"this action can trigger NOT by" insteat of "this action can trigger by"see more in the attachment.
We have problems to use the asset feature. WE have no local AD and using AzureAD for Device Management and we can't get the mapping between user and device so it is not very useful tho have not the relationship between device and user. The agent doesn't deliver this and also the Intune App doesn't use this field.
is it posible to set default values for ticket fields?For example default group, default supporter.Also default date set as today.
Looking for more automation between Freshdesk and Freshrelease.We'd like to add a private note (status update) to tickets in Freshdesk when the associated user story in Freshrelease has been assigned to a release that has been released.Is there any sort of way currently to automate these steps or any plans to do so in the future?
I would like to have different Fields on the ticket template based on the Group.This should work like the dependent fields functionality, but with the parent field being Group.My case here is, I have two groups and they only have access to tickets on their own group. I have a custom dropdown field named "Category" for categorizing the tickets on both Groups, but the items in these dropdown Menus should be different for each group. e.g Group A should only create tickets on categories 1,2 and 3 and group B should only create tickets on categories 4, 5 and 6.Dependent fields don't work on this case because each group would be able to create tickets for categories of the other group, just by choosing the wrong parent category.
In the Ticket Creation on a Customer Portal, the Custom Text Fields which were added, do not have any whatsoever Text Formatting Tools.Is there a Plug in or is there a possibility for us to develop a custom plugin ? Does the Freshdesk interface allow that ?
we often need to add a public or private note, instead of a public reply
Within a service request all fields (including custom fields) are locked after the first approval is requested. We use custom fields for the assignment to a cost center and product group. In some cases users request items for different cost centers, so we cannot use a user related field.If the information entered is wrong and the manager receives an approval request he has no possibility to change it. Adding comments makes it confusing when using reports, because the custom field still has the wrong information.There should be a way that custom fields in service items can be changed afterwards. Could be solved by one of the following settings:- additional option when creating the custom fields.- special permission role that allows agents to change custom fields even if an approval has been requested or approved.- option on action "request approval" in workflow automator: "do not lock custom fields".
At the moment epics appear under the month they are due to finish. We are keen to see when epics start and finish on the roadmap so people can visually see the amount the team is working on and where there are overlaps
At the moment we can only view epics on the roadmap. If separate user stories are being fulfilled over different sprints and an extended period of time, it would be good to be able to view these on a roadmap
It would be great if we could use placeholders within Solution articles. We have a product that is branded differently for different markets. Customers overseas will log in to their own portal branded up, but i want to avoid duplicating all of the solution articles and simply replacing the product name.
It will be good have the option to sort the test case header as shown below:
As you did with Jira, it would be great if you could provide integration with Microsoft Team Foundation Server.
I would like to be able to save the sort order as part of a view. My agents have a customer view that shows the tickets they should be working on (called 'My Work'), and they are supposed to sort them in ascending order by due date and then pick the one off the top of the list.The problem is they keep forgetting to sort the list if they have been using a different view so I would like to be able to set the 'My Work' view to always sort the tickets in the order that they should be working on them.
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.
