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.
Many of the pages we pull up in the Helpdesk actually show something useful in the browser tab title, but the Projects do not. This leads to issues with copy/pasting project links because they all show up as a generic title (in our case, “AHC Service Desk” instead of “<project name>”). Seems like low-hanging fruit for a competent dev team. Please fix this, thanks!
When a product launches new information/updates, such as, “Switch to the new Freshservice UI for a cleaner, more delightful experience”, it would be nice that this only displays to the system admins instead of all agents. Our organization must test for accessibility on all UI functions per state-law, and displaying banners to all agents before we ourselves are notified is less than ideal.
Hi,I have some customers that are not happy that it is not possible to control the unsubscribe link in the email outreach functionAt least possible to translate to local language Some outreach email is critical and it should not possible to unsubribe.
I believe this flag what we call in ITSM world is “Needs Attention”, is set when the ticket assigned to you is updated by anybody other than you. That means it will show up in your ticket dashboard as highlighted. And as soon you as an assignee make any changes to this ticket, this flag should be reset to null. And this is how it should work. If it isn’t, it has to be made available. Cheers
Hello, Currently there is no native functionality to require that a Service Item included on a ticket be set to the “Fulfilled” status prior to closing the ticket. Having this available would be helpful for ensuring Agents are properly performing asset fulfillment, and without this feature it is difficult to accurately track inventory. Ideally, it should work similarly to how you can mandate a particular field be filled out prior to changing a property on a ticket using Business Rules. Thanks
BonjourWe at Synerity made a chrome extension that makes it a lot easier to work with Workflow Automations in Freshservice. When creating automations for workflows in Freshservice, it can be annoying to keep adding “/edit” to the URL every time you want to alter or create an automation. This app does that for you. Additionally, this app makes it easier to create web requests by increasing the size of the input field for the payload body when doing PUT, PATCH or POST requests. Increases the size of the email body field. Link to the app:https://chrome.google.com/webstore/detail/freshservice-automation-t/hgbnbhlmljjnchfcpihajfjkfeelaeol?hl=svLink to a short youtube video:https://youtu.be/7tIUBKOXAIw
We received a request via email. It was turned into a ticket in our Freshdesk account. An auto New Ticket Notification email was sent back to the requester. But the requester email address is also linked to a ticket system similar to Freshdesk. They also sent back a new Ticket Notification to us. The notification email subject included the new ticket number in their system. A notification loop happened in this case. Hundreds of tickets were created. We have to disable the auto New Ticket Notification temporarily to break the loop.Could you please make the auto New Ticket Notification function not to send notification email to the same requester email address within a few minutes or an hour for example?
Configure Canned Forms so that the data collected from customer is automatically written in the desired ticket fields.
suggest the implementation of what, from our point of view, would be a helpful and visual way to inform about tickets in which a private note has been added. The idea is to add an additional state for such cases. Similar to New, Overdue, Customer responded, etc. we suggest the label for New info. This would refer to tickets whose last message is a private note. Otherwise, this status remains not visible at a first glance in the Freshdesk board. Below there is an example of what we suggest: Last status is a private note: Ticket shows a New info status: Please evaluate our request and consider its implementation, if it aligns with your workflow.
When working with assets, there are frequent field changes we make when adding, deploying and recovering computers. Although we have work instructions and checklists for agents to follow, steps frequently get missed resulting in a need for periodic review and cleanup.I would love to see Scenario Automations extended to the Asset space so we can build automations of the set of needed changes for the agents to run.
Hi AllA lot of our work involves sending engineers out to site to complete support requests. We would like to be able to automatically create and print off a job/time sheet with a description of the issue and with blank fields (start/finish time, description of work done and customer signature) for the attending engineer to fill in by hand and to keep as proof of work done for billing purposes. This seems to me to be a fairly basic requirement of any service desk software but upon enquiring with support I received fairly uncertain responses. Previous software I have used has offered this plus a mobile app for people to sign using the touchscreen, is there anyway to achieve this using freshdesk whether directly or with an add-on? Hoping I'm just missing something obvious here?
I am requesting an enhancement to Solution Article management.Add additional columns to the Solution article view:Created Date Last Modified Date Ideally, the Solution Article view should have a filter button that allows you to filter in the same manner as the ticket, problem, change, etc. views.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.
