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.
Currently search is only able to search against the title and short description of a catalogue item meaning that all the meat of the description is missed. This should be crawled so it can help return more accurate results to users and reduces the reliance on convoluted product titles and descriptions.
When the amount of scenarios is big like we have, it’s difficult to search among them as they are ordered by name.It would be nice to be able to search the list of scenario automations by name / tags or filter them by availability to a specific shared group
Currently prices for items can only be 0.01 or higher. Where an item is free to a user it would be useful to be able to show that rather than it needing to be inferred through omission which may be confusing. Add a “zero/free” option
Good day everyone,we struggle since months with that and already have a ticket raised twice (one is a feature request now). Now I would like to find out if we’re alone with that problem:We’re using the out of office function to trigger workflows if agents are not available. When we’re facing unplanned absence (sickness, forgot to set their outofoffice) from one of our agents, we’re not able to set a out of office on behalve of them. If tickets of an absened agent receives an update the team does not receive any info about that and a customer will be left high and dry! #noGoThe app Freshdesk Out Of Office Integration | Freshworks Marketplace covers that function but it does work with workflow automations! :-( So we need urgently an option in the standard function, that our teamleads can set the out of office on behalve of agents in their group! Is anyone also missing this option? Looking forward to your upvotes! :-) CheersAndreas
Enable PUT requests for Service Catalog items (e.g. dynamically update pricing of an item based on supplier price changes being flagged upstream, SLAs for out of stock items increasing etc).
Hello,In case there are multiple E-mail mailboxes defined, the agent can choose the correct one in the FROM dropdown, when replying to a ticket.That list is not ordered by name, but by order of date added (I guess). It would be best to have it order by name, so we can search easier and faster. Thanks,Alex
Currently a Service Item can only be assigned to one Category in the Service Catalog. Some items often blur the line between categories (for example, are Apple Earpods a headset or iPhone Accessory?). In order to improve user discovery of catalog items it would be useful for items to be taggable with multiple categories (converting the dropdown to a checkbox list)
When pressing enter in a text property, the value is entered to the property.When pressing enter in a numeric property, the value disappears and is not entered to the property.This is easily observed by typing data in Tags property and pressing enter; the value is added to the ticket as a Tag.Create any numeric field to accept data, type a number in the property and press enter; the value is not added to the ticket, but disappears.
Hi, When using JSON path expressions filter inside the JSON parser node it would great if you could use placeholders so in you can dynamically get data you want. For example: With JIRA Orch app you can get information about a issue including comments. You don’t want all comments to get added to FS, you rather get the new ones. If you could make something like this $.comment.comments[{{ticket.field.placeholder_last_seen_number_of_comments}}:].bodyIt would always give you all new comments added to the issue.
In the service catalog, for certain items such as keyboards or mice, have a quantity that is set by admin so when X amount of users request the item, once it runs out the item will be hidden until it is restocked.
We are using the Knowledgebase heavily and it is really painful regarding the editor/formatting. We also want to publish more comprehensive documents and this is currently not really good to accomplish with the actual knowledgebase. It would be great to get a better editor, Word import, Markdown editor….Would be great to get feature like a professional KB:Create a Stunning Knowledge base with Document360
I often as an Analyst, find myself needing to send reports through FreshDesk Analytics and whilst it’s great that I can arrange a schedule for a PDF and CSV of the raw data to go to any email address I would like. I often wish I could open up the report itself to a collaborator, similar to what we can do with tickets now when we need support from a third party who does not need a full FreshDesk license. I think this feature would be really useful to people who would benefit from being able to see the report natively in Freshdesk where they can hover over to get exact numbers and trend lines for each particular field. As this is much more visual and easier to digest however I find most of my audience do not need a full licence for example senior management.Hope this is an idea others can get behind!Thanks.
When creating a widget, you can set up rules whereby matching URLs get specific articles shown to the user: https://support.freshdesk.com/en/support/solutions/articles/50000001663-showing-specific-solution-articles-based-on-pages-on-your-website-to-provide-contextual-helpThis is great, but it has a limitation. You can specify partial urls, as mentioned in the article, which is good. HOWEVER, if your URLs have dynamic information in the wrong place, there’s no way to match them. For example, let’s suppose that my url structure is as follows:www.example.org/books/<BOOK_ID>/synopsiswww.example.org/books/<BOOK_ID>/reviewswww.example.org/authors/<AUTHOR_ID>/bookswww.example.org/authors/<AUTHOR_ID>/reviewsIf I wanted to use my widget to suggest different articles for each of these URL patterns, I cannot. Creating a rule that looks like this… does not work. It would be REALLY great if it could be made possible to achieve this either with a “*” wildcard, or better, with a regular expression match in the url like /books/(%d+)/synopsis or something, anything like that really! It would make the specified suggested articles feature so much more powerful Thanks!
Sometimes there are instances where we get tickets that we cannot act on until a certain date or after a certain amount of time. I would like to be able to “Snooze” a ticket for a certain amount of time or be able to select a date on a calendar for the ticket to “wake up”This would be different than just changing the status to “Pending” or “awaiting response” since after the set time, the ticket will revert to “Open” status and be visible again in the agent’s list. This will help to hide the tickets from the list only temporarily so that the agent can focus on the tickets that they are currently able to work on. Sleep a ticket for a specified time | Freshworks CommunityThis is the closest thing i could find to my solution, but would require a separate ticket status for each amount of time that you want to snooze (1 day, 2 days, a week, etc) In my testing, i was also able to add a command to email notify the assigned agent to let them know that their ticket is done snoozing and to check their open tickets.
Hi,When we set up an automatic reply to an incoming e-mail, and the receivers contact also use a ticketing system with an auto-reply, Freshdesk creates a new ticket for each auto reply, and so it goes on and on in a loop if you dont manually exclude the email domain in the rule. To use a ticketing system is not unique or distinctive anymore, and it would be nice to stop it before the loop starts between the different ticketing systems.We have already added a rule to prevent these we know about and we are so far skipping 30+ e-mail domain, but we see the use of ticketing systems are increasing and there should be some feature that stops the system to create a new ticket when the e-mails comes from another ticketing system.
Hi,We are using Freshdesk for a short period now and we noticed a very annoying imperfection.It is not possible to trigger automations on actions of collaborators in freshdesk.This means that if a collaborator adds a note (reply on the mail) on a closed ticket the ticket cannot be opened by an automation.We have had several occurrences where a collaborator responded with additional information on a ticket. They got the answer of the agent FYI but decided to reply with additional information. Since the ticket was not changed from closed to another state this information never reached the agent.For sure the collaborator can go the site and post and open the ticket, but in practice this does not happen.A ticket system is used to prevent faults and to make sure that answers are given. Due to this behaviour some of our customers missed additional important information.It is my strong opinion that this behaviour is not as it should be in a ticketing system. Therefore, this suggestion for improvement. To make Freshdesk even better.RegardsHarro
Dear Freshdesk Team, The Freshdesk Solutions tab already offers some functionality to also use it as an internal Knowledge base.We did this by creating a separate portal (One portal for the FAQ and a separate portal for internal use). However, it is still missing some basic functionality, so I would like to share some ideas and feature requests that would make it fully useful for this case: The default agent role should not have the access to create and edit knowledge base articles. As you can not change the restrictions for the default agent role, we have to create a completely new agent role to restrict the access. In general, it does not make much sense that the agent role includes access to edit the Solutions articles and that this can not be restricted. It should be possible to restrict the access to a specific portal. E.g. there is a portal that is synced with the FAQ page, that should be only accessible by the Marketing team/role. The agents should only be able to access and view the second portal that is build for the internal knowledge base. Agents should be able to save internal knowledge base articles as favorites, give feedback or comments, mark them as helpful, etc. Agents should not be able to use internal knowledge base articles in Tickets I hope this ideas are helpful and Freshdesk offers full functionality for an internal knowledge base in the future! :)Best regards
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.
