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.
I am maintaining a master of my application using custom object. I have about 20+ object fields with 500+ records in my custom object. Depends on business change, we need to update the custom object, and it might involve only few records. Right now, the only way to find a specific record is to export the entire list, search for it in Excel, and then re-import the file if we need to make changes. This is risky because it can accidentally modify other records during import, and the whole process is slow and inefficient.It would be really helpful if we can have a search button to search for specific record instead exporting the whole list or scrolling few pages just to perform 1 update.A simple search function would: Prevent accidental data changes Save a lot of time Make updates much safer and easier Improve the overall user experience This feels like a basic feature that would greatly help anyone managing Custom Objects.Thanks for considering this request!
As an agent it would be great if we could add filters to a ticket view to our own specifications and then set that ticket view as the “Default” view we see when signing into freshservice.
The ability to print the available data from an asset is absolutely broken. For a single asset with <50 fields it is showing is 24 pages and almost all of those pages are entirely blank. We occasionally have to provide audit artifacts for certifications and submitting the data in a csv/excel spreadsheet is less than ideal and can lead to questions about data integrity compared to a PDF printoff.
We are maturing our Asset Inventory and looking at optimizing our experience for the risk team. In speaking with them, I realized that the ability to have a separate tab on Assets that has fields list would be huge. With this idea, we could expose the fields for risk related questions (what kind of data does this house, how much, etc etc) that IT doesnt necessarily “care” about. It would also give better capability so far as being able to print out a copy of the data to PDF for an audit artifact and not have it contain all the additional fields that are related to the specific item such as SLA, Operational state, documentation reference fields, etc etc.
Agents need to be able to be defined by Workspace, so they can be ‘Agents’ in one Workspace and ‘Requesters’ in others. One of our biggest issues with Freshservice is how “Agents” in any workspace are treated as an “Agent” in all other Workspaces. If Agent/Requester status were defined BY WORKSPACE the world would be a better place. I’ve brought this up a few times - the answer is that this is “by design” - but it’s poor design. I have a Global Automation to re-open a ticket if a Requester replies or adds a Public Note to the ticket. However, if someone from the HR Workspace adds a Public Note to an IT ticket, the ticket will not re-open. There is no way for HR to request an IT ticket be re-opened if they aren’t the original requester of the ticket without ‘outside intervention’In the IT Workspace, I’ve tried setting up an Automation to help with this, but there is no way for me to say “If Agent in THIS WORKSPACE vs Agent from OTHER WORKSPACE” in the Automator. If I say to re-open a ticket if an AGENT replies, then the “Send and set as...” options become useless, as whatever status is set will be un-done by the automation immediately. There are many other issues with not separating ‘Agents’ by Workspace - our HR team regularly misses updates/email replies to tickets on which they are Requesters because they filter all Freshservice emails. I had to create an entire walkthrough of how to create certain Outlook rules for tickets, but most agents do not use them. We have many Agents in our organization who gave up on “working around” these barriers in Freshservice and just decide they’ll direct Teams message anyone and not enter tickets at all. Requester Groups also mean nothing with they don’t include Agents from other Workspaces.
Hi everyone,We are currently migrating to Freshservice and building several large and complex workflows.During this process, we’ve noticed a major limitation — when different condition branches require the same action, we need to duplicate that action node multiple times. This makes workflows harder to maintain, more error-prone, heavier to load and manage and time-consuming to update when something changes In most modern automation platforms, this is solved with a “Looping” or “Shared Action” capability — allowing multiple conditions to connect to the same action node instead of duplicating it. I understand from support that this feature is planned for mid-2026, but given how impactful it is for real-world workflows, I believe it deserves higher priority.This improvement would simplify workflow design dramatically and help many teams migrating to Freshservice. 💡 Suggestion:Please consider accelerating the release of the “Looping” feature to early 2025 or make it available under Early Access / Beta for customers facing complex automation use cases. Would love to hear from others — is anyone else facing the same pain with duplicated actions?Thanks,Gabriel
It would be a nice QOL feature if Assets had descriptive titles like the Tickets do.For example, when a ticket is open the browser, it shows [#1234] Ticket Subject | Portal NameAssets only show Service Desk : Portal NameSometimes I open multiple Asset records that I’m working with on different tabs. It would be nice to see what tab I have what asset open on easily.
I would love to see the option of adding a time entry included under both Bulk Update and Scenario Automation.As we require time entry before any ticket can be closed, we can’t fully automate ticket handling- the agent must always add time on each ticket individually before they can close the ticket. There are 2 instances we encounter frequently where this is not ideal:Frequently submitted tickets where we know the entire solution and, ideally, would initiate a scenario automation to categorize, add update, add solution, add time and close the ticket as one action. Responding on outage tickets where we may have a dozen or more people who called in the same issue. We’d like to do a bulk update to categories, set agent, set solution, send reply and account for time spent rather than processing one at a time.
It would be great to built a more flexible Service Catalog with Sub-Categories (maybe 3-4 Levels would be great)
Currently product notifications are displayedAs a number next to the help button at the top toolbar As a number on the favicon of every open tab Favicon exampleToolbar exampleI don’t mind reading about upcoming updates, but the Freshservice marketing team are in full swing and there is an update every day, sometimes more than once a day.The product update notification updates the browser tab icon and is right next to the ticket updates notification icon, so I keep thinking I have a new ticket update when I look at Freshservice, but its just a sales message and is distracting.My suggestion is to incorporate one or all of these:The product updates number should be a different colour, perhaps grey or blue Blue product update example The browser favicon should show ticket updates and not marketing updates. This would be a real boon for the product. Imagine being able to check your browser tabs to see if there was a ticket update! Product updates should have an opt-out option Product update notifications could be associated with an agent role, like admin or managers.Some discussion has already occurred on another thread, see Disable products update notification | Freshworks Community
Currently Maintenance Window recurrence is limited to several months. It is better and easier to manage planned maintenance windows a year at a time. Suggestion is to allow a recurrence expiration date up to 1 year from current date.
In order to offer users a better experience, we would like to give the chatbot in teams a more personal name. It would be great if we could customize the name and profil image of the servicebot/virtual agent in MS Teams.😎
Es wäre sehr hilfreich, wenn man angehängte Dokumente bearbeiten könnte.Durch Anbindung/Integration von ONLYOFFICE oder ähnliches.Damit hätte man eine Alternative zum integrierten Editor, dessen Fenster ja bedauerlicherweise an vielen Stellen nicht mit wächst und man so immer ein externes Dokument braucht, um eine Problemanalyse dokumentieren zu können.
Hi team, I recently passed the Freshdesk Product Expert Master certification exam, but the certificate I received is linked to the wrong email address. My correct email is ismailozerguven9@gmail.com, and I’ve already contacted University@freshworks.com, but haven’t received any response yet. Could someone please help me fix this issue or forward it to the right team? Thank you very much for your time and help! Best,Ismail Ozer Guven
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.
