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.
Currently, shared fields can have Conditions added, but this is applied globally to every service item. It would be great to have the ability to add Conditions directly inside a specific service item to a shared field, so that the condition would apply only to that particular service item.In service item:In shared field manager:
It would be great if we could build the forms for catalog items using the identical interface that is used when building a form activity in Journeys. I feel it is a much better interface for building sections, managing dynamic dropdown sections and just an overall cleaner interface. It also allows us to put fields on the same line/row instead of one monolithic column. This would allow a more compact form experience and one that would allow a more user friendly experience.
We have Freshservice Agents on our team who have stated that they are trying to do a Service Request while on the go, but the FS mobile app doesn’t have the ability once you have changed the FS Incident over to Service Request to actually Add an Item from the Service Catalog. The Agents who have lengthy commute times are wondering if FS Mobile could be set up with this “Add Item” featurte while away. If it was there, associated ticket automations with an SR could be processed efficiently. And the web page instance of FS is unwieldy to navigate over Chrome browser on both a tablet and a smart phone.Does anyone else come across this feature request? And would your FS Agent teams find it useful, especially where it may concern automations for Service Requests?
Hello.We would like to maintain or limit the possible language options on the login page for the user registration. As the customized fields or specific articles are only translated in the main languages we think a limit language option would make sense and improve the usability.
As the number of important documents increases, tracking expiry dates manually becomes difficult. Most teams still rely on spreadsheets, calendar reminders, or email follow-ups, but these systems become unreliable over time.This is especially common for:passports visas contracts insurance documents licenses compliance certificates employee recordsA missed renewal can create delays, penalties, or operational issues.That’s why I started exploring better ways to centralize document tracking, expiry reminders, and renewal management in one place.Recently came across DocuAlerts which focuses on:automated expiry reminders secure document storage renewal tracking centralized visibility for important recordsCurious to know how others are currently managing document expiry tracking and renewal reminders at scale.
Please can the ability to open tickets in tabs within a single browser window be added, this will make working on tickets of the same type easier to view without having multiple browser tabs open at the same time. Other service desk providers have this functionality and I have found it very useful.
Related to this post, in our use case we need a way for the QoS team to easily identify whether agents are linking Knowledge Base articles (Solutions) to tickets.Currently, it is difficult to see this association, and we would like to know if there is an existing method or a possible enhancement to make this linkage more visible and easier to track.We are aware that it is possible to create a report using the Data Export option, but we are looking for a more native and straightforward way to view this information, similar to how it works in GLPI, for example.
We have teams who want to work more transparently with each other due to the nature of work on tickets they are submitting. There are often times they need to refer back to an older ticket for information that was provided. If John is out, he may need to search that information on a ticket James submitted. The team shares the tickets they create with each other for just this reason.The catch: although they can view the “shared with me” tickets, they can’t use the search feature in Freshservice to search those. It surfaces only KB content and their own tickets. Can this be changed to include also tickets shared to that requestor?
It would be really helpful to have markdown support on the Editor. It is really painful to format the solutions.
Currently, the system forces a ‘Related Ticket’ to be a ‘Child Ticket’ and the same ‘Type’ of ticket (Incident to Incident, Service Request to Service Request).Currently, when a Child Ticket is re-opened, it will force-re-open the Parent Ticket. When a Parent Ticket is Closed, it will Force Close the Child Ticket. This appears to be hardcoded functionality with no ability to change. “Related Tickets” should NOT be dependent, they should be “related” as in “linked” - e.g.:I want to be able to add links to tickets - any status, any type - to other tickets. Ideally, I’d be able to say “caused by” or “preceded by” or “caused” or “ongoing” Furthermore, it would make sense if in the “Similar Tickets”, Freddy did better at suggesting not only similar titles/Subjects, but also tickets from the same person, department, and that had the same Assets attached.
Hi there,I'd like to propose a feature enhancement regarding ticket sharing and access permissions.Currently, when a ticket is shared—whether via CC or via ticket sharing option —the recipient does not automatically gain access to the ticket unless explicitly granted by an agent that can access the ticket in the agent view. This can be limiting, especially for users who are CC’d but cannot view the ticket content, making the CC functionality less useful for both agents and requesters.Feature Request:Can we introduce a mechanism where, regardless of how a ticket is shared, the system automatically grants access to the ticket in alignment with the user's existing permissions?For example:If a user is CC’d on a ticket, they should be able to view the ticket based on their role and permission level. If they are Requester only they should see the ticket in the support portal view. In the agent view, even if the agent is not the owner or primary assignee, they should be able to access the ticket with visibility limited to what their role allows (e.g., public notes only). Or alternatively redirect the agent to the support portal view.This would greatly improve collaboration and transparency, while still respecting permission boundaries.Thanks for considering this!
I’m kind of shocked this doesn’t already exist, but having the ability to add To-Do list items would be extremely useful.Example Scenario:A New Employee is starting. When that ticket type is changed to “Onboarding,” add items to To-Do list (Provision computer, create account, mail accessories.” There are so many repetitive situations this would help
Currently, toast notifications will ‘go away’ on their own with the exception of closed tickets that will just stay there for seemingly ever. This is really frustrating to have to manually close out of every time we close a ticket. I like the toast notification and have had to click back into the ticket, so I don’t want it gone forever, just to go away on its own. Can we please make it so? Alternatively, if anyone has a solution to this issue, sharing is caring! Thank you! 😊
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.
