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.
A majority of my staff and myself find the Board view to be the most efficient view to work through tickets quickly. One enhancement for Board view would be to add the details of service requests so you can triage at a glance. Right now it simply says the title of the service catalog item. (See screenshot)Board View of Service RequestHere’s a mock-up of what it could look like….
This is a frustrating one for us, we would love if we could send outbound emails that become tickets, without the first response timer glaring at us. If we have an 8hr SLA on first response, and we send an email to someone who contacts us back the following day, we have SLA violations. We need this disabled, or preferably in the case of outbound communication - the timer to start when the customer replies to us for the first time. We cannot clear it with public notes, and support is firm that everything is operating as expected. Since we have not responded to the customer yet (even though we are the initiators w/outbound email). (our ticket w/them is #15556397). Public notes, replies, etc - nothing will resolve this until they email us back and we reply.
Hi, I am looking for an option to be able to sort my saved ticket filters/views either alphabetically or custom.Can this be made possible?
Currently when ‘watching’ tickets you get notified when an action happens on that ticket which is great, however it would be really useful to get a list view of tickets on the left hand side of all tickets you’re currently ‘watching’ whether they be open or resolved/closed. I often watch a ticket and yes get a notification when something happens on it but once it’s cleared it moves further down the list of notifications and gets lost and I often would like to go back to the ticket but don’t know the number to search for.
Currently, the filter options within the Calendar are only available when you search for Changes. Ideally, the filtering can be done also for all other parent types: Tickets, Problems, Tasks etc.
Hello all,Short of exporting a list of knowledge base articles and managing through Excel, is there a more automated way (or app), which allows a review cycle to be applied to Freshdesk knowledge base articles? For example, if you can schedule a bi-annual review for all articles based on the last modified date?Just trying to streamline an otherwise very dull and manual process… Thanks,Melissa
Hello, I would love the possibility for uses to add their assigned assets ,just on conditions the assignee is the requester !(please if that is already possible please guide me )
On the ticket creation page, you can only use the ‘Templates’ in order to define information that should have to be pre-filled in the ticket creation fields.We put a qualification/classification of the incidents system in place based on a dropdown (3 levels) menu, we named it ‘Triplets’. You can for example classify an incident as being an ‘POS Sytem / NewPOS / Error’ issue. What we would like to achieve, and what is already feasible and in place in other ticketing tools, is that the Description field of the ticket is dynamically adapted based on the incident qualification values that are chosen. I mean by this that if we choose for the above triplet, then the Description field who pre-fill itself with, for example: # of the POS system: Error displayed on the system: Has the system been rebooted ? Are all peripherals correctly connected ? What was the trigger of the error and how can it be reproduced ?In short, when we choose a classification for the incident, the system would automatically update the description field with the information our agents should have to ask to the requester in order to log a ticket containing the required minimum information. In a large company, with hundreds of different systems and softwares, working with predefined templates for this is just not manageable.
Add in a help/descriptive text value for custom fields in the Service Catalogue to guide the user on how to answer the question asked.
I have been building service requests for my company and there are some instances where it would be helpful to have repeating items in the service request. Here’s a use-case I ran across.I’d like to create a template for setting up network communication between one or more boxes. I have a textbox for the source & destination, but if they need more than a single port for connectivity, it would be great if they could click a plus sign and repeat the same thing over and over again until they have all of the ports they needed. Instead, I end up with a large textbox for them to spell everything out in - the problem is that not everybody uses the same format and it’s unrealistic to expect them to put in a new SR for each port/protocol needed.Almost like an excel table, how you can simply click on the plus symbol to add a new row - you have what you want your table to look like, just add another object without having to put in an entirely new SR.I mocked up something below that I think would be great -- this is just an idea, but it would help me from having to create additional SRs that can accommodate bulk requests.
Currently filtering tickets is done by selecting attributes that match, and results are shown. It would be handy if we could also incorporate filtering for attributes that EXCLUDE certain parameters (ie: status, tags, etc). Maybe allow us to place a (-) in front of the attribute.
Hi, would be nice if you can implement small indicator that any note is added to the ticket. Sometime ticket is moving between workspaces and teams. Information about private note added to ticket on listing view would be perfect. It would be a instant information that you should check the note first. Those indicator can be also value for different information instantly accessible for agents like (new message from requester is waiting, tasks added to the tickets and how many of them, etc.) It can be just an icon with count number.
We would love to see the ability to clone a task. Specifically in the Rel and Tickets sections.We often have work where we want several agents to perform the same activity (testing a release, perfoming inventory, update something at their locations, etc). Currently we open track this by creating a Rel or SR ticket with tasks for each agent so we can easily see who has complete and who has not. Without the Clone option, this is unnecessarily tedious. We’d love to create the ticket, add a single task with detailed instructions then simply clone the task for each agent involved.
Hi everyone,I was wondering if other people like us at zooplus feel that it would be a great addition to have canned responses added to scenario automations. In our case, this would help us improve efficiency, EX but also the quality of data we collect. We’d like the agent to reply to the customer and log the tickets with very low efforts in only a few clicks.What do you think?
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.
