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 to see a feature to report thus ways in the workflows which are used rarely or never.benefit: regular cleaning up and streamlining of the rules
Hi there, Currently we can only manage Service Catalog visibility by requester groups. That is great but limited for mid and large sized organisations with more complex IT Service organisation. It happens often that agents creates Service Items as well. However currently all agents have access to all Service Catalog Items. It would be nice to manage granular access by agent groups to Service Catalogs as well.What do you think ?Regards, Stefan
Is it possible to export the knowledge base solutions? We are keen to populate the knowledge base but then we would be vulnerable if we can't keep a backup of the information.
It would be nice to have a way to define packages being shipped to end-users and update the support tech when the tracking info shows the package has arrived. For instance, if I attach a UPS or FedEx tracking number, it will provide tracking updates as the package is updated by the carrier as a private note on the ticket. This will make it easier for large-scale shipment to remote users, like what many of us are facing right now in the wake of the pandemic.
I find the solutions editor super clunky and it makes it difficult to format articles properly. It would so much better if the editor supported markdown. This would help make solutions easily readable without having to fight the editor to make it do what you want.
My team and I like to use Team Huddle to discuss open tickets. However we are constantly missing team huddle conversations because we are not effectively notified of a new team huddle or a team huddle response. What would be good is either a pop up notification within the UI that grabs our attention better than the standard notification panel in the top right or even a push notification straight to each users desktop.
�We have a global support portal and a product for a second one. When looking at filters for product, the global channel is named "none", can we rename this?
To avoid emails having inconsistent fonts, I would like to see a font seletection (drop down) when composing an email in the Automater
Would be very helpful to be able to add private notes when tickets with certain conditions come in, to provide a prompt or link to solution/website/software that the agent will need to resolve. This can be done with Observer, so why is Supervisor and Dispatcher different?
we need to use "add note" in bulk actionsprivate and public note
It would be great if you could assign tasks to requestors. Bit limiting having to first assign a user agent rights before assigning them tasks. The users i'm speaking of typically wouldn't be resolving tickets, but would be a dependency on an existing ticket in order for it to be completed.
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.
