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.
We recently ran into a pretty significant limitation when setting up an additional Solutions Database. We were unable to use the same category names in the new one as we had used in the existing database.This is very limiting as we would like to setup more databases, but the category names are the same.Please consider making it possible to re-use a category name in multiple Solutions Databases.Thank you! Mindy
It would be great if the ticket summary was added to the available placeholders when using the webhook action in the automations. Also current timestamp or some basic date functions would be useful when calling external APIs.
Currently I can easily filter tickets which has a limit of 10 pages with per page having a maximum of 30 tickets. But this is very limiting if I just want the count of tickets based on a filter.
It would be really helpful to be able to associate Vendors directly to Assets - we have created a custom asset type to input our properties and would like to be able to match Vendors (Landlords) directly with the asset. Please let us know if this can be possible? Thanks!
It would be great for Freshdesk to introduce a built in PDF viewer for tickets. Currently, a user relies on the capabilities of the browser, however for example on the newer versions of Google Chrome, when you click a PDF attachment it immediately asks where to save the file now, rather than opening within the current view. Therefore, a built in PDF viewer could allow the user to remain in the ticket and view the PDF at the same time. A similar type of technology can be seen in the likes of Gmail.
I’d like to automatically add several emails as recipients or cc’s on a ticket, perhaps using a group as you can in email clients such as Gmail. For example, I want an email group “Distributor A” that contains emails john@a.com, jane@a.com, and sue@gmail.com instead of having to add each Distributor A email individually.
Hi there, this may already exist, if so please reach out. On the support portal I’d like to create animation to the announcements such as scrolling or fading. This would be especially helpful if there are multiple announcements on the site.
Hello, I would love to see Field Service Management in Freshservice as well. If an agenten can’t solve the issue over phone/e-mail/chatt someone needs to go to the user. In larger origination you may have 3 - 5 agents that are dedicated just to go out to the user.Having the Field Service Management as Freshdesk would give the agents on the phone/chatt/e-mail a tool to check status on the onsite support ticket, who is going and when. //Daniel
Within the Analytics module you can create multiple widgets regarding the time spent of a ticket. You can see how long a ticket has spent in business hours and in calendar hours. But one important metric is missing: Time spent in SLA hours. This metric should be a combination of the business hours, SLA timer running and the SLA applied to the ticket. With this new metric we can track tickets that have a close to violating SLA status. Because most of the time this indicates to more complex request from our customer. Specific knowledge is necessary to answer the question of the customer. We try to replicate the metric by measuring the time spent during business hours in hour SLA timer statuses (Open and Pending). But somehow we get different results with the “SLA resolution %” metric. For example: the applied SLA should be 45 hours as resolution time (5 business days with 9 hours per day). SLA Resolution time is 100% but ticket has spent 46.04 hours in the SLA timer statuses “Open” and “Pending”.
Typing “/s” or “/c” to quickly add content to a ticket is great, however it only displays content for the default language not translations.I would like the ability to display and use canned responses/solution articles in the same language as set on the contact. If no translation can be found, use the default language.
When searching for solution articles via the API we can use the call /api/v2/search/solutions?term=[keyword] (“Search solution articles” in the API docs)It seems, though not documented, to be possible to filter by a specific language code like /api/v2/search/solutions/sv-SE?term=[keyword].I’m lacking additional filters, in my case to get articles for specific portal(s) and status to avoid drafts/unpublished articles. The additional filters could preferably be added as a query string similar to /api/v2/search/tickets?query=[query] or as query parameters like: /api/v2/search/solutions?term=[keyword]&visible_in_portals=[array_of_ids]&status=[arrays_of_statusids]
I would like to be able to export data that was gathered from a ticket form into a spreadsheet.
At the moment the ticket summary is a optional field for agents to fill in. More often than not agents forget or don’t fill this in. It would be great if there is a option to make the ticket summary a mandatory field upon updating a ticket status.
I’d like to automatically send out a different account activation email if the user doesn’t activate their account within a time limit that I specify.
Ticket View - Lock Subject/Requester Section When Scrolling DownHey!Now of course I have a laundry of list of things that can’t be done but this one moved up my list of issues today when I was replying a conversation and took way to long to realize who the requester was and what their initial issue/subject was and then I realized when you scroll down through the “description” to get to the conversations the top area that shows this does “lock” when you get to the point where the “Details” “Related Tickets” “Tasks” “Activities”, etc tabs are and then I was like why doesn’t it just only lock that whole top section instead of just the “tabs” - this would eliminate having to either scroll up and see it and scroll back down or moving my mouse to the top of the screen to click “edit” lol .. It’s already locked just needs to include the “whole top half” - interestingly enough.. I don’t even really care about the “description” box locking (only because yours can get very long with Exchange cloud signatures lol) - just the “subject” and requester info that is there already which is a brief overview of time/date/source/to, etc
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.
