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.
As the FreshService Admin for my company, I wanted to create views for each group within my organization. We are relatively small, with only 50 employees - not a very high number, but as the Admin for the product, I would assume that I would be able to create a view and share it with employees in a certain group - it even seems there is a way to do this throught the UI.When I do that, I get a message saying my “View was created”, but I get a simultaneous message that tells me I don’t have permissions to do this - the view is never created and it is not available for the other groups.The only way to do this, is to add myself as a member of every single group. I tried that and I created the views and then removed myself from the groups, but that also removed the views I had setup for them.With being such a small company, I could walk around to 50 people and do this, but I still think that is ridiculous - as the Admin, I should be able to create the views that I want to and share them to the groups that I need to share them with. I couldn’t imagine implementing this in a larger company
I have a use case for a dropdown on a Service Catalog item where we have a list of vendors being populated from a custom object table. I can inclusively filter, but not exclusively filter. In this table, I’d like to have a column for “retired” where any time we stop doing business with that vendor, I can drop an X in the value. Then in the SC item, i’d have it configured so that Retired is not X. Right now, you can only select inclusively, which would mean I would have to swap retired to In use, mark every entry X and then over time remove the X from the in use field. Being able to do this exclusively seems to be quite the oversight from a functionality perspective.
When our reply to a requester cannot be delivered=is rejected, so the e-mail bounces, there should be clearer error messages within Freshdesk instead of generic "unexpected error" ones, where we then have to reach out to your Support team to find out the real reason.
Do we have a possibility to integrate a logic in change form in business rule where we can mandate that change requester will be able to request the start time of the change only after 24 hours of the current time. This will help in implementing the mandate of the organization where Change notice time will be 24 hours.
Implement a feature for Freshdesk Collaborator Agents to receive email notifications for any new Freshdesk Forum activity, ideally for all forums, but at least for a particular forum.Not just for a particular existing forum topic/post, which is already a feature.This feature will enable Collaborator Agents to know if there are new forum posts without having to go the the Forum on the customer portal to check all the time for new activity.
Can we can the “available in” selectable to Business days as well as Hours? eg: a piece of hardware is know to take 3 days to order and 2 for configuration so it’s 120 hours. 5 business days is a lot easier for requesters to understand...
When reading long articles in the knowledge base and you reach the end the user needs to scroll all the way back up to choose something else.Proposal:make the bread crumbs bar stay visible all the time make the related articles on the right stay pinned all the time in general maybe add a tree structure of articles on the left and pin them all the time
We are often contacted by email by new customers from new/existing companies where our agents will often have to edit some key elements of the customer details as we don't have a record of all individuals working within each company we work with: Name - Email display name will not always match customer name, will often be in format of last name, first name etc Company - Agent will allocate which existing company the customer is from if it isn't possible to do this from their email domain (hotmail, gmail etc) I'm sure other helpdesks will have other fields they'd like to see as the minimum for customers, but these are the key ones for us.The problem at the moment is that to edit these details the agent has to navigate to a separate page, firstly clicking on the customer name from the right pane of the ticket page, then clicking the edit button on the customer details page, entering/saving the changes and navigating back to the ticket. All of this can be quite time consuming.What I'd like to see is an 'edit' button next to the customer name on the right pane of the ticket page, which either opens up an overlay on the existing page, or makes the details shown for the customer editable in-line, allowing the agent to quickly make any changes to the customer's details and saving these without ever having to leave the ticket page.
Dear Team Good day, I am wondering if we can add the below to the roadmap Total received, resolved yesterday: Can we mention a date in the title instead of saying yesterday or Static title? Can we display the number # and percentage % within the pie chart?Thank you.
Sorry, it’s a long one.We are a Managed Service Provider (MSP) and as such our clients are companies and all our communications in Freshservice are with clients who typically have their own ITSM system or with their and our suppliers who we need to work to resolve issues with the system under our management who also have different ITSM systems and all of them use their own ticket reference numbers. We have done an analysis and around 40% of all our Freshservice tickets are duplicates (many of them are maintenance notifications from clients or their suppliers which we do need) which come from the fact that Freshservice (as many other ITSM systems) could not thread emails using third party ticket reference numbers. A substantial portion of these emails is generated by automated systems, lacking the attributes currently employed by Freshservice for effective email-to-ticket threading.An example – comms provider doing maintenance. That maintenance might not be touching just us, so even if they could, they would not be able to insert our ticket number in any further communication on it. Their ITSM system sends us at least 4 new emails – initial notification, notification a day before, start of works notification, completion of works notification. That is 4 tickets in Freshservice as the only common thing between all of them is comms provider ticket number, which Freshservice could not use for threading to the same ticket on our side. To address this challenge, we explored a solution using Power Automate as an email processor, coupled with the Freshservice API to accurately associate emails with the respective tickets. While we succeeded in achieving the desired threading outcome, unfortunately, we encountered a roadblock preventing the release to production. The impediment arose from the inability to insert embedded email images into Freshservice tickets using the API. Despite consultations with Freshworks teams, no viable workaround was identified.What we have done is not a rocket science and pretty straight forward – before an email is threaded to an existing ticket or new ticket is created the subject line is checked for Freshservice and Third Party reference numbers based on formats/patterns we have defined. Here's a brief overview of the features we had implemented, and we suggest getting it implemented in Freshservice:Hierarchy-based Ticket Matching - The system should check references in a predetermined hierarchy, prioritising certain systems over others. For instance, if there is a Freshservice reference, it should be checked first before exploring third-party references.Configurability - The system should be configurable to support multiple patterns for ticket references. This would allow us to adapt to different ticketing systems used by our clients and third parties.Linking Multiple IDs to a Single Ticket - It should be possible to link multiple references to a single ticket. This flexibility is crucial as emails may contain references from various systems (client, suppliers), and being able to associate them with a single ticket would streamline our processes.Updating Multiple Tickets from the Same Email - The system should support the updating of multiple tickets based on references found in the same email. This would be especially beneficial in situations where a single email corresponds to multiple tickets (for example same maintenance in multiple datacentres have different ticket numbers but update can be sent in one email).Visibility in Ticket Properties - Ticket references should be prominently displayed in the ticket properties, providing agents with quick and easy access to this information. This visibility is key to ensuring that agents have all the necessary details at their fingertips.Manual Addition of References - Agents should have the ability to manually add references to a ticket. This ensures flexibility and control over the matching process, especially in cases where references may not be automatically detected.Integration with Outbound Emails - References should be carried over to outbound emails if not maintained in the subject. This ensures consistency and avoids confusion when communicating with clients and third parties.Again, apologies it’s a long one, but it’s a sour point for us so hope to get some backing. Thank you.
In the field manager, for a dropdown you can select a data source as listed below but no additional options. We’d like to be able to use a custom object table with a list that we have to force specific items to be selected if conditions are met in a ticket (in this case vendors we work with). We cannot use a custom object table to do this, or even the vendor table that is native and being able to do so would be a huge capability lift.
Nowadays, ticket Merging allows merging an older ticket into a newer ticket.At simple sight, it would not cause any inconveniences. But if you use Analytics or have any dashboard related to response and resolution times, it will affect those metrics.How? Let´s suppose we have ticket A created on June 4th, which was responded on June 5th.Later, another ticket B is created in June 10th, related to ticket A. So the agent merges both of them. But selects ticket B as primary ticket. That would mean that all interactions from ticket A are merged into ticket B.The timing results show up as follows:Ticket created date = June 10thTicket first response date = June 5th (because the response from ticket A was imported).As the first response time is First response date - created date, this leads to the final first response time being a negative number, which affects all metrics resulting in misleading numbers. Here I have a clear example: When I export the ticket details to calculate the first response time, the final result was = -30 hours.I suggest to have a restriction at merging, like only allow newer tickets into older tickets or something of that sort to avoid this.
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.
