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’re a special needs school for kids with Autism and are evaluating Freshdesk for use as an internal corporate help desk system. We need the ability to apply SLAs based on the category->subcategory and priority of the submitted ticket.For example: assume we have a ticket category and subcategory such as: “Facilities->Building Security” and a staff member submits a ticket for this category with an Urgent priority. We need to be able to assign an SLA for this specific ticket type which likely has a very different response and resolution times than say, an Urgent priority ticket submitted with the category and subcategory “IT->Internet Access Down”.
Effective root cause analysis requires group review to ensure the problem is properly identified and addressed. The FreshService settings should allow and approval to be required before the Problem can be closed.
Currently, if you want to “free up” an agent license - the only way to do this is to remove the agent. This means you then lose all their history as you have to transfer it to another user. This is just wrong from an audit trail and compliance perspective. You should be able to remove an agent license from a user and keep their history
We need to be able to select all agent groups from all workspaces in a drop down in the Custom Fields data source. Please add it.
Solution Articles should have a field to be able to add “internal notes”. This would be helpful for information on when the information was last verified, caveats to the information that is presented, etc. It would be visible in the agent-side of the knowledge but not in the portal.
Freshdesk currently allows only four priority levels (Urgent, High, Medium, Low). We’d like the flexibility to add a fifth level to follow a P1–P5 structure, and we need the SLA timer to work properly for this additional priority as well. Please consider adding this feature.
Current Challenges with Bulk UpdatesLimited ticket selection: Freshservice currently restricts bulk updates to 30 tickets at a time, which slows down large-scale changes. Private Updates: Unable to add private updates to tickets via bulk update tool, which is difficult for admins to manage large numbers of tickets without using a workflow tool. Bulk Updates in Change Requests: Having the ability to bulk update change requests is also only possible via workflow tool but doesn't allow for dynamic questioning or notes. Mandatory fields frustration: Users often need to export, reformat, and re-upload data for fields they don’t intend to modify, leading to inefficiency and errors. Rigid workflows: Existing options (Bulk Action, Scenario Automation, Supervisor Rules, Scheduled Workflows) lack flexibility for dynamic conditions and large datasets. Modernisation Ideas 1. Dynamic Field HandlingAllow users to skip mandatory fields if they are not being changed. Introduce smart validation that only checks modified fields, reducing unnecessary errors.2. Enhanced UI/UXReplace the current pop-up with a multi-step wizard: Step 1: Select records. Step 2: Choose fields to update. Step 3: Preview changes before applying. Add inline error handling and real-time feedback for formats (e.g., date fields).3. Scheduled & Conditional UpdatesIntroduce conditional bulk updates (e.g., “Update all tickets older than 30 days with status = Pending”). Allow scheduled execution during off-peak hours to minimise impact.4. AI-Assisted UpdatesUse AI to suggest field values based on historical patterns. Implement predictive checks for common errors (e.g., incorrect date formats).5. Improved Asset & Service UpdatesEnable nested field updates and bulk clearing of values without re-uploading CSV files. Support dynamic filtering so only relevant fields appear for selected asset types.
While the new Analytics update (April 2024) provides a way to favorite reports to allow for ease of finding them. We would love to see an editable folder/category ability within FreshDesk from an admin level. The goal would be to categorize the reports based on customer needs.Using our configuration we would look to create categories by team (Content, Implementation, Support & TAM) and then by function/frequency.
Hi,I have got an idea: Let’s make catalog items import/export able with bulk or mass operations ofcourse.- Imagine you have catalog full of 1000 items, but you have found that there is mistake in the one field you have in every item. In the current state you have to click every item and fix it. But with export into xml, you can fix it with script in all items at once. 100 hours saved! 🎉🎉🎉🎉- Imagine you have fresh freshdesk with empty catalog and you need item for this and that. But hey, there is a community forum and somebody already did it! X hours saved! 🎉🎉🎉🎉- Imagine you have completed catalog in English but you are multi country company and you need translations to local languages because you are in automotive. But hey you can export items in English, put them into translator and import them in language you need. Lots of hour saved! 🎉🎉🎉🎉Save time and make the helpdesk useful for agents too :)BR.Karel
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.
