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.
The current bulk update process in Freshservice, particularly concerning required fields, is a significant source of frustration and inefficiency. Users should not be forced to engage with data they don't intend to modify, especially when it leads to a time-consuming and error-prone experience.Consider this common scenario: I needed to update a set of assets. The process required me to have two tabs open simultaneously – one to identify the mandatory fields and another for the export settings. I had to constantly switch between them, meticulously checking off all the required fields for export, even if they already contained the correct data.After a painstaking export and extensive data manipulation, I attempted to upload the updated assets, only for the upload to fail because I had missed a required field. This meant repeating the entire export process, this time including the newly identified field.The frustration didn't end there. Upon the second upload attempt, the process failed again due to an incorrect date format in a field I never even intended to modify. This forced me to reformat an entire column of data, further extending a task that should have been straightforward.This convoluted process significantly hinders productivity. We should be able to perform bulk updates without being coerced into exporting, reformatting, or re-uploading data for fields that are either already accurate or irrelevant to our intended changes.
Linking POs to assets is cumbersome and time consuming currently. It would be nice to add the purchase order field to the csv. file when importing assets that links back to the previously entered PO to tie everything together in a fast and efficient manor.
On the display field, can you have the option to display Groups? Right now, we can only show:Status Ticket assigned to Requester Priority
Hi there,This has been a nice to have since 2 years ago. 😁Please see these two pages:
We want the FreshService Support Portal to be the one-stop shop for all end-user requests. However, in some scenarios we have other tools which handle these requests such as the Microsoft Entra Self-Service Password Reset Portal, SharePoint forms, etc. There doesn’t appear to be an easy way to create a Service Item which would redirect to another site. Having this feature would allow us to put all potential requests in one place, but still allow end-users to access the forms wherever they may reside.
Currently you may associate one asset at a time.Whenever you select “Full fill request” you may select one asset and associate it with the ticket. Afterwards you will have to go to the associated asset and select the next asset and so on if there are more.We would like to have the ability to add all assets that need to be associated to the ticket in one go. Is that a possibility?
Hi There, I’m working on use-case where I want to create task on run-time & assign to group based on some selection on SI form. I though of using Custom Object to built the mapping table (e.g. Plant location vs. Agent groups) but then I don’t see task module has any reference to Custom object in-order to assign group dynamically. If you guys can extend CO capabilities for Task as well it would be very helpful.
Currently you cannot link a solution to an Incident, but only a problem. Freshservice should be able to link Solutions to Incidents to keep a record of solutions being used to resolve incidents, not just problems.
There have been requests going back years for templates in Freshservice Solutions. How about we get this going?
After a couple of years with Threads and moving over from “Discussions” I have these suggestions for “Threads” that would be great to implement. They were already involved in Discussions, so it seems like a step back to not have this feasibility.Would it be possible for us to have a view of all tickets in which we are mentioned in threads, with a task? For example, in the notification bell, might we be able to “filter” notifications in which we are specifically mentioned in a thread? As was the case in FreshConnect, having the little widget in the bottom, right-hand corner provided a handy method of returning to previous tickets in which we were mentioned, in the event we weren’t able to tackle a project immediately in which we had been mentioned. Currently, we are notified on the bell, as well as email; however, our company relies heavily on this internal communication/collaboration within Threads and discussions for teamwork, so it’s easy for them to get buried or lost in emails if the notification is just a single instance notification without a designated placed to return later. Having something like the attached would be handy to be able to revisit those later. Doing the “highlight” feature in FreshConnect was handy, being able to isolate a particular part of the conversation within a discussion. Is there any possibility that functionality could be incorporated into the “threads”? PLEASE can we set a preference to MUTE a thread unless we are specifically @mentioned within it? I cannot express how many times I have been notified of a response in a thread that has nothing at all to do with me. It’s very distracting!
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.
