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.
Can we get the ability to show fields that are already captured by the application as placeholders for email responses in our ticket list view? Being able to see {{ticket.requester.phone}} as a column or even just when doing a mouseover of the requester would be a big convenience.
Hi everyone,I’m working with multiple service teams on CRM and workflow automation, and wanted to share some technical insights from my experience with GoHighLevel Automation & CRM that may benefit others here.1. Unified Automation Logic Improves ReliabilityWhen building automations across lead capture, follow-up, pipeline movement, and revenue tracking, keeping your logic inside one platform (rather than splitting it across multiple connectors) significantly reduces failure points. Consistent identifiers (like standardized email and phone fields) help ensure triggers fire reliably.2. Explicit Workflow Transitions MatterIn complex service workflows, implicit transitions often behave differently under high load or after changes. Wherever possible, explicitly define status changes, ownership assignments, and trigger conditions in your automation logic rather than relying on inferred behavior. This makes testing and validation more predictable.3. Validate With Real Data ScenariosTesting with synthetic or “happy path” data seldom reveals edge cases. Build test cases that mirror real user behavior — incomplete records, duplicate submissions, or rapid repeated actions — before deploying automations live.4. Keep Rule Logic Simple Before ScalingHeavy branching logic and conditional rules increase maintenance overhead and risk unknown side effects during platform updates. If a rule doesn’t directly support a clear outcome (e.g., conversion, retention, hand-off), consider deferring it until there’s measurable value.I’ve applied these principles at leadsflex while optimizing automated CRM processes, and it has noticeably improved lead responsiveness and pipeline accuracy. Looking forward to hearing how others are handling similar challenges with Freshworks tools.
Hi, we would like to create a report that shows the total tickets by category/sub-category/average resolution time in Bhrs ranked by top 10. Right now, I can only run a ranked report by either category or sub-category but not by category and sub-category (widget filter rank order). I heard on January’s Freshworks Analytics presentation that this feature can be implemented if requested, we are interested in having this implemented. Please let us know what we need to do to have this implemented. ThanksJorge Torresjorgetorres@sanmar.com
We have several Workflows set up to send reminders to Agents to work on Tickets. We’d like to do the same for Project Tasks, but the Projects module isn’t available in the Workflows. Please add this functionality. Thanks!
Will Freshservice provide any ability to track analytics for the First Acknowledged by so we can include this in monthly/quarterly reports? We would love to be able to track time to acknowledge as well as get an average like what is currently available for the First Response. This metric would be a great help in providing data for the acknowledgement of tickets and the elapsed time of the entry of the first public reply.Thank you.
An enhancement that would significantly improve incident communication is the ability to use a shared service model across Incidents, Major Incidents, and the Status Page. We’re looking for a way to better align how services are defined and used across Incidents, Major Incidents, and the Status Page in Freshservice. Today, services defined for incident impact and major incident workflows are not linkable to Status Page services, requiring teams to manually recreate and maintain separate service lists. This prevents incident impact (e.g., a critical platform like Kubernetes going down) from automatically triggering major incidents and updating the Status Page with the correct impacted services. Enhancing this feature to support a shared service model would improve ITSM workflows by enabling automated incident impact communications, reducing manual maintenance, and ensuring consistent service visibility across incident management and customer-facing status updates.
I am interested in a report that breaks down the number of tickets that are assigned to a specific agent and are then are re-assigned to a different agent and/or group. The purpose of this is potential training needs for the original agent or there needs to be better explanation on the reason why it has been re-assigned.There is a report that shows the movement of a ticket from one agent to another but it is too general and doesn’t fit the brief above. From conversations with Freshdesk direct this report isn’t possible yet. Would this be something that other would find beneficial?
I would like to see the ability to put a ticket in pending BUT for someone who is CCd on the ticket. I have come across too many times where the person who put the ticket in is not who we are waiting on, but we need a response from someone who is CCd on the ticket before that ticket can move forward. In the past we have sometimes been able to edit the ticket details and change the requester to the person CCd, then put it in pending. However this just gives that person incentive to not answer the question and have it close automatically. If there is already a way to do this please let me know. Thank you!
The to-do list on the Freshdesk dashboard is amazing to use, however, currently only 2 items are visible. It would be great if the section could be bigger so more items are visible. In addition the newest created item is always shown at the top of the list, it would make sense to either have a filter on in which order they should be displayed. Or the item that was added last should be added at the bottom of the list.
Our Agents are supposed to provide a Summary for each ticket:Solutions to assist with this would be:Have a filter with the Summary field. Include Summary Field as option in Analytics Make the Summary Field Mandatory.
Hi.Currently, we have a curated report called Ticket Lifecycle.In the Ticket-wise Split widget, for instance, you can have a view of how long (both, in Calendar and in Business hours) a ticket stayed in a status, in a group or assigned to an agent.That is actually pretty good. But it is missing something very important for the ticket lifecycle itself: The timestamp of any of that points changed.I’ll use a real example for elaborating this.This specific ticket has passed several status changes, group changes and agent changes:The correct order of events was:Ticket created with status “Sin Datos” (Without Data). Data was filled, so it changed to status Open. Auto-assignment assigned it a group and an agent (and was kept in status Open). I changed the group and assigned it to myself, and set it to status “En Proceso” (In process). I worked on it and sent a reply to customer asking for further information, setting it on status “Waiting on Customer”. Customer replied back with a response, changing the ticket to status Open. The information of how long a ticket stayed in a status | group | agent combination is perfect, but it is missing the timestamp of such events, making it impossible to view in a streamlined way the lifecycle of this (or any) ticket, as you can’t currently have the proper sorting of those events.That example Report / Data should be shown in this way: That’s the chronological order of the events, as seen on Ticket Activities, If having a timestamp column in such report, we could sort that data as expected. I tried / thought of creating a custom object in order to store that data and then retrieve it from Analytics, but Custom Objects are basically readable-only in Workflows and we cannot write data onto them from Workflows. This is very much needed for auditing. This applies for FreshDesk and FreshService (and I guess all products that uses Analytics). Hope this gets considered, approved, developed and delivered soon. Elvis.
Make it an option to logon via SSO to the status page, making it possible without having to verify logon every time you close a browser window...
Right now, Time Trigger Automations don’t have the ability to look at agent status - please make this happen! The screenshot included shows the functionality that currently exists on Ticket Update Automations; we really need this on Time Triggers: Not having this functionality is really causing big issues: We have time triggers that reopen tickets. BUT since those tickets have no way to check availability, they are left open in the name of an agent who might be on a two week vacation. Currently, our Out of Office settings will automatically unassign an unavailable agent. This works beautifully for replies, but that Ticket Update rule can’t affect a ticket reopened by a Time Trigger Automation because the Ticket Update Automations are only based on Agent and Requester actions and this awkward-not helpful sampling of possible system actions.
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.
