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.
Hi there, it would be awesome if we could visualize the SLA timer better for freshdesk like they do on Haloit would look like this:
Hello!It seems odd that we can't add stakeholders to an employee's offboarding process. There must be some questions we need to ask before terminating the employee and it would be nice if we could add stakeholders to a Offboarding request like an onboarding request!
With the implementation of ticket sharing, there are 3 immediate updates that are needed to support this new feature.Ability to remove sharers/watchers from a ticketNotes: There may be times where a collaborator needs to be brought in to support a ticket but may not necessarily needed through the life of the ticket. This is probably more difficult to implement in that you have to make a decision on whether the person should be able to view all notes or just those that were shared with them at the time they were a collaborator. This would force a per-note/reply permission flag which makes things complex. The other scenario is an all or nothing permission scheme which is probably an easier approach. This would also help in the case of accidental shares. Agent ability to add sharers and watchers (requesters) to a ticketNotes: As noted in the community thread, Agents do not get the same view of tickets as requesters do, so they lose the ability to share tickets or add requester watchers in the agent portal. Agents should also be able to view the sharers that have been added to the ticket in the agent portal view Activities log tracking the adding/removal of sharers/watchersNotes: This is a critical one from an audit perspective especially with restricted groups. All share or watcher events should be tracked in the Ticket activities log. Audit & Infosec teams will look for this evidence in the event that information which could fall under a company’s data classification policy is inadvertently shared with someone during the life of a ticket. This is particularly critical for groups that are marked Restricted.
Currently INC and SR tickets at treated as though they are completely separate. In reality, we have many instances where something a customer submits as an INC that results in one or more SR tickets being created. Ex: customer reports a problem with their laptop that results in needing a loaner system and ultimately a system replacement if repairs on their original system are not practical. (why we do it this way gets into how we handle SLA’s and relative urgency of problems until a workaround is in place as well as the ability to track asset movements across the company)We’d love the ability to relate these tickets in the system beyond just adding a note with the ticket link.
Hi,Analytics updates reports every 30 minutes but there is currently no visble metric in analytics to know when the next refresh is due. This can cause issues if you have some updated data but don’t know if you’re viewing the latest version or when the next refresh is other than waiting 30 minutes. It would be hugely beneficial to have something in analytics that tells you when the next refresh time isThe best place I think would be is here (Screenshot below) - Just some text that says something like “Next Refresh: NextRefreshTime Thanks
Hey!As a large proportion of the population use Apple products, we are finding more and more image files being sent to us via tickets that are HEIC files.They cannot be previewed within FreshDesk like more traditional image files such as JPG and PNG and I would love for FreshDesk to branch out and have this as functionality like it does for other image types.Being able to preview the picture without downloading the file works better from an efficiency point of view and is more secure indeed so would really benefit our agents.Hopefully this idea would be good for other clients too so the idea can gain traction!
It’d be great to have the ServiceBot in Slack notify agents when there’s an update to a ticket they’re assigned to.
In the activities section of a ticket, when you are looking at the history, sometimes, the time is summarized - what I mean by this is that instead of telling you an exact time something happened, it tells you things like “2 hours ago” or “a day ago”.While I’ve always felt like this was a nice touch to quickly summarize time, I recently had to fill out a Post Incident Report on a major incident. On our PIRs, I want the exact timeline that things occurred and I that’s when I wished it wasn’t summarized or there was a way to get the exact timing.Instead of relying on the Activities tab to see when things happened, I had to look at individual posts and hunt down each time via emails that came out when the post was created. Since, I’m already in FreshService filling out the Post Incident Report, I don’t want to rely on the emails to tell me the time something happened - there’s a possibility that the email gets delayed throwing off the timeline. Instead, I want to use the source of truth (FreshService) to fill out the timeline reliably.My recommendation is that you could still summarize the time, I do like that feature, but when I need an exact date/time, I’d like that to also be available so I could use it in a PIR following a Major Incident.
The resolution note field has been added into our instance but we would like to see the next developments around that field: I looked at the workflow automators and it seems you can use that resolution notes field in them, as a placeholder in the actions, but you can't find it back and use them in the 'Events' or 'Conditions'. Then I also looked at the business rules, I would expect to be able to set up a rule in there like : if 'Resolution Notes' is empty then prevent Resolve/Close the ticket. This to enforce our agents to always properly fill in that Resolution notes field prior to resolve/close a ticket and our requesters to get proper feedback about the resolution of their tickets.I would also expect to be able to make that Resolution Field disappear by just switching a toggle button off as long as the above points are not possible because now, as it's added and active, it could be used by some teams that were expecting such a field for a while (like me), they will fill it thinking the content will be communicated to the requester by the resolution of the ticket which off course won't be the case ... (I also looked under the business rules if we could not just hide it in there, by an extra rule, but 'Resolution notes' is again not a field that we can use in the Actions).
Currently we are allowed to have 10 levels of nested folders in Solution articles. While this is great, the list of "other folders in this category" got messed up now. It is displaying a random list of folders across the whole category. So please:Only display folders, that are closely related to the parent folder where the sub folders are in - closest relations first Or make it an alphabetical list across the whole categoryIn its current state the list does not make any sense and could be removed.
When you deactivate a requester it removes their name from the offboarding module view if you show the “Employee to Offboard” field, instead showing the ID of the deactivated requester. Same thing if you add the requester name to the ticket subject, that is missing as well in the list view. It would be more helpful to show the full name of the requester with (Deactivated) next to it like some other modules in Fresh Service do. Same thing for the ticket details page, it shows an empty value next to that field in the ticket description, would be more helpful to have the name there with a deactivated note.
Do we have a possibility of integration of OCI cloud asset scanning in freshservice like we already have for Azure and AWS. Lot of customers has started using OCI now.
There are several areas where business rules may not apply/work (for example, moving a ticket from one group to another but having requirements to transfer to the next group). This would result in a unique workflow automator being needed for each originating group so that the original group is known and can be returned to. In my org, this means we have 10+ different workflow automators to return a ticket to its original group when conditions are not met, when we could have one automator that would work similar to the below:Trigger: Group is updated from any group to any groupCondition: (Whatever you want)Action: Return ticket properties to previous state This would revert the ticket properties to the state before it was triggered and save a ton of replication, all because the automation stores a cached “start state” before running that can be called back to.
Given an Agent Group with M-F business hours which receives a ticket, say, on Sat, the Unattended Ticket notification is sent on Sat and completely ignores the Business Hours set on the Agent Group.It would be excellent to have the system honor the business hours in this respect.Thanks! Tim
Use case: Service item has a date on the item that is in the future. The automator should only run on the exact date specified.Problem: Current conditions only allow for X days in the future or X days in the past (see below)Solve: Add the ability to check the date natively. Current workaround (in case someone else stumbles on this): I had to get around this by settting up two logical expression nodes with the code below for the requested item AND the current system date/time:substring({{ticket.ri_234_cf_effective_date_iso}},0,10)Then I had to setup a condition using a custom expression that uses equalsIgnoreCase({{E1.result}},{{E2.result}}).While this does work, it adds an activities entry every day until the ticket gets resolved/closed (I set a condition for that immediately) which adds a lot of noise unnecessarily.
Hello,It would be really interesting to have the ability to send out test email while editing email notification
Is there a way that users that are Agents are able to see the ticket that they are the Requester/ Customer, in the agent view and not as the Customer? We would like agents to be able to view the tickets they submit as requestors the same way they view tickets they are working. We add private notes in these tickets and when agents are requestors, they are not able to see the private notes.
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.
