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.
Our organisation faces an interesting challenge: Freshservice only supports American English, while our corporate communication predominantly uses British English. As a result, our service catalog(ue) items sometimes mix both languages (e.g., “licence” vs. “license”).We’re keen to improve the user experience and consistency for our employees.Question for the Community and the Freshworks team:Have any of you encountered a similar situation?How did you address mixed language issues in your service catalog(ue)?Are there any plans for implementing a “Did you mean?” functionality that suggests the correct spelling based on the user’s preferred language? Looking forward to hearing your insights and experiences! 🤔
We love the fact that Freshservice has a Projects module so we can connect the dots on SR’s and INC’s as they relate to larger projects. The trouble I have as a manager is the Projects doesn’t have any overall activity page to show what tasks have been worked on within a specific time frame. Another oddity is that you can’t just click to mark a task ‘Complete’ and it automatically fall off the list. Instead you use task status as a way to keep up with what needs to be worked on. This isn’t very intuitive based on having worked in several other project specific platforms like Teamwork Projects and Asana.
Currently Freshchat PRO standalone doesn't offer holiday setup. Every time we have a holiday we need to remove the corresponding day from business hours and remember to add it again once the holiday has passed. The feature is available in bundled versions of Freshchat but not in standalone.
Currently when merging a ticket, the tickets that have been merged to a master ticket are not included on the master ticket in the “Related Tickets” tab. Including the merged tickets in the Related Tickets tab, or potentially considering them as “Child Tickets” would enable additional automation opportunities, assist in reporting and generally improve user experience.
For some languages, such as Chinese and Japanese, a title can be less then 3 characters. For example, the Chinese for Download is 下载, which means this title cannot be used since Freshdesk requires that titles must be at least 3 characters. This is somewhat limiting and I’d like this limit to be reduced to 1 character.
It would be nice if adaptive messaging could be used to create a survey via webhook. The idea would be to create an email with the survey embedded in the email as an adaptive message. The registered message handler app would then call a webhook in which the body of the payload would contain the survey and the endpoint would cause the csat to be created against the ticket. I’ve done this in another ITSM platform and this method tripled the survey response rate. This was in a microsoft environment and was limited to tenant email domains. FS could not be responsible for the adaptive message handler of course, but just having an endpoint that could create the survey would be nice.
In trying to cut down email clutter, I’ve created a rule that automatically closes any tickets that have any of my agents CC’d on, and responds to the requester to try again without an agent CC’d. However, this rule breaks my ability to forward in tickets from my email because, well surprise, I’m now CC’d on the ticket due to some internal automation that Freshdesk does with forwarded emails. Please expose the automation rule on email forwards so I can disable the automatic CC function and continue moving forward with cleaning up my email clutter.
There is currently no way of checking the eml of a ticket to see headers.We don’t keep any email on our servers so to debug it’s not possible to view EML file. The only way would be that Freshdesk saves that.
Check ticket: https://support.freshdesk.com/support/tickets/16264243 All message coming from Zendesk are flagged as automated response which is not correct.
Hi, I’ve noticed that Automation Time Triggers can add tags but they cannot delete tags in Freshdesk. Is there a reason for that? It would be really helpfull from a process/type of tickets control perspective to be able to add AND delete tags when needed using Time Triggers. Is there a plan to implement that into Freshdesk? Thank you.
Hi team, We have several ocasions where a customer needs to update very old tickets but there’s no easy way to do it in Freshdesk, since there’s a 30 days automation limit. Our customer just migrated from zendesk and without doing a script our using manual operations, they cant really change their old tickets anymore. Please take this as a feature request.
Good morning, I write because the customization capability of the dashboards is extremely limited. We cannot create dashboards according to our needs. We would like to be able to modify the main Dashboard, or if not possible, at least to be able to make a copy and modify it. I also suggest that you can add banners to the dashboards (text widgets, if I may)... I suggest removing the limitations on the number of widgets in Dashboards. And that the SLA statistics can be customizable. Greetings,
I see this topic has been brought up several times before and has been closed for voting each time. I believe this was on the roadmap for this year, but I don’t recall exactly when it was to be implemented if it was. It would be incredibly helpful to be able to re-order the Service Request Categories in a meaningful way. As it stands now the Service Request Categories seem to be randomly placed on the helpdesk portal and shift randomly if I re-order the categories in a workspace. Please make this option available as soon as possible, thanks!
When using “Insert code” in a Solutions article it is invariably because we want the end user to be able to copy all the code and paste it elsewhere. Marking the text to copy is surprisingly cumbersome - how about adding a Clipboard icon to the control for easy copy? # This is PowerShell code, a template that for some reason is not available in Freshservice.# Copying everything in the box does not appear to be much easier, though.
New feature to allow us to relate Service Requests to Incident tickets within the Freshservice ticketing system.It is often necessary to request new services to resolve incidents. For instance, when an issue arises with a user's device, we may need to create a Service Request to resolve the issue. However, the current Freshservice system does not allow us to relate these two types of tickets, which can cause difficulties in tracking and managing related issues.Example Scenario:An incident is reported where a user’s laptop is malfunctioning. To resolve this issue, we need to request a new service, such as a replacement laptop or additional accessories. Currently, we cannot link the Service Request for the new laptop to the original Incident ticket. This lack of linkage makes it challenging to see the full scope of the problem and the steps taken to resolve it.
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.
