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.
Hi,I would like to formally submit a feature request to update the tab names when visiting admin settings as we are constantly jumping around to different tabs within different workspaces. Examples below. Note how "Custom Objects" is the only one that currently identifies the page on the tab, however, we have no way of knowing which workspace it is within by tab name. Custom Objects current tab name: "Custom Objects | Admin | Helpdesk"Custom Objects proposed tab name: "Custom Objects : [WS]" example "Custom Objects : Global" & "Custom Objects : IT" Also, note how custom objects is the only tab that uses a pipe separation vs a column separation like the others. Most of the other pages just show "Admin : Helpdesk". Within the image below, I put the recommended tab naming convention. The current naming convention is an absolute nightmare for admins in my opinion.
On the tickets table view, you can only sort the tickets on a few columns, like date created, priority and status.But it would help a lot if I was able to sort on any column, including columns from custom fields I've added.For my situation; I've created a custom date field 'Customer reaction expected date’. If I know a customer won't be able to look at his case this week, I use this field set a date in the future. When I'm able to sort on this date, I can see exactly which cases I need to work on today and don't have to bother with cases due for next week (or tomorrow)
We would like more options for resolution generator. One small, but major blocker for some agents is that it is querying private notes into resolution notes and we want private notes kept out of resolution notes.
Looking to be able to include more in the Analytics part of Freshdesk. Ticket Description field and any of the Ticket Body/Content (such as the conversations between requestor and agent). By doing so, we feel it will benefit our teams with training and finding what the root causes to the tickets are.
There is a need for a French-Canadian language pack to comply with Quebec bill 96
We use Amazon Business to procure consumables and low cost peripherals (e.g., labels, keyboards, mice, USB drives, etc.).We’ve published these as Service Catalog items in Freshservice. Depending on the cost of the item, it could go through an approval process.After the Service Request is approved, someone from the Team currently places the order manually in Amazon Business.It would be great to have a native integration or an App available in the Marketplace to achieve this. The APIs and requirements from Amazon are well documented (https://business.amazon.com/en/solutions/systems-integration/punchout). Some work would need to occur within the Service Catalog items to ensure you’re including the ASIN, and other mandatory fields that Amazon needs to collect as well as the correct meta data to accept from Amazon Business to update the service request with the order status automatically.I believe this could also be achieved if you use Microsoft Power Automate, but would need development resources to maintain and support.
On many of our Service Request types we have date fields the customer completes. In some instances these fields indicate when work can start or when it must be completed by. We are looking for a way to leverage workflows to set the due date of tickets and tasks on those tickets based on the customer date field.ex: Conference Setup request form asks the customer to specify start and end date of their event.Tasks will be assigned to the agent for setup and for equipment breakdown. The due dates should be possible to set via workflow that pulls the due dates from those fields on the Service Request as well as sets the due date for the entire ticket to the end date of the event.
I want to be able to monitor live chats of other users and customers. For example, I'm a manager and want to monitor how Joe is doing handling customer questions. Joe is using Live Agent to chat with a customer. Is there a way to setup Live Agent so that a manager can view the live chats of their subordinates?
Hi guys :)By implementing a workflow automation, we were able to enforce the requirement for resolution notes. The workflow functions through an IF statement that checks the length of the added resolution notes. If the length is zero, indicating that no notes were provided, the ticket status is automatically changed from "Resolved" to "Pending." Additionally, a private note is appended to the ticket, reminding the user to provide the necessary resolution details. In this case, workflow will only check is the resolution notes empty. If you want to force agents to make it longer than X characters, you can just adjust the condition in IF function. You can also build the IF function directly in Condition window by using "Build Expression" window. if(length('{{ticket.resolution_notes}}')==0,1,0)
We’re exploring the new XLA option. One major metric we don’t see is “ticket assigned within (a specific period of time).” From a customer perspective, knowing your ticket has been assigned to an agent (and not just had a first response stating we’ve seen your ticket and assigned it to a queue) is a metric we think plays into XLA.
analyzed the number of escalating tickets and whether it comes from a group or a user in analitycs.A gender metric: group that escalates
Currently, when replying to a ticket in the Freshdesk mobile app, the reply screen indicates that you are replying to the ticket creator but does not indicate whether any additional recipients are CC’d or BCC’d on the ticket. This can make it difficult to know exactly who will receive a response before it is sent.Adding a visible indicator when CC or BCC recipients are present would make mobile ticket responses much clearer and help prevent messages from being unintentionally sent to additional parties.
Get the latest schedule, date, venue, competition format, and viewing information for the Asian Games 2026 Equestrian Jumping Individual Final on October 4 at JRA Equestrian Park, Tokyo.
At the moment there are two options on how to give access to tickets:"Logged in users" or "Anyone with a public ticket URL” In the case of logged in users only the requester on the ticket gets access. We however work mainly B2B and often more than one person needs access to the ticket. Giving a person access to all tickets in the organization is often too much, access with a public URL isn't safe enough for our data. We want to stimulate collaboration without overrunning them with tickets. What we see at our suppliers and their ticket systems is that a person in the CC with an authenticated account can look into the full ticket after logging in. Anyone else who would like this feature?
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.
