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.
People often reply to a Helpdesk support email (1) using another email address to the one captured for the ticket, or (2) to another of the corporate email addresses (e.g. as I have to set up a Google Calendar event outside of Freshdesk, anyone who replies to an invitation will send an email to joe@bloggs.co.za (my Calendar email address) rather than support@bloggs.co.za). In the case of (2), no ticket is created because the email wasn't sent to the support email address. Currently the Freshdesk widget in Google Apps Mail shows recent tickets. It would be great if an opened email in Gmail could just be "added to" one of those support tickets directly in the widget. The current workaround is to create a whole new ticket/contact then merge them etc. which is quite a hassle when the email content might just be a simple "yes" or "thanks".
Our company has multiple "scenarios" which have multiple steps that require completion to successfully resolve the ticket. Creating a scenario is a great function that does enable us to link additional and specific tasks that are required for completion of certain tickets/scenarios. I.E. a ticket for a New IT Account request or Employee Termination will have multiple steps involved to ensure the process is completed successfully. The issue we have this Scenarios is that you can only add a "Task" as apposed to a "Child Ticket". The issue with this is that we use the Arcade function along with Resolved tickets as an "at a glance" work performance metric. With "Tasks" our analysts are essentially not getting any credit for completing 10 tasks that are involved in the completion of a ticket. So in short, 1) Is there a way that creating a "Scenario" or Ticket Template that has additional child tickets could be an added function? 2.) Is there a way to add "Resolved" as a status function for a "Task" so that agents can get visual and identifiable credit for said task? 3.) Under the "Arcade" section, could more fields be added? Such as points for Task completion.
For deleted tickets ( those in Trash ) I'd like to be able to mark a ticket as spam without having to restore ( undelete ) it first. I would like to have this option on the individual ticket page. The way we are working is this: agents are instructed to just delete tickets that don't belong in the helpdesk. From time to time, a supervisor looks through the Trash folder and decides which of the deleted tickets should be marked as Spam ( and also makes sure that no "real" ticket was deleted by mistake ). Being able to move a ticket from Trash to Spam in one step, is very convenient.
Adding a notification once the problem created could be an important feature as there's a need to notify specific teams with the problem then they can notify clients or other affected teams. Now we've only "Observer" rules for Problem but no "Dispatchr" rules.
Proper email threading is well described in https://www.jwz.org/doc/threading.html and relies heavily on the In-Reply-To and the References headers of an email and, if all else fails ( and this is extremely IMPORTANT ), on the Subject of the email - a technique called threading by subject. "Threading" means that when Freshdesk receives a new email it has to decide if it belongs to an existing ticket ( in which case it add the email to the thread of that ticket ) or not ( in which case it generates a new ticket ). We have a good number of customers that use exotic mail systems. These systems send replies that don't provide proper In-Reply-To and References headers ( if they provide them at all ). We also have customers that compose new emails and just use the Subject of our reply as the Subject of their response email in the belief that this is enough. Judging from the fact, that other Freshdesk users also mention such cases, I believe that my problems are not unheard of but just more prevalent. We have past experience with systems that used threading by subject and could handle these emails. My understanding from testing competitive products, is that a number of other helpdesk platforms, also implement decent threading by subject. In most cases, the threading by subject implementation in helpdesk platforms relies on searching the Subject of the incoming email for a string that can be matched to a ticket number. For example, it can be configured to look for the first occurrence of SometextSomenumber and use Somenumber as the ticket number. Example Subject of a customer reply, with COMPX used as Sometext: Subject: Re: [ Case: COMPX674591 ] My gizmo is not working. A threading by subject system that works as described above, will conclude that 674591 is the ticket number and, if a more reliable match cannot be made on the basis of In-Reply-To and References headers, will add the email to the thread of that ticket. My understanding is that Freshdesk does not implement threading by subject ( but I would be very happy to be proven wrong ). I REALLY want Freshdesk to implement threading by subject ( and give the admin the option to enable or disable this feature and select the Sometext value they want ). If you are a fellow Freshdesk user that has faced problems with multiple tickets been created when customers with problematic email systems reply, please support this feature request.
What are the differences between Freshdesk and Freshservice? I am a MSP and Breakfix service IT company and was wondering which one would be better and what the difference are.?
I have a rather large forum and I want to be able to look at all categories but showing only the Planned items. Is there a way that I can do this already? I tried searching and finding it but was unable.
Our team is starting to get heavy with Slack and I see integration with other helpdesk systems, can we get integration rolling for FreshService? Thanks!
By definition, Standard changes don't require approval. Therefore, it should not be possible to add approvers to a ticket where the Change Type is Standard.
I'd like to be able to send email to the system whereby (a port of) the Subject would be the Title of the announcement and the Body would be the Description. You could select the Visibility by including a tag in the email Subject. For example: Subject: @Agents "Service Provider X - Notification of Intermittent Service" I'm not sure how to control the scheduling feature, but I imagine that this could be done after the fact using the web interface.
Ok so once you've got a really granular reporting system in place and can export sexy looking (branded) graph & table based reports to PDF (which I'm sure will be ready by tomorrow right ;-), we need to look at Scheduled reports.You've probably seen my request for client admins (something Webhelpdesk does really well), but if this is not going to happen how about simply allowing us to setup scheduled reports. These reports are configured, scheduled, run and export to PDF, and finally are emailed to the recipient of choice
I have a suggestion: It would be very useful if we were able to sticky the most common service items on the main portal page, thus removing the need for the requester to navigate to the page they're looking for. I know it already suggests the most popular, but that doesn't work all of the time.
When managing users in multiple domains, it would be helpful for more conditional extensibility of the requesters group logic, e.g. "from @foo.co => rg1 | from @bar.co => rg2". Sadly, there were only two lonely antecedents listed when exploring. Difficulty to implement should be trace, if even present.
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.
