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.
In our organization we have created an “on hold” status. We usually use this or the “pending” status for tickets we are not actively working on or need to wait to resolve on a future date. It’d be great to have the ability to schedule the “on hold” or “pending” status tickets to re-open on a specific date or time. Rather than needing to manually needing to go in and adjust the status.
Tasks which are created via workflow can only have fixed due dates from a drop down.Please add the possibility to choose the Due Date dynamically - for example to be set to the due date of the ticket itself.I know it can be done via webhook, but it would be so much more convenient in the GUI.
When I merge two tickets, it would be helpful for the surviving ticket to have all the users (from both tickets) as cc’s. Currently, I had to add a few users as BCCs (the CC field was locked)
It’d be nice to have the ability to update the category, sub-category, and item from the ticket list screen. Preferably without using the bulk update option. I’m thinking something similar to how you can update / change the status or priority fields via the drop down menu on the ticket list screen.
I’d like to easily move a company to-do to one of the company’s contacts. Example:Company to-do:Updated company to-do:My current workaround is to copy the company to-do, delete it, and paste it into a new to-do for the contact.
Hi,Utilizing service request, it would greatly enhance our product adoption if the service request data could be exported independently, rather than requiring the submission of a support ticket on every occasion as advised here. We eagerly expecting this enhancement in the future.Thank you.
Currently, you can only set up 2 levels when creating the Service Requests. The Category as level 1 and one next level. This makes the overview of available SRs very unclear and does not allow any good reporting based on the SRs. Therefore, it is important to have at least 4 levels. This will bring clarity for all users and will allow better follow up, automation and reporting.
This was first brought up 2 years ago, please read the thread:https://community.freshworks.com/contacts-companies-11405/adding-fields-columns-to-contacts-view-23332?postid=88499#post88499We can’t view existing data. We can’t customize which columns/data is being shown. This UX is broken.
We have several workflows which generate tasks as part of a service item request. The problem with this is that if a task is created on a Friday late, but it’s due in 3 days this really only gives that team part of a working day (if no holiday on Monday) before the task goes into overdue. Being able to have task due dates be set via business days instead of calendar days would allow for a more accurate portrayal of timeliness of task completion.
As agents we should be able to print out a solution article. Seems pretty basic, especially if it is available on the support site side. Currently when trying to print a support article from the agent site, it is so poorly formatted as to be useless. And when printing an article from the support site, the text is miniscule, unreadable. Are improvements in the works? Thanks,Joe
Currently, the Service Requests can only be created in English, but since Carrefour is based in Belgium where France and Dutch are crucial, it is crucial to also have them in French and Dutch.
We are using FS automators to handle almost all of our access management. Instead of having hundreds of SC items, we went for a single SC item that has a conditional field where the application is the top layer, and the type of access for that app is the second. This creates manual work every time we add/remove an app from the environment, whereas if I was able to use the inventory to populate this, I wouldn’t need to hand edit (and sort!) the SC item every time a new app is added.
Would it be possible to separate the Create and Edit assets rights ? They’re actually bundled in the Agent roles: But we don’t want that agents allowed to edit assets also have the possibility to create assets.While agents have to be able to adapt the location, state or other fields of an asset, having that possibility to create assets also allows them to import a huge amount of assets from a CSV and potentially import a lot of unwanted records in the DB.Creation and edition of assets should really have to be separated rights.
We remark that there is no Export possibility under the Locations module. We have to deal with a huge number of Locations (about 700) and for us, only being able to import them without having any possibility to Export them is a not an efficient way to keep our Locations up to date. Could you please add the possiblity to also export Locations from freshservice ?
For incidents and service requests, you can configure automators to send mails from a custom specific mail address (when you have several addresses configured in your freshservice instance). This seems not to be possible with the changes automators.We would like to send those notifications from another address than the standard address configured in our instance as we have a dedicated mailbox for change management.Is it possible to add that feature in the changes management automators (feature request) ?
Would it be possible to add the possibility to configure a daily scheduled automator to run several times during the day.Now, to achieve this, we have to clone the same automator several times and set each to run at different hours.Being able to set several launch hours in one automator would reduce the amount of automators (better visibility) and facilitate their management as, when we want to modify the flow, we currently have to adapt each clone …
I would like to insert a Canned Response into the Canned Response editor.
We have a customer requesting the ability to default workspace on new forms in the requestor portal before submission. As far as I know this is not something that we can do at this point in time. Would it be possible to make this a product enhancement request?
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.
