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.
At a previous org our security automation tool had an ability to specify a time required on a workflow. From there the service would track runs and you could extract information based on the total over a time period or overall. This could be used as a data point for leadership as well as a way to drive further investment into automations and integrations within the product to solidify the expense involved with FS etc.
Our business has multiple products with relating product portals. A customer may have access to one or multiple portal depending on their purchases products. Each portal’s content is restricted and not publicly visible. Freshdesk currently allows only one custom Contact SSO policy for the entire Freshdesk instance. This requires our customers to login to each portal as they switch between the various products they own. That is a terrible customer experience. As a customer, i should be able to log in once, and then I should be able to switch between the various portals that I have acces to without being prompted to login again, and again, and again. My understanding is that FreshService is currently built to allow multiple contact SSO policies, even down to the portal level. WE need this functionality in the Freshdesk platform.
Custom field properties As of now when we add custom fields to the forms, we get the below properties. In addition to this, it would be great to have additional properties likeHide when <<condition>> Required when <<condition>> This will provide more functionality to the usability of the custom fields. If we extend this to the code/ootb fields, that will be an added advantage. Thanks
We need a wait condition, loop or both for workflow automation. Use case:Creating a user for on prem AD then syncs to Azure on a 30 min schedule. Once the users is in Azure we need to assign a license to the user. Both tasks can be done with current workflow automation with manual intervention.The wait or loop cannot be achieved. and the license is triggers with an supervisor automation that kicks off another workflow automation. We need a wait condition in the workflow automation that can be used to PAUSE the automation for a given period of time, then we could check for the user in azure, if its their continue the workflow, if not loop back to the wait condition.
Whenever assigning user to an asset in “Used By” we need to select the Department of the User. Can we make this automatic to pickup the User’s Department and assign it automatically? Why do we need to do it manualy?
I would like to be able to edit the robots.txt from the support website for seo purposes. Then I can tell crawlers to crawl certain pages, yes/no.
Please can the ability be added to sort tickets by clicking on any column header and sort either ascending or descending.This could be made even cleverer by also keeping the previous sorted column values (i.e. you sort by subject ascending then you click to sort by date opened ascending, it should still keep the sort on subject as ascending as well but show the date opened sort you have applied). This would be easier than using the filter, which I find can be slightly unwieldy at times, and also I still want the view of all tickets, I just want to sort them by different columns than you already can.
Freshdesk subscription doesn’t show in the “All subscriptions” tab in the Neo admin center. So this is difficult to manage the subscription. Could you please develop all products consistently?
Hi!I’d love to see the Workflow Automator be able to prompt the Agent to choose from pre-defined options and then, based on this choice, the flow would continue further.In many cases we don’t want to set up a static automation that relies on current ticket attributes, but want to be more flexible and let the agents choose what happens next.The idea I have is to be able to add a new “Prompt node” in the workflow automator that would display a popup for the agent where they can pick and choose which way the flow would continue.This is just an example draft, but imagine the possibilities:Based on the choice picked in the prompt, you could add ordinary condition nodes that allow you to branch out the automation.These prompts would eliminate the need to create and use unnecessary custom fields we currently need when we need to make a dynamic choice like this, not to mention the necessary business rules to show or hide these custom fields.Let me know what you think.
I want to know if it is possible to link tickets to contract , or add a contract filed in tickets
For years we have had the problem that the customer portal cannot be translated reasonably. We have to change the given texts / contents. The suggestion from support was to do this using JavaScript. That means, I should change the content of each individual element, via JavaScript. This is not only cumbersome but also not possible for all labels and all content, because the elements often have no ID.I don't understand why it is not simply possible to edit a language file.First of all it wouldn't be a big hassle and secondly it would provide maximum flexibility if you as a customer could edit the language file.
I’d like to have multiple ticket reply “drafts.” Example use case: I’m writing a reply to a customer when I realize I need to clarify something with the distributor, who is cc’d. Right now, I copy-paste the reply in progress into another app then delete the text in Freshdesk so I can reply to the distributor. Instead, I’d like to be able to save my customer reply in progress while I send another reply to the distributor.
It would be very helpful if Solutions could have sub-folders. We have an ‘internal only’ Solutions category and it would be incredibly helpful to break this down by section, to reduce clutter, rather than made several ‘INTERNAL -’ categories in the Solutions.
In the Onboarding Module HR puts in the initial form to start the onboard process. Then an email is sent to the Hiring Manager to complete the second part of the form. The ticket is not accessible for anyone until the Hiring Manager submits the second part. We would like FreshService Admins to be able to access the ticket after the HR rep submits their part. Being able to see the ticket or redirect/resend the onboarding email to an alternate recipient would also work.
Would be nice to CC people (requester/other) to really make use of the App Saw previously raised on but no traction
Our company has Hiring Managers and Admins process New User Requests for Onboarding. Currently the only option is to send the second stage onboarding email to the Hiring Manager. We would like to be able to add an Alternate contact (preferably from a custom object) for all Onboarding tickets. Not having this ability is keeping us from utilizing the Onboarding module as a whole.
As an agent in Freshservice, if I submit an incident and a different team/agent is addressing my request, I have no way to reply to the agent except using the forward option which doesn’t fill out the To: or CC: fields.If they send me a reply it is addressed to me, but if I hit reply, it is also addressed to me. I can’t reply in the end-user portal because opening the ticket there directs me to the agent portal for the ticket. There is no option to reply to the agent’s reply, like with a private note.Please allow agents to reply as a requester to tickets that they have open.
Currently we have the option to either send an update/info email to our customers or send no email.But some customers do not like to be ‘spammed’ with emails about their tickets etc. Others on the other hand want to be informed about every step in the proces.Is it possible to have an option in the contact record for receiving emails or not. Not needed to have an option for every single email but just for receiving or not receiving.Would be really greatly appreciated by our customers!
Please allow us to use and save views with wildcards for tickets and assets.Why? use case:We have Dell as our main assets Their models are called Dell Precision 5510, 5520, 5530, 5540, 7510, 7520, 7530 and so on I need a view there I can see all Precisions and maybe 55xx the filter would look like Product = “Precision 55*”This would make the product much more mature regarding asset managementCurrently I need to have about 30 different views and if a new model appears I need to create another view… This is not scalable...
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.
