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.
Being fairly new to Freshservice (we moved over in 2021), we were excited to finally reach a point where our “year-over-year” reporting is actually able to show trends such as what time of year we seeing upticks in ticket count, upticks in new hires, etc. Up to now we’ve had to manually pull numbers into Excel to combine our old system counts with Freshservice since it’s hard to know a trend from a spike with less than 2 years of data!Now the FUP program has been announced that will require us to restrict our reporting to no more than a 2 year period! So we’re going back to the same boat of having to manually pull data to Excel for reporting :( I can appreciate the concerns prompting FUP but it feels like there should be a way to permit an exception. Possible workbooks that have only a single page or are limited to the number of widgets? We don’t need to see most of our analytics back further than 1-2 years but there are a few instances where that extended trend is really important.
In the Project module there is no functionality to look at the project grouped in different portfolios and look at the status of the projects. The status could for example be how the project is performing based on cost and also based on time. The different status could be in different colors that show green, yellow, red for example. This should be possible to show on a board for projects.
When managing Software fields in Asset Management module, there is no provision to add a lookup field for Group. It is possible to add a dropdown, but not one with a lookup.The ability to add a lookup field would be a major functionality improvement for Software Asset records.
The ability to view subtasks in gantt view in a task could help planning of our projects and tasks.
When searching through tickets made by colleagues, it has been requested to have an “All” option in the dropdown, to see all tickets made by the company in the same view. Otherwise you could select tickets made by yourself or specific colleagues only.
Hi Freshdesk/Freshworks team,I’ve recently been investigating ways to integrate an AI chatbot with our Freshdesk service desk. So far, the only practical approach I can see is to build something externally using API connections into Freshdesk.I’ve been disappointed to find there doesn’t seem to be a straightforward way to integrate a custom, configurable chatbot directly within our IT team’s Freshdesk experience (ideally embedded in our day‑to‑day workflow), to improve accessibility and self‑service.What we’re looking for is a chatbot that can be configured to:Query and report on tickets, including open / closed / pending statuses Support common ticket actions (e.g., status updates) Help out IT Team navigate and make better use of our Solutions / Knowledge Base, which we’ve built up over the yearsDo Freshdesk have any plans on the roadmap to provide a built-in service like this within Freshdesk, rather than relying primarily on custom API development
The new version that just launched is missing a scroll bar and it is causing issues. Could you please add the scroll bar back?
Please add a cart / basket for the service desk so multiple items can be created with the same ticket.I know you can already add ‘Additional Items’ however that would mean making an entire list of the complete catalog as an additional item for each item, which is just not feasible.
wishing there was a method to loop, or call part of a workflow… e.g. having multiple condition statements that would run in sequence regardless of the previous condition’s result.
If an Incident is associated with a change “change causing this incident” the Incident is not displayed on the Change > Associations > Tickets caused by this change list.
We are running into an issue with asset management due to having 2 workspaces with assets enabled. When selecting Managed by Group in the secondary workspace’s inventory, it brings up the groups from our primary workspace instead.It would be much more useful to have this field pull the groups from the appropriate workspace, like it does if you are an admin on the account.
We are the top mobile application development company in India having 10+ years of experience in Custom iOS & Android Mobile app development Services. Hire Best App developers from Quytech.
Enable Two-Way Synchronization Between Google Admin Console and Freshservice ChromeOS Device AssetsDescription:Currently, the ChromeOS Device Discovery in Freshservice provides a one-way sync that imports Chromebook asset data from the Google Admin Console into Freshservice. This helps keep our asset inventory up to date, but limits the ability to manage and maintain Chromebook information efficiently across both systems.We are requesting that Freshservice introduce a two-way sync capability, allowing select editable fields to be pushed back from Freshservice to the Google Admin Console.Business Need / Use Case: Our team frequently updates asset information such as: Assigned user Location / department Asset tags Notes / ownership info These fields must also be kept accurate within Google Admin for proper device management, assignment, and auditing. Because the current integration is one-way, any updates made in Freshservice require manual duplication in Google Admin, increasing workload and risk of inconsistent data. A two-way sync would streamline asset lifecycle management and eliminate redundant administrative tasks. Requested Functionality: Two-way data synchronization for key Chromebook fields (e.g., user, asset ID, location, notes). Ability to configure which fields should sync bi-directionally vs. one-way. Sync scheduling options (e.g., real-time, hourly, daily). Full audit logs for changes made via sync to Google Admin. Impact:This enhancement would: Improve data consistency between Freshservice and Google Admin Reduce administrative overhead Streamline IT asset lifecycle management Improve accuracy for audits and reporting Enhance Freshservice’s value as a single source of truth for IT assets Priority: High — affects daily operational efficiency for Chromebook fleets.Optional Add-on:If direct two-way sync is not feasible short-term, an API-based “write-back” option or webhook-based update mechanism would still provide significant value.
Hopefully a simple request. In the monitoring tools, the Alert reopen interval allows for minutes or hours. This is good for most things, however for our use case we’re experiencing unnecessary tickets due to being restricted to a 24 hour reopen interval. Use case below: We’ve setup a monitoring tool with a vendor so that when a ticket alerting us to an issue on their side, the email flows into FS via alerts so that only one person is able to work on a team, auto assignment happens, etc.When new comments are posted, the notifications all flow into the same original incident, however when the ticket is resolved on our side, a day or two later the vendor will automatically email out asking for “customer approval” on the ticket, then again a week later (at this point the emails stop). The same resource is parsed out on each (which is what alerts are grouping under) but the 24 hour restriction means I now have 3 tickets for the issue instead of 1. While training people on the team to wait to close until they render an approval is possible, I think this use case, as well as others, would merit an expansion of the criteria to be able to accept days (max 30?) Unless of course some of you have thoughts on how to get “around” this/shameless upvote plug? @mbutler @Daniel Söderlund @msconfig87 @zachary.king @DanielRuff
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.
