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.
It would be helpful (for testing especially) to be able to trigger an automation you’ve created directly from the service request or ticket kind of like you can with the scenarios. This would make testing your automation easier and would be a good alternative for certain automations where the available triggers don’t accommodate your use case.
You should be able to have a search box on the product page
When Printing a ticket, it shows all ticket fields - whether they are visible or not on the ticket.We have lots of ticket fields that are controlled by sections.For example, we have a ticket field called Ticket Form.If Ticket Form = abc then show 10 fieldsIf Ticket Form = def then show 10 different fields If Ticket form = ghi then show another 10 different fieldsWhen printing a ticket ALL fields are shown.We used a Ticket Form to control ticket fields the end user should not be able to see but PRint shows everything.This should honour the fields that ARE visible versus what is hidden
This has already been raised here but no movement for 9 years: Need to be able to export search results. The export on the Ticket View page is not the same as being able to export search results. Also having the ability to search the drop down filters is great BUT it would be better if every field was available for searching in.In the search bar you should be able to enter a search query like other helpdesks do. Is this possible?For example:Created = Today AND Status = Open AND Agent in (John Smith, Jane Michaels and so on)
There seems to be no placeholder for emails for threads to address to the person being tagged. At the moment we just address the email as Hello, ‘You have been tagged….’ but it seems very informal. There should be a way to have the template pull in tagged name as a placeholder so it can be addressed correctly.
As well as our clients set up as products, we also have our internal IT system set up as a product. If one of our agents has an issue with a computer for example, they will submit a ticket to the IT team. When a ticket is closed, the satisfaction email is sent but it does not get shown as the requester is an agent. We want agents to receive the satisfaction email too.
Would be nice to be able to brand the agent activation email (not the users). Scenario - we have external clients log into our helpdesk as agents. When they receive the email it doesn’t show our name anywhere at all except the person who created that agent.Our clients were expecting an email from us and as it wasn’t assumed it was spam. Having the ability to brand the email would make much more sense
Hi,It would be super helpful to be able to filter tickets using custom fields (in addition to the standard, default fields).Many Thanks,Alan
Bonjour,Pouvons nous faire que le délai de traitement soit recalculé à la date de ré-ouverture du billet.Si un ticket est cloturé, puis ré-ouvert suite à une réponse client, que la date d'échéance se recalcule à partir de la date de ré-ouverture du ticket.Merci
Bonjour,Pouvons nous faire que le délai de traitement se recalcule a la date de ré-ouverture du ticket.Si un ticket est cloturé, puis ré-ouvert suite à une réponse client, que la date d’échéance se recalcule à partir de la date de ré-ouverture du ticket.Merci
We have a bunch of assets that were created before we deployed our HR workspace, and now we would like to move those to the HR workspace. The only problem is there is no option to do this, and the only way to get those assets to the HR workspace is to delete and rebuild them. Tedious work to say the least. Can we please have an option to update the Asset workspace? Thanks!
For certain requests we would like to use special wording on the approval request. Currently this means we need to maintain a separate document with that text to paste into the Approval request. We’d love to either have a catalog of Approval messages to select from (similar to the Canned Responses section) or be able to access the Canned Responses section from the Approval menu.
Activities does not show audit of what field was before change, only what it has been changed.It would be great to show what the field was incase the field was changed incorrectly.
Product_id is not a placeholder that can be used in automationScenarioWe cannot allow users to amend the group and product on the ticket. We have in place the app that says:if product = xx then group can only show xx if group = xx then product can only show xxThis works great locking it down however agents can choose ‘--’ and both options and all options become available.I have added automation when the ticket is raised to populate custom field ‘group_id’ with the actual group_id, then a further automation if the group is changed from any to any change the group back to the custom group_id field and this works perfectHowever product_id does not have a placeholder so this does not work for Products. I end up having a group and a product different from each other causing issues.If product_id was a placeholder the automation would work perfect.I’m actually surprised that not every field via webhook can be manipulated regardless if a placeholder exists or not.
The ability to stop closed tickets being edited.In other helpdesks Closed status prevents any changes being made to any ticket field.Although the apps help reduce the fields that can be edited, you are unable to prevent all fields being edited.
We have ticket fields that go across several sections. It would be good to have the ability to make one section requires the field to be mandatory and the other section does not require. For exampleStandard Form - Section 1Reason for closure --MandatoryAdhoc Form - Section 2Reason for closure --Not Mandatory At the moment it is either mandatory everywhere or nowhere
The default priority status names are currently:Urgent High Medium LowWe use a quadrant system to label how important / urgent our priorities are, and would like to have our tickets match. Can we please be able to name the priority status levels? Also, all tickets currently default to “Low” priority. It would be nice to be able to set our own default status.
automatically approving people with whitelisted domains is greatHowever, adding automatic activations based on contacts that are added to companies with specific filter requirements would also be helpful.
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.
