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.
Hello is there any integration available or planned with Magento ecommerce platform?At least a single sign on option to implement customer ticket page and faq/knowledge base would be mandatoryOther competitors (e.g. Zendesk) has such an integration :-)
Hi,It would be great to be able to embed placeholders (product name etc) into the signature. This would enable us to offer a more personalised experience for each product we support.Thanks, Andrew.
Would be nice to integrate Freshdesk with Pivotal Tracker (https://www.pivotaltracker.com)?The ideal workflow would be that you could create a story from a Freshdesk ticket. Ideally PT could reference the FD ticket and vice versa. This would make forwarding tickets to our developers so much easier and seamless.
Not possible to target the internal agent or internal group ticket field when creating scenario automations. This seems to be missing in more than one place as well but scenario automations are critical to my current task. As per my last opened ticket this functionality implementation seems like it lacked follow through.
Hi, Like the Call History I would like an Agent Availability History so you can see when Agents were in/offline and use with the Call History to better understand why a call isn't answered or goes to Voice Mail. Thanks Dan
Please add the Ticket Creation date to the Ticket summary line.My thoughts: saying a ticket was created 'about a month ago' does nothing for our reporting or viewing actual ticket creation dates. Having a creation date would also help in our reporting and would help us to identify exactly when an issue or issues occurred.This is the only system I know of where 'Created Date' is not available.
Hi, Is it possible to install a tag manager like Google Tag Manager in Freshdesk? Thanks, Vijay
Currently if you have multiple Support Portals, one for each Client (using MSP mode) a client from company A can log into any of the other customer portals. It does require them guessing or stumbling on the url but there's no way this should be able to happen. If information on the portal should contain proprietary information (i.e. client specific KB Solutions) they should only be accessible by users belonging to that company portal. Related, all the Support Portal settings that are allowed (Allow Sign Up, Require to be Logged in etc) should be available on a per portal basis, not the same set of setting for all portals. My first feature request, lets hope this doesn't take 3 years to get implemented!
Trying to create two links to put on the portal. When these links are selected it creates a ticket that goes automatically to a specific group. Any help is appreciated.
It would be very helpful to be able to merge customer records.
I need to be able to create a scope that would allow a group of agents to see tickets based on location. For example, AgentA needs to be able to see all tickets where the requester's 'site' field is "A". AgentB needs to be able to see all tickets where the requester's 'site' field is "B". They need to be able to see these tickets by site regardless of what agent or group they are assigned to. However, they should not be able to see tickets from a different site. AgentA should not be able to see tickets where the requester's 'site' field is "B". I suggest creating a page to make custom ticket scopes with a number of variables we can set to create our own scopes for however we need them. 3 options is just not enough for scope.
The possibility to use the own domain with SSL/https would be useful.At the moment encryption is only available through the subdomain of Freshdesk.
Our Grounds and Maintenance team use FreshService ticketing and often share jobs. We would like the ability to assign multiple agents to one ticket to keep all parties up to speed. I believe this is already a feature in FreshDesk and would like to see it in FreshService.
When setting up a multistep service , like onboarding, using "Additional Services" in the service Catalog, you have to choose wether to make all additional services as child tickets, or they are listed as items under the original ticket. It would be a lot more flexible if you one could choose which additional services where extracted as a child ticket, and which will stay in the original ticket. The reason is that a lot of the additional items is handled by the agent that gets the case, but some things are sent on to economy ore HR. F.ex, on our flow th IT agent will create the user in directory, order hardware if needed and sets up the machine when it arrives. We want this things to stay in the main ticket. Then we have some stuff for Payroll, and some stuff for HR, and this are the things that we want to put in child ticket. The way it works now makes us 7 to 10 tickets for an onboarding, when only three parts are involved.
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.
