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.
My org is approaching over 100 separate automations that are running on tickets alone. Recently, we had an outage which made us realize that there was no ability to easily see blast radius. While thinking through this, I think the below would be huge when it comes to automator administrative items.Similar to the ticket list view, the ability to filter automators based on things like: App integration used Credential(s) used Last updated date Trigger event(s) Ability to add tags to workflows In lieu of point 1, it would likely be lower effort to allow tags on workflows to be able to search/filter based on those Ex: If it uses a web request, a tag of WebRequest can be added. If it uses Intune it’s tagged as that, etc. Ability to Categorize workflows This can kind of happen with Workspaces as I understand it (we are not using them) but it would be nice to set a category similar to a ticket as this would help reduce noise when troubleshooting (what things run on everything, etc). Ex: Global, Business unit specific, Service Request Specific, Incident Specific, etc.
Hello,It would be great if the quantity could be subdivided.If you have products calculated in meters for instance you can’t insert 12.4m.The same is for kilograms and other similar units.Thank you
Hi folks! been thinking about the MS Teams Collaborate tool, and a few of the issues we have with it and the ServiceBot. Mainly, that many of our Agents feel it is to ‘chatty’! The ongoing thread seems to be that some (not all) Agents are happy to use the email alerts to be updated about ticket changes. Indeed, they can put email rules in place to personalize their mailbox, customizing it to fit their individual needs.Sadly, the MS Teams ServiceBot is not so flexible. The options are Global, and dictated by myself and the other Admins. Ideally, I'd love for individual users to be able to choose what MS Teams notifications they get. Allow our helpdesk, with high ticket volumes, to only get notifications when Collaborate is initiated, and our Major Incident team to get all the alerts whenever something happens on a ticket in that group. Anyone else hit similar issues? Maybe found a nice easy solution I’ve overlooked?
I spent about 10 minutes today typing out a change request, only to get to the end and click on cancel instead of Submit so I lost all data.It would be great from a UX perspective where if specific fields are updated (or any) before form submission, you get an “are you sure” prompt when cancel is clicked before the person loses all of their data entered accidentall.Same logic should also apply to the incident and asset pages.This page (as in the community) has a prompt like this (on navigation away from the page) on it
Not being able to sort Knowledge Base articles by name, date, or manually makes it very hard to create an optimal experience for the public using our various KB articles. This is basic functionality. Only being able to move articles from one folder to another isn’t very helpful. Please add sorting for KB that lets users Drag and drop KB articles to sort them manually Sort KB articles alphabetically (A-Z, Z-A) Sort KB articles by Create Date Sort KB articles by Last Edited Date
CloudBik’s Teams to Teams Migration tool simplifies the process of moving data between Microsoft Teams tenants. It handles the transfer of channels, chats, files, and permissions with precision, ensuring no data is lost during complex migrations like those driven by mergers or tenant consolidations. This solution minimizes disruptions, allowing teams to maintain their collaborative momentum.For SharePoint Online transitions, CloudBik’s SharePoint Migration Tool automates the migration of content, metadata, and site configurations from on-premises or cloud-based systems. With features like error detection and incremental migration, it ensures a smooth and compliant process. CloudBik’s tools enable businesses to embrace Microsoft 365’s full potential with confidence and efficiency.
Possibility to let users sign documents when generating them from withing FreshService.It would be great an user can request an asset, we provide the asset and assign it to them, generate the relevant agreement and let users sign this, all from within Fresh.Currently we have to generate→ print→ sign→ scan→ add attachment or generate→ open in 3rd party app → sign → upload
We use the FreshService on-call system, which is fantastic. A team member recently brought up an idea where he would like to know if he’s the primary on-call, secondary on-call or tertiary on-call. He’d like to get this information in his e-mail reminder. Unfortunately, there’s no placeholder for which position he holds in the on-call schedule.It would be great to add a placeholder so I could put in the e-mail if he is the primary person who is on-call, secondary, or tertiary.Available Placeholders for On-Call Notification E-mailsOn-Call Shift Positions
Hi, would be great if the API allowed to update the profile/avatar picture for requesters. Would make it easier to know who is requesting a ticket. This is available in the Freshdesk’s API. It would also be great if the photos was shown in the mobile app.
When creating a build kit, I am creating it based off of an employee’s position. The build kit conditions will do this no problem. The issue is when the same position has different requirements based on other factors, such as location. If you have 2 techs in 2 different locations, they should get the same items, but due to regulations of one of the locations, now they are required to have more items. It would be nice to have the ability to create conditions with multiple requirements, ie: Position includes Tech and location is area1. Right now you would put Position includes Tech, Location is area1. Thus getting all tech’s and all in area1, not the overlap.
Currently only agents with ‘Play God with Super Admin Controls’ have the ability to update Ticket Fields and Ticket Forms, It should be possible to manage the ‘Ticket Fields and Ticket Forms’ if Perform Operational Admin actions’ is enabled.Providing an agent with the ‘Play God with Super Admin Controls’ provides the agent with the ability to change the Portal settings which could result in providing content to users that are not authorised.
Hi Freshworks Team,I'd like to suggest an improvement regarding the German wording used in some parts of the UI, particularly in employee-related forms.For example, the current phrase "Einen Mitarbeiter einführen" is not gender-inclusive. In German, this literally refers to introducing a male employee, excluding other gender identities. A more inclusive version would be something like:"Anfrage zum Onboarding eines:einer neuen Mitarbeiter:in"or"Neue:n Mitarbeiter:in einführen", depending on the context.We understand that Freshworks is an English-speaking company, but many of your users work in countries like Switzerland, Germany, or Austria, where gendered language plays a significant role. It's not only a matter of inclusivity but often also a legal or cultural requirement.We’d really appreciate if you could: Update German UI texts to use gender-inclusive or gender-neutral phrasing Consider using standard formats like the colon (:) or asterisk (*) which are commonly used in German for inclusivity Potentially allow language preferences that include gender formatting options Thank you for the great work you're doing – and for considering feedback like this to make the product better for everyone.Best regards,Joel ZiswilerStiftung SAG
Currently workflow automations are possible fortickets problems changes releases tasks assetsPlease add also Agents and Requesters (all Users) to be able to trigger automations such ason change from active to disabled on update from sync on creation of new agent/requesterthis would make possible a lot of new useful workflows.
Currently to add a webhook to an automation or install an app on freshdesk it requires an agent API key to be added. This is a poor implementation as if that agent ever leaves the company then this API key becomes unavailable and things can stop working and probably won’t be obvious straight away as to the issue. There should be an account level API key that can be used instead.
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.
