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.
When a channel is capable of capturing the information (web forms and API submissions), capture and store “User Agent” details and IP address. Although this information isn’t always 100% accurate, it helps our agents confirm actions the user might have taken or not taken in our backend systems that capture this same information, especially in the cases of fraud.
Hello everyone,I just ould like to suggest an improvement to ticket view for agents is to be able to show the information of the location where the requester or the concerned asset is located. That would allow an agent to better prepare his “journey” on the field by avoiding to ask an admin where is the location or search a large directory of locations until he can get the correct address where he us supposed to go.This would be helpful to the person who prepares the field missions for all the members of the team whose perform “on field” missions It would be nice to have a “location” tab in the tab list for a ticket but being able to display the location info without rellying on an admin would already be great
There are several scenarios where an Incident triggers a Service Request. For example, "computer cannot boot" incident which leads to the service request for "new laptop". From the Incident, we are unable to add the Service Request as a linked/child item. It seems that if the original ticket is an incident, only incidents can be add with the same true for service requests.
I would like to be able to sort the tickets in the tickets view by the column titlese.g. click on State to sort by the State The response I received from FreshService was: Looks like the enhancement in the sorting is something that a few customers have sought but not enough of such requests. Moreover, I was told, making changes to the sort option on the ticket page would mean for us to bring a change to our current architecture. This request is in the backlogs but we are not going to pick this up any time soon. Submitting this here to see if other people would also be interested in this - so it can hopefully be implemented..
Hi,It would be very helpful and along the line of current development to allow busines rules for the on and offboarding forms. Currently we face a lot of challenges when trying to achieve customers use cases when it comes to the forms that will create the onboarding ticket. The consequence is that onboarding is performed with Service Item Bundles which can be done but has it’s short comings when it comes to scalability.Just the simple fact that you cannot hide certain fields depending on selections in the form makes it hard to create forms that are understandable and simple to fill in.Cheers,Erik Alm
Looking to see if this would be something of interest to others. We would like to add incident fields that are hidden during business hours (example. After hours Call-Back Number)Scenario: We have seasonal and part time employees who work after normal business hours at events. The Call Back field that is in the tickets if left blank, defaults to the phone number assigned to the person submitting the ticket. (This number could be a generic department phone number which makes it difficult to get ahold of someone after hours) Proposed Idea: Adding a field (required or not) for an after-hours direct call back number for the person entering the ticket. We would like it to be hidden during normal business hours (M-F, 8-5) to reduce the redundancy of ticket fields, but would be marked with a text field below to signify providing this information will speed up the resolution for the end user.
The time-based trigger automation rule currently lacks the capability to check the requester's language. Adding this functionality would be highly beneficial, as it would allow triggers to operate based on the contact's language as well.
Hello, I have been looking into the new Workspace in Freshservice and notices that Custom Objects are per workspace and not global as well. There are going to be cases where we need the same custom objects in several different workspacies.
Hello,I am surprised so few social channels are available? We are B2B and having a LinkedIn Integration would be valuable.I saw feature requests in the past, but no response as to whether that is considered let alone what the timeline might be.
Hello, Having the ability to view KB articles in the ticket view would be great. Currently the only way to see solutions is by adding it as a note. However if an agent is wanting to work the ticket they either need to insert it in the ticket as a comment or exit the preview. It would be great to restructure the ticket view (again lol) into 3 columns:1st Column:60% of current ticket view size This would be the current screen with the conversations and other tabs2nd Column10 - 15% of screen Ticket properties3rd Column25-30% of screen Solution Articles viewer
Currently you have to statically define who/which group will receive an SLA notification, there is no option to select “assigned group”.Because of this we have to create 4 SLA policies per group so we can send preemptive notifications at 50%, 75%.
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.
