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.
The ability to import themes across multiple portals.Or have one over arching theme that can be copied down and applied to many portals at once.Having to download and import into 50 separate portals is painstaking
The ticket created placeholder to show the time the ticket was created in emails shows the systems timezone and does not honour the users/agents timezone.This is causing significant issues with users/agents in different regions than the systems timezone.
Would be nice to auto collapse the contact details widgetEven zoomed out its quite big
Would be good to order the apps.This was raised 4-5 years ago.Some of the apps are standard apps so even if you removed the custom/downloaded apps to bring the app into the position you want it still is not great.A simple drag and drop like other helpdesks have (or an ordering page) would be great.Thanks
Would be good if Time Trigger automation could be set to honour working days instead of x number of hours.Scenario - We want to close a ticket automatically after 3 days of being resolved so we have it configured for 72 hours.However if the ticket was Resolved early on a Friday the user really only has the one day to respond as it will be closed on Monday morning. Anyone have a suggestion to handle this or is it a new idea?
One of our customers would like to see Revision Numbers to show on our published articles as they may need it when they are audited on the use of our products.
HelloMy organization is in need of tracking the time a ticket has dwelled in a particular status and would like to action on it accordingly. I see that this is something that is asked for by other freshdesk users as well.I request that this be introduced in freshdesk. - Vishnu
We want to hang a screen and show the current ticket status. There is also the ready-made analytics page, which changes independently. Now we don't want to use a full license for this monitor or have to log in with one agent user at a time. It would be very good if only this changing display could be displayed in full screen without logging in.
What is the problem?Workflows in Freshservice are really great but the more you use them with external integration the more you rely on the API to be available and the API calls to work and not fail due to some reason. Main issues we’re facing and ideas for that:API Keys and restrict users Every single agent (300-400 for us) has an API key and can use the API even if I don’t want them to use it. There is no possibility to restrict this behaviour. It should be the other way around, I allow specific users to use the API instead of generally allowing the usage. Rate limit and monitoring Notification about errors in web requests E.g. my third party integration failed because the rate limit from freshservice was reached and I needed to pull data via API (or any other error). How do you get notified about this? In Freshdesk admins get an email about failed web requests - not in freshservice. If you want to get a notification you can use the best practice I documented in the community using this Link. We need a better overview of the requests, the results and if we want to get notified about errors. Who uses the API? At the moment freshservice doesnt have the ability to see who used the API to see why the API limit is reached. I need to ask freshservice support, they send me an excel file and in the far background they themself can see the user who has sent so many requests to the API that my third party integration failed. We run into issues with rate limit very often and are hardly struggling to run our third party integrations speaking to our freshservice instance. Unauthorized requests Tell me your freshservice URL and I can exceed your rate limit without having a valid API key. I could write a script that sends 1000 unauthorized api calls to your productive freshservice instance per minute and that would reduce your rate limit even if my requests are not authorized. My API integrations that rely on freshservice api can easily get ddosed. If you ask the freshservice support they can manually block IP adresses but that’s it. Unauthorized requests should not count towards the rate limit. Following my first point about restricting users from api usage that should help here as well. Also having a timeout for users that exceed the limit very often or I’d be happy about any other improvement.Example: Simple API call to support.freshservice.com without a valid API key. I sent 6 requests to their endpoint and the ratelimit is reduced by 6. A simple script with a loop and their productive instance API rate limit is reached. Money Having a lot of external applications trying to access freshservice literally costs a lot of money as they all need a valid fulltime license + account. Best practice recommended by freshworks is to use single accounts for every integration. Just as a side note. See this topic in the idea section to get additional licences for tec accounts: Link
please allow us to add the agents to the roles from the page where roles are configured.This would easy up changes for roles greatly.Currently you have to switch to each individual agent and edit his roles in a lengthy procedure.
Hi All, I'm a big fan of the recently introduced threads in Freshdesk, enabling me to keep conversations about a ticket connected to the ticket.However, due to the nature of our subject matter, many of the ‘external help’ we need to call in, are companies who have their own ticketing system and do not allow to coldly send in e-mail. So what happens is we post a ticket in their website, and this becomes an e-mail convo after that first step. This e-mail convo automatically turns into a ticket for us when it enters our inbox, but really it should be a thread that connects to the original ticket.I don't want to merge these tickets, because then it will become muddled and the reply button will only reply to the original customer. But I can't turn the secondary ticket into a thread either, that's not technically possible.So currently the ‘solution’ is to cross-link them by simply posting a comment in each ticket that links to the other ticket. But that's not great either; the comment gradually travels to the bottom of the page (when viewing newest first) and disappears from view.Does anyone have a more elegant solution to this? Or could this ‘merge into ticket as a thread' be a feature request? thanks for readingMartha
The search function is great for agents, but why isn't this also a simple solution offered within admin/canned responses where we see ALL canned responses and have to manually scroll through the pages. Seems like an oversight to me, can this be added?
For the international use of our service catalog, we urgently need a translation option for catalog articles in the support portal.Many of our employees only speak their native language and it is useless to be able to offer articles in only one language.Making articles multilingual via clone and hiding the employees who speak other languages is not usable due to the amount of workflows behind the articles.What does the roadmap for this look like?
As of early March 2023, the ticket view in Freshdesk includes all responses created by automations. This is not useful - we don’t need to see ‘Your ticket has been received” etc all the time. We need a way to mark an automation reply so it is not included in ticket threads. Thanks
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.
