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 an agent leaves our business it seems the only options to prevent them from taking up a license are:1. Delete the agent. This has the drawback of removing the agent from all tickets they previously resolved or closed and from any reporting (except customer satisfaction)2. Make the agent an Occasional Agent. This means the agent's name remains on all the pick lists for notifications etcI don't think either of these solutions are ideal, and it would make a lot more sense if there was the ability to mark an agent as 'inactive' which should remove them from drop downs for ticket allocation, notifications etc yet retain their name against historic information such as tickets that they resolved, the ability to run timesheet reports on them etc.
Until recently, new ticket requests could be created by staff and deployed through an Outlook group email. [ see pic ]. This has been in place and working for several years. Last week we learned that tickets created through this deployment method are not being recognized and created within our FreshDesk ticket system. In short, requesters are believing that they are successfully generating a cry for help, but nothing shows up within FD. I did not see anything within recent FD updates that would stop a ticket from being generated. Does anyone have an insight on why this may be occurring? Thank you in advance!Bill K
I ran out of ticket fields available to standardize troubleshooting guides that are currently published outside of the ticketing system (and therefore inconsistently followed).Would like the ability to have the Checklists (even if it is done through tasks which could be available as a Form Field Option).We are loving the simplicity of the FreshService UI but the limitation of how many ticket fields we can have has caused us an issue.
Most of our users are almost exclusively submitting tickets via e-mail. All of these tickets arrive as incidents, which have much more strict SLA requirements than Service Requests. We desperately need the ability change the submitted issues to the correct type more quickly than opening the ticket, waiting for it load, changing the type, and clicking update. Can we either add this option to the Bulk Actions in the nav menu or to the right side of the ticket? A single action to do this would alleviate so much headache.
Perimeter: Roles and scope of the agent Today, agents can have access either to all tickets (modification), or only to those of the group or groups to which they belong. The request is that the agents have access to the tickets of their group (s) in modification and in consultation on all the tickets. New requirement: An agent can edit tickets in his group(s) and see all other tickets
Often a new Freshservice portal version is activated before it is announced in this forum or in the portal itself.So I would to see the portal version that is currently live to see if there are unexpected changes.Thom van Zee
Change requests can be associated at the project level. It would be very useful if the association could be made to the specific task within a project. Ideally, it should be possible to associate more than one change request to a single task.Thank you.
Hi,It would be helpful if requests containing attachments were automatically given the attachment tag.Thanks,M.
Do you have try to quote customer question? http://www.netmeister.org/news/learn2quote.html http://www.anta.net/misc/nnq/nquote.shtml We can't, and it's a big problem. We don't reply above the text and let all the text below. We broke and clean the text, answering below some parts. Freshdesk block it. I can't quote clearly and selectively
Hi,To save our sanity on the Service Desk, please can there be an option to disable the green notification pop-ups.Red warning pop-ups are fine, these would be useful. But the green pop-up have no use and just block access to the 'new' button. They are extremely annoying and terrible use of the UI!e.g. I why do I need a message telling me login was successful when I can see that I have logged in successfully. It's just stupid!Thanks,M.
Hey,Can we get https://domain.freshservice.com/itil/analytic_reports to show reason for changes details inside the data export?We can get some details, but not all of them like these planning details?Regards,Lochy.
Many times you may need to forward ticket information/threads outside of your support system to another person at your company or an outside entity in an easily consumable format.In Freshservice, there isn't a good way to do this will all the right information in an easily accessible format. The "best" solution so far has been to generate a public URL and then send that to another person. This has two issues 1) It's extra steps to generate a public URL and 2) That leaves your URL open and the security setting is set to allow/disallow logged in users for ALL public URLs. Freshservice does have a forward option, but this does not capture all the data within a ticket nor any of the relevant properties.Our current ticketing system does this well, and Freshservice should implement a similar feature. Screenshot example below showing the basics and the thread; I took two screenshots but you get the gist of it.
I have created a Requester Field drop down to define whether a Requester is "Internal" or "External". It would be really useful to be able to select the necessary requesters in the main requesters window, and then bulk edit the field. Would save a lot of time!
Ability to use Customer Tags in Dispatch'r would make auto assignment of tickets much easier. I don't really understand what Customer Tags are for currently. I cannot get them to trigger anything.
Add support for openID authentication for things like Azure AD B2C
Hi,I integrated Office 365 in Freshdesk to make the "push to Outlook" action available to me. At first this appears a really good function, but I noticed a couple things:- There is no way to change the formatting of the message and it's all in the same format. I included the placeholder "ticket description", but the initial message loses its formatting. So if someone receives a forwarded mail this way for example that consists of three previous mails, it's not easy to see where one begins and the next ends. Also, the used formatting is huge for no reason.- This action is only available as an observer rule, while it would also be handy as a supervisor rule since it allows people to choose between adding a private note or sending a reply that would be visible to the client.Anyone else have issues with the limitations of the "Push to Outlook" action?
In my workflows, I need to check the requestor's reporting manager. Specifically, I need to catch when the requestor's reporting manager is NULL, otherwise the workflow will hang when I send out an approval email to the manager.
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.
