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.
Is it possible to add watcher to ticket from SDK or API today? Cannot find it...
Would love to be able to see the actual conversations people are having with the search box on the end user support portal. That way we could know what subjects we need better documentation for in our knowledgebase.
Users might associate it with an "About" or "FAQ" link. The icon-graphic could use a clearer symbol
Often times, an agent will either be new and learning, or in a hurry, and they will accidentally merge the wrong ticket. When they realize the mistake, they need to re-open the original ticket, then copy/paste any replies back into the original as notes. This is hugely time consuming, and it would be really helpful if there was a way to reverse or undo a ticket merge after it's been completed.
Add the option to notify the Assigned Internal Group and Assigned Group instead of just the Assigned Agent. This will help allow for increased visbility by a supporting team in case of leave etc. We make extensive use of Internal Groups - this would be highly useful
Currently dynamic sections are limited to 5 and are not allowed to be nested.We use a lot of automation in the Service Requests and recently hit the dynamic section limit of 5 for mutliple requests.Please rise the limit of dynamic sections to at least 10 Please allow us to nest dynamic sections within dynamic sections or multi drop down fields
A feature to autosave a draft of a new article created for the Knowledge Base would be great. (Recently lost an article that hadn’t properly saved prior to Google Chrome updating.)This feature would work similarly to Google Docs or Microsoft Word’s autosave feature to prevent the lost of content when writing. This doesn’t have to be as fully featured as those 2 examples but just a backup to prevent total loss of content for those extreme situations.
OMG can we PLEASE get API access to Workflows? This point-and-click building is killing me!
Welcome to our website I will provide Whatsapp Groups entertainment, sports, IPL, cricket, education, news, Kerala, gaming, BGMI,France technology, shopping,foreign girl,ludo money and More active whatsapp group 2023.Enjoy Latest Whatsapp Groups Link 2023.
It is incredibly frustrating that you can add a tag with an automation, but not later remove it with an automation, meaning an agent has to manually remove it (or use a long winded API approach, as previously suggested by Freshdesk in another post that originally raised this idea four years ago).
Hi 🙋🏼, I found that when I checked all our set business rules and workflows, some would be activated but essentially useless because a value used inside a condition for example was altered elsewhere and therefore removed from the condition statement. There is - to my knowledge - currently no other way than checking each rule in depth to see this problem in the flow even exists.Maybe an indicator/warning 🚨could be added in the list-view of business rules and workflows to see at once where such problems inside a rule or a workflow occurred.I think this would greatly improve debugging and make it easier for changes to be made in production.
We currently deactivated the standard requesters notifications in freshservice and are using workflow automators instead for one and only reason: exceptions cannot be configured in the standard notifications settings to avoid notifications being sent to specific requesters. This is needed because some of our requesters are also our suppliers, they're of course using ticketing tools at their side and enabling notifications for them creates loops of notification messages being sent between their system and ours.Would it be possible to add that feature (exceptions list) for each type of notifications so that we could use the freshservice standard requester notifications instead of automators ?
Normally you can clear First Response Due by adding a Public Note on a ticket. However this does not work on tickets that you open yourself and assign to yourself. This means the only way to clear the First Response Due is by emailing yourself after you open your own ticket. This is a silly workflow that just adds an unnecessary step in for the Agent. If they forget to do this, then it messes up statistics on the First Response Times. Please make this make sense and either remove First Response Due all together for self-opened tickets (since if you are opening the ticket for yourself, of course you’re aware of it and no response is needed). Or at least let a public note clear it. Remove requirement to self-email please!
It would be very helpful if the Customer Portal could remember each user's preferred conversation order within tickets.Currently, every time a user opens a ticket, the interaction order resets to the default (for example, "Recent first"), requiring the user to manually change it back to "Oldest first" each time.For customers who frequently review long ticket histories, especially support teams and technical users, reading interactions in chronological order is much more efficient. Having to change the sorting option on every ticket creates unnecessary repetitive work and negatively impacts the user experience.Suggested enhancement:Allow customers to save their preferred conversation order (e.g., "Oldest first" or "Recent first") in their Customer Portal profile. Alternatively, remember the last selected sorting option using the user's account or browser session.
Mer Méditerranée ↓ Suez Mer Rouge ↓ Bab el-MandebGolfe d’Aden → Océan Indien ↙ ↘Somaliland Djibouti | ↙↓↘Bases UAE USA, France, & potentiels Chine, Japon, Italie, Espagne ↓ Positions russes / discussions en Soudan
I like to have the date format a specific way for ease of sorting things. I prefer YYYY-MM-DD, but the fact that it displays the date as Fri, 2026, Jul 17 is not very useful. As I am sure some if not most of you are aware, not all onboarding and offboarding’s come in the order they start or leave. It would be nice to be able to change how the date is formatted. I would like it the title of the journeys to look like this Journey - Offboarding [2026-07-17] - Jimmy Jones #JNY-90
In Admin you can create a location hierarchy which you can then assign to an asset.But there is no way to see this location path or location details in an asset and you can’t even search for a location to find it in admin to see the path or details without clicking through the hierarchy. Assume Location Path as: Country - City - Site - Building - Floor - Room - ‘Rack 15’‘Rack 15’ contains a Network Switch that has an asset and the asset is assigned to ‘Rack 15’ Now have an non admin agent try to find the location of that asset, good luck.Please show the location information somewhere in the asset details view.
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.
