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.
Please integrate with Asset Panda for the Assets module in Freshservice.
We currently use Power BI to provide dashboards across our organisation which pulls through data from various applications that we use including FreshService. We would like to be able to integrate FreshRelease with Power BI as well so that we can reduce the manual reporting
There is very basic email validation in the feedback widget which leads to end users creating tickets with an invalid email and no way to contact them. Adding a simple API validation to ensure the mailbox is reachable would stop this. Could this validation please be added to the email field on the feedback widget.
Please add a feature to sort by Language and/or Country so that I can easily see all tickets for my country at a glance from the among the all the countries tickets mixed and spread.This is a very much requested feature for all regional supporting crews because each crew is interested in their language/country tickets only.It should be an easy task to add this feature and I hope to see this feature added in a few weeks.Best regardsTradingView Supporting Center
Feature Request: The ability to sort tickets by "response due" or "customer responded". This is something we monitor to make sure we are responding on time to our customers. It would be helpful to sort and report on this.
Currently sorting is limited to set fields within FreshService We have implemented a lot of custom ticket fields and would like to sort by that.Is there a workaround or could this possibly happen in a future update?
Freshdesk mobile app helps a lot when we are out of computer and we need to reply a ticket, add a note, etc...But when it comes to proactive support, notify incidents for customers, monitored internet link going, etc...it would be really awesome to use ticket templates within mobile app.Those same ticket templates available on web desktop version.It's really annoying having to type a similar text every single time, specially on mobile.So far, i open the ticket system URL via browser with/without desktop mode to send out tickets usings templates.Regards,Rafael da Costa
Ability to add custom fields in Kbase Import solution articles Kbase - To have a “cache” of keywords
I request that we be able to restrict access to certain marketplace apps so that they are only visible to certain agents or Groups of agents.The use case is some of the apps may have sensitive information or require special knowledge/training to use correctly. It seems that there is no way to do this unless the marketplace app actually has developed an access privilege feature within the application.I think this generally should be a feature that is used especially when you have multiple large groups of agent using the system and have them change on an on-going basis. There is just no way to control misuse of an application and the honor system will never work as a methodology for access control. Least privilege all the way!
Hola Comunidad tengo la siguiente consulta, estamos utilizando Freshdesk para servicio al cliente y Jira que es el quipo de desarrollo. ¿Tenemos un problema de comunicación entre Freshdesk y Jira, ya que hemos realizado la configuración necesaria para escalar un ticket al equipo de desarrollo mediante Jira?Tenemos el problema que no podemos @mencionar al equipo de Jira, y a ellos no se dan cuenta cuando agregamos una NOTA PRIVADA, solicitando información del problema, ellos actualizan la fecha de entrega de un Bug, pero a nosotros no se los actualiza en Freshdesk y no los damos cuenta. De momento realizamos el seguimiento con Teams, algo que nos afecta porque no está bien la integración tenemos que usar canales externos, contactamos con soporte de Freshdesk y nos dieron opciones como usar colaborador, integración con freshconnect y Slack, pero no los parecio lo queremos hacer más facil solo usar los canales de freshdesk y Jira.. espero me puedan ayudar o me ayuden como mejorar la comunicación de freshdesk y Jira Buen día Saludos
Within the new Tabular ticket view, the functionality to:1. Sort by custom headers instead of the defaults 2. Sort by multiple headers (e.g Priorty AND Due by)3. Group tickets by custom field value (e.g Section for Overdue, response required etc. Sorting would follow after grouping).
In the Canned Responses, it would be great to have a field where we can interest a description or instructions to our team about when and how to use the response like the picture below. This part is not sent to customers, but only viewable by support staff to get additional context/direction on a specific canned response
Please add the “Ticket Views” button to the tickets : This would accelerate going to another view.Presently : we have to exit the ticket : resulting in listing all tickets in that view : only to change Views Again !?!!!This is ridiculous.This option would also aleviate your servers !
The ability to see all your sent emails or tickets (similar to the sent emails folder in Gmail/etc). This is a basic and indispensable feature. Namely, sometimes we forget to star/watch a ticket from a customer we're corresponding with, and then if we need to easily refer back to it at a later time, we're left unable to find it again! Being able to go to your sent emails would make life much much easier! I waste a lot of time looking for certain emails that get lost in translation... it's very counterproductive, especially for a support agent (like me). Please please add this feature as soon as possible.
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.
