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.
We’re currently implementing the offboarding process into our Freshservice environment, and it’s apparent that the module is quite limited.Firstly, when the parent ticket is created, step 3 should allow you to create, either Child tickets or Tasks (or both). Currently, the child tickets created are per software assigned to the user, this should be the same logic for Tasks.Secondly, from the parent ticket, using either Related Tickets, or the Tasks option, you should be able to assign them to an agent from that screen, and you should be able to resolve them from that screen also, without the need to open each one and edit.Thirdly, when the child ticket/task is resolved, this should automatically unassign the associated asset.
Currently there are only a few fields from the requester that we can include in approvals, it would be very helpful to be able to include fields such as Title, Department, and even custom fields (for my specific use case, I’m wanting to include a field we call WorkerType that tells if a user is an employee or contractor).
In our efforts to assist customers, we've observed that the range of inquiries we receive can be categorized into specific types, which ideally should correlate with a finite set of predefined responses.Although our current system allows us to search for these canned responses, enhancing the link between the type of ticket and the corresponding canned response would streamline our process.Introducing a feature such as 'canned response typing' could be beneficial. This would ensure that using a canned response would automatically set the ticket type (and perhaps influence other fields).Take for instance, a customer contacting us regarding a missing order.We have two scenarios: If the ticket has already been classified under the 'missing order' type, this would prompt the canned response system to prioritize relevant responses. If the ticket hasn't been assigned a type yet, utilizing a canned response should ideally set the ticket to the corresponding type or at least propose the option to do so. The said categorization should be integrated into both the exported data and the API.For more details, refer to: https://developers.freshdesk.com/api/#canned-responses
Hi, Every time after sending a canned response I need to go and set various properties like the tag for example. My suggestion is to add ticket properties to canned responses so that if the properties have a value then these properties are assigned to a ticket automatically when the text is inserted. Thank you
Currently, the Announcement only supports one language, which can be a limitation for users who speak different languages.
We can setup Multiple CAB groups for approval, but we cannot get one person from each group to approve when we send them out one at a time. What happens is that only one person from ALL the groups needs to approve (which is not correct) Can we have a feature that enables us to send out approvals to multiple CAB groups where each group only needs one approval. This enables us to have a backup approver of a particular area in case someone is on leave. Example send all at once. Security CAB Group (only one needs to approve) Security person 1 Security person 2 Infrastructure CAB Group (only one needs to approve) Infrastructure person 1 Infrastructure person 2 Governance CAB Group (only one needs to approve) Governance person 1 Governance person 2 Service Delivery CAB Group (only one needs to approve) Service Delivery person 1 Service Delivery person 2
The inability to automatically remove Tags from tickets using Automation is severely limiting. I am aware of the API work around users have devised, but API calls take time to execute and occur outside of the Automation itself. This means that a single Ticket Update event cannot both remove a tag AND run an Automation which is looking for tickets that don’t have the same tag. A second update even must occur.Use Cases; Too many to list, but here are two examples;1. Say you have multiple different auto-replies which are sent to Requesters of New tickets, depending on which department the ticket will be routed to. Multiple times per year, your company shuts down for Holidays. You want to send a special auto-reply to let Requesters know that you are closed and will get back to them when you reopen, but you don’t want to also send them the regular auto-replies.To solve this issue, you make the regular auto-replies not run if a Ticket has the “Holiday_Time” tag. This automation needs to run on both Creation, and every time a Requester updates the ticket while you are on Holiday.When your company returns from Vacation, you disable the automation adding the “Holiday_Time” tag and replace it with an Automation that removes the “Holiday_Time” tag from all tickets when they are updated by anyone.To expand on the above, the auto-replies in question don’t apply to just Ticket Creation. In Zendesk we previously used a setup where an Auto-Reply would be sent-out if a Ticket was moved to a different Department.Further more, the above Holiday Time method works up until a ticket is open for multiple Holidays. In our case, some customers take 6+ months to respond to an invoice. Meaning a single ticket can easily cross multiple Holidays. Currently, it is outright impossible to implement the above without using the API Workaround, but that is inherently inconsistent. 2. Say you have a sorting rule that pushes tickets to a specific User when a variety of different conditions are met. The possible combinations of conditions required to prompt the auto-assign are too complex for a single Automation, requiring multiple automations which all add the same Tag. Then downstream the auto-assign automation looks for the existence of this tag and assigns the ticket.Now we have an issue, either the ticket will be re-assigned every time a ticket with the Tag is updated, or this Auto-Assign can only ever run ONCE for a single ticket. This makes complex ticket routing and escalation setup nearly impossible to implement.Ticket Creation automation suffers the most from this limitation, since not even the API workaround can help. As mentioned above, a second update event is required to trigger Automations looking for Tickets without the tag being removed.
I’m managing multiple projects in FreshService and in many occasion, a task depends from another task that is not in the same project. If not already (didn’t find how), it would be very useful to have the ability to set a task predecessor across different projects.
Our change management procedure requires that the assigned change agent not render a request for change approval. The procedure actually has three levels of review to it (peer, leadership, CAB). We will have occasions where a leadership member may be the change agent so should not be self approving changes. The leadership CA contains 10 members, so I would need 10 different conditions on a workflow to handle checking the change agent, then sending the list over. If there was some ability to restrict the list based on the change agent that would be great.I also looked into doing this via Powershell script (to cancel the approval immediately after send if it matches) but there is no ability to view the requested approvers on a change request it appears (though it does exist for Tickets).
Want to make fields mandatory when other fields are selected.Business CaseWe have a custom field called Hold Party which is a dropdown with various parties to say when a ticket is put On Hold, who it is on hold with.When we mark it as On Hold, there should be a way to make the Hold Party mandatory in this case.Short term, a Private Note/email can be sent but it doesn’t enforce it.Thanks
What I completely miss in Asset Management are queries by asset type.For example, "Show me all notebooks that can be updated to Windows 11" or "List all software packages that are not compatible with Windows 11" or "Show me all software packages for which a security update exists".That would be a great help in our daily business.
I was searching for an option to hide or delete these default views, because these views are “polluting” the tab unnecessarily, since we did custom ones.
Recently our Microsoft mailbox had an issue of not being able to support the outbound ticket notifications.On certain days we are exceeding the limit of 10k emails in 24 hours. Our user base is this large and we have this many teams working in Freshservice. As i worked with Fresh support to mend our issues it came to our attention that Freshservice does not allow us to condition emails currently in the ways we need.Ex: If group is (A) skip ALL email notifications. or If group is (A) skip agent notifications.We only have the ability to skip all new email notifications and not skip the updates and/or agent actions.If we could condition emails better rather than an all off/on toggle this would provide relief for us.
Currently, we lack the ability to display “My Group Tasks” on a dashboard. This provides a pain point in our system that denies us from being able to filter/display tasks in the same manner that tickets are.The recent release of ticket filtering enhancement is a success for our community, and I would like to see a continued push for equal abilities across all the Freshservice modules for the user base.
Currently, we do not utilize ANY of the out of box roles (Admin or Agent) that Freshservice provides. Without the ability to edit them they do not fit our business needs and we have made our own custom roles instead.For quality of life, can we hide/delete and or gain the ability to edit these roles? I understand the need for Fresh Support to be able to ask for certain permissions to provide assistance during support, so if a higher-level role needs to stay that is ok. But the rest, just sit there and take up unnecessary space in our tool.
Currently our business has grown into the different workspace environments. Each workspace deals with different categories and therefore does not need to see the cross contamination of topics not their own.The idea is to move category from a Global Form field into the workspace level, so it can be conditioned to show per the workspace you are actioning in. This can also be accomplished by giving us the ability to make a business rule conditioned from the workspace, but moving the category to workspace level would let us declutter the list so that Global category isnt a mile long. Also, please bring back the old Category UI features. Sorting and editing cat, sub-cat and items are a nightmare right now without the bulk edit features.
Hi, community.Currently when the user wants to associate an asset with a ticket we can either let him do so or restrict asset association. In case the user is able to associate assets we can either let heim view all the assets or only the assets assigned to him.What would be great is to be able to configure the custom asset lists, based on:asset state asset location asset “Managed by” team etcThe use cases may be following:an employee of a store should be able to open a ticket for some equipment in this store users should not be able to open tickets for the assets that are in the “In repair” or “Missing” states users should not be able to open tickets for the assets that are under maintenance activities right now.
Imagine a scenario where users receive timely notifications about warnings, outages, and other critical information through attention-grabbing pop-up banner. With this feature, users can easily stay informed and take necessary actions, all within the support portal environment. Example
The generate email is now dependedent on the language settings of the agent.We use internally English as our app. But we are Ducth speaking, have German, French and Spanish speaking clients that now get all email back in English when we use the “generate email” functionality. It makes more sense that the “generate email automatically detects the lamguage or that it is related to the languages in the portal
I recently setup a workflow which has requirements that a set of tasks are completed (order is not specific) prior to a subsequent set of tasks being generated. The task automator only looks at the specific task that triggered, and the ticket automator doesnt give any ability to look at the number of tasks that are not done. Something like this would be a huge help to allowing a process to happen when predecessor steps are completed.
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.
