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.
You can view all tags currently in your Freshdesk account from the Tags page in the Admin module; however, there’s no way to export a list of these tags. Seems like such a glaring omission and such an easy one to remedy,When I asked Freshdesk support about exporting all tags currently in my company’s account, here’s the response I received:You could get the tag data by exporting the entire helpdesk data. Go to Admin -> Account -> Account Details >Export data > click on the Export button on this page, to receive the data. The export of the entire helpdesk data, in XML format, will be sent to your registered agent email address of this account. I tried this. It took 13 minutes to receive the download link via email and another 1 minute to download the 65 MB ZPI file. After unzipping, this was what I found:Unfortunately, the export does NOT contain “the entire helpdesk data.” The export includes XML files for...users (aka “contacts”), tickets, companies, groups and solutions...but not for tags. 😕So, what I ended up doing to create my list of tags was to copy each tag one by one from the Tags page in the Admin module and paste to spreadsheet. A tedious bit of work but at least our FD account has only 41 tags. REQUEST 1 of 2 - TAG EXPORTPlease add export functionality on the Tags page in the Admin module. Include the following:tag name tag id count of related tickets count of related contacts count of related solutions date created created byREQUEST 2 of 2 - TAG IMPORTPlease add bulk import functionality to the Tags page in the Admin module that supports the following:create new tags update names of existing tags remove tags
You have ## contacts that need your attention.We’ve started receiving the warning message:“You have X contacts that need your attention.”After investigation, we learned that this appears to be caused by the specific phone number formatting we use for our contacts. It seems that the system recently began enforcing a stricter format, possibly to align with phone integration or third-party telephony standards.Current Behavior:Our team does not use any phone integration features. We typically reference the phone number visually from the Contact Information section and dial it manually. The previous formatting was easier to read and understand at a glance. Example of easy-to-read format:(603) 123-4567 Ext. 123 Example of required (system-compliant) format:+6031234567123 While the latter is technically correct for integrations, it is much less human-friendly and harder to read.Proposed Solutions: Allow custom or multiple acceptable number formats — for instance, permit both human-readable and E.164-compliant versions. Provide an admin or user-level setting to disable or suppress this warning when phone integration is not in use. Optionally detect when phone integration is disabled and automatically relax the validation rules. Benefits: Improves readability for teams that manually dial numbers. Reduces unnecessary alerts or warnings. Provides flexibility for different use cases (integrated vs. non-integrated environments).
Now that looping exists in workflows, it’s time to put it to good use within Freshservice itself: administrators should have the ability to design a service request where a multi-select dropdown can reference a data source such as All Users.I have multiple service items where my clients want the ability to make access requests for multiple users in a single ticket. Right now, that’s inconvenient at best: it would require setting up a dropdown field for every user, or a textbox field where (say) email addresses would be entered line-by-line or as CSV. The first option provides input validation, but you’re effectively capped by the number of discrete fields you design, while the latter has no input validation.Multi-select dropdowns to data sources solve this elegantly. If I can pick multiple users from All Users, I can have “as many as I need” in a single field, and then I can use loop through the array within WFA to provide the access requested. The data is validated because I can only select valid users, the user information can be immediately accessed through whatever reference the array uses, and those references can be fed through the WFA loop to do the job.*Second, I’m building an account reactivation service request for a client. Currently the only condition options to sub-select All Users in a dropdown are Department and Location. It would be very useful to have the ability to define “Is Deactivated” as one of many additional useful conditions for filtering All Users. Some others I can imagine being useful: Is VIP; Is a member of a group; Title includes; email address includes; Tags includes; and Reporting Manager includes. You could do a lot here!
Currently we’re able to sort by a Column in either Ascending or Descending order. However, due to the naming of some of the default statuses, we’re unable to create an order that matches what I’d like.I want newly created “Open” tickets at the top, tickets I am working on “Working” next, then a custom field we have “Escalated”, then Pending, Resolved and Closed.This doesn’t match the options I have available, can we create a custom order (preferred), or rename default statuses with numbers to allow the Ascending/Descending to be configured as I’d like?
I can’t be the only one running into this limitation.While implementing Freshservice for contract management, I created several contracts in Draft status and later realized I needed to introduce an additional contract type. At that point, I discovered there is no way to update the Contract Type on existing draft records.This creates unnecessary rework. In my case, I had to recreate nearly half of the contracts I had already entered—time that could have been avoided if draft records were editable as expected.Suggested improvement:Allow the Contract Type field to be editable while the contract is in Draft status.If others have encountered this, please upvote to help prioritize this enhancement.Thank you,
As we continue to evolve our automator configurations I realized that values must be hard coded for endpoints, etc. It would be nice to have a custom placeholder that is available in the GUI. For example:I have multiple automators that are hitting companyname.com on an API hit. Company is changing all of their endpoints from V1 to V2. I have to go through and try finding all automators that use this API endpoint and update the endpoint location.If I had a custom placeholder table of values or similar, I could find a single value and update it, then the automators would automatically have the new/updated value on next run. This is just one use case, but this could be expanded out to shared folder locations, etc etc and allow for substantially reduced overhead as companies evolve both internally and with their partners.
Allow users to customize the rules that are used for threading emails into tickets. We have a scenario where a reply or forward is sent to a distribution list, but the person who replies is in our org, but is not the requester and is not in the CC lists. Their response creates a new ticket because it fails the existing requester marker check even though the ticket ID is correctly formatted in the subject.It would be nice to have more control over the threading behavior by creating custom rules or overriding the existing rules.
When filling out a PO form, often times the product being ordered may not be in the product catalog. Having a way to do that directly from the PO form with the ability to then choose that new product while creating the PO would be extremely helpful. Currently, when that is needed, you have to cancel out of creating the PO, edit the product catalog (assuming the user has that permission) and then return to creating the PO in order to reference the product in the PO.
Currently only agents can drag and drop files in the attachment box for service requests and incidents in FreshService. It would be nice if that functionality were available through the Requester Portal as well.
Currently if we have a new role where we need to add 50 agents to, the only way we can achieve this today is to go to ALL 50 agents and apply the role 1 by 1. There is no mass way of doing this which is extremely odd to me.Please add ability to do this as soon as possible, this would be a huge time saver for companies that use granular permissions as all companies should. By not having this makes admin jobs an absolute nightmare and makes admins give up, and in return comes poor security.
Some of our people love the board view as it helps visual people work better than a list. Currently the board has all the cards in columns by status. This is ok, but for supervisors and some collaborative teams, we would like the columns to be by agent. And others by category. Allowing the agent to choose the primary sorting/column method would provide lots more flexibility. Thanks.
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.
