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.
If I have a company in freshdesk, and that company stops being a client, we would like to be able to switch off the company. That way the contacts still exist (and there could still be tickets assigned to those users) but they will not appear in the Requestor field when we are searching.
The new notification center is very good, but it would be really nice to see notifications for new solution articles or when updates/ edits are done to existing articles. It would help agents keep solutions "top of mind", and also pitch in by updating and creating solutions on their own.
Since last update, whenever we enter a ticket, field "Requested Items" rolls down, so the outcome is that we cannot see a ticket before clicking on "Requested items" to open them. From our perspective this feature makes no sense since: When I enter a ticket I would like to see content of it When I have to dispatch many tickets it makes me inefficient When I am a manager I don't want to waste time on clicking so many times (for my department all SR has to be approved by me) so now I have to click on Requested items, then approval Window "jumps" when rolling down occurs Request: revert that change, it was better before.
It would be very useful in a busy IT team to have the requesters mobile phone number showing on the Request Info section of the ticket screen as well as the existing email address and Phone (which is the Work Phone field). Most of our user base is mobile based so if we want to phone the user from the ticket screen, we have leave the screen and go into the requester screen to get their mobile phone number. It would improve productivity if the mobile phone number was also available on the ticket screen.
From the 'view all task' view on the Dashboard it would be nice to be able to sort the list. Maybe even drag and sort based on what you're looking to prioritize for the day.
We have some fairly long service catalog items and it would be great for our agents to have the service catalog item within a ticket formatted better. If it were possible to either insert HTML through the API or format them (preferably through HTML) while creating the item in the service catalog I think it would help sifting through request information.
Is it possible for you to break down your pricing plans into add-ons? It be nice to pay for what we need instead of paying for a plan where we only need a selected features. Such as live chat that's only available in gardeb
We'd like to use the new custom ticket reporting to spit out a weekly report that contains a bunch of data, but have noticed some shortcomings that could be improved: - date range should include an 'undefined' or 'infinite' option (or not be included at all). If we have a long running job (>90 days) we currently need to specify a fixed date, which means the report has to be edited every time it's run rather than being generated automatically on a schedule. - columns should be easy to reorganise using drag-and-drop or similar. - options to sort multiple columns alphabetically ascending and descending. For example, sort by Agent, then Company, then Contact, etc. - dynamic column sizing. The 'Subject' field contents are always long, and the 'Ticket ID' is always short, so having non-static column widths obscures data and increases unnecessary white space.
This seems like a no brainer to me and am surprised it's not default behaviour or even possible. If a user sends an email to our helpdesk email it generates a ticket, great. If they flag their email as high priority the ticket should automatically be set as high priority as well. Won't hold my breath but would love to see this implemented. Regards, Phill
I think it would be a good idea to be able to create a seperate customer feedback form for the website widget- seperate form the ticket fieldsWe currently have our ticket description field as 'Description of your problem, request or query'- this will confuse users who click on the widget to give feedback
I am in a situation that should be familiar to people trying to integrate their helpdesk with other platforms:The companies we do business with are already assigned unique GUIDs in our ERP platform. The GUIDs I am talking about are unique IDs looking like "6d2d2107-3112-4d47-a439-1b3b8ffd6e83".In order for our systems to interconnect they must be able to reference each company by the same ID and using our ERP assigned GUIDs is our preference (for a number of technical and policy reasons we do not want to store the Freshdesk IDs of the companies to our ERP - it has to be the other way round).In Freshdesk, I can create a custom text field field for a company and store those GUIDs there. However, this approach has an important disadvantage:Freshdesk does not care if the ID I am storing there is unique or not - it will happily allow me to use the same ID for more than one companies. The fact that Freshdesk does not allow me to create a new company with the same name is not sufficient protection as company names are not very reliable as IDs (ie "W.BLACK LTD", "W. BLACK LTD", "W BLACK LTD." etc)I propose that Freshdesk either adds a special field called 'external_id' to companies and contacts (BTW, that is what Zendesk does). This will be a text field. Freshdesk will make sure that non-empty values stored there are unique.Just to explain what we are trying to do: We will bulk import our existing customer list to Freshdesk (including the GUID of each company). Then, we will write a Freshplug that, for each company, reads the GUID stored in Freshdesk, make an API call to our ERP and get information from it (for example, the current company name, whether this customer has a valid support contract, a link to the relevant webpage of our ERP etc). This Freshplug will be available at the ticket level and will provide the supporter with useful information.
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.
