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.
I really need this! :)This would allow a much more dynamic and customized portal, by allowing to properly bring into freshdesk other sections that may be relevant for customers, in a completely integrated environment. To give an example, right now I'd like to to provide a frontend for contract and license management. This is something that is very specialized (i.e. hard to make it generic) and is related with customer support, so the ability to do my own integration would be great. Give me a blank page, I add a bit of HTML, CSS and jQuery, et voila.
I was testing the Mailchimp integration and noticed a couple of things that, IMHO, need improvement.A new Mailchimp list has, by default 3 fields:- Email Address (mandatory, can't be removed)- First Name (optional, can be removed)- Last Name (optional, can be removed)Since Freshdesk has just a Full Name field (not a First Name and a Last Name), the integration tries to be smart and splits the Freshdesk Full Name field into a Mailchimp First Name and a Last Name.I'd much rather prefer that the integration is not based on the default Mailchimp fields but on custom Mailchimp fields. This would make installation and configuration a bit more difficult but would add useful functionality.Changes:- Instruct users to create a new Mailchimp list (say 'Freshdesk list')- Instruct users to remove the First Name and Last Name Mailchimp fields from the list- Instruct users to add new Mailchimp fields for Full Name (the contact name) and Company (and, possibly, fields for Title, Work Phone, Mobile Phone, Address, Time Zone, Language and other data that Freshdesk can provide) with prearranged tags.These changes would mean that the integration passes on to Mailchimp a wealth of useful information.
Please can you add current week, previous week, previous week and previous month as default time periods for the reports? Quests have current month and previous months so should be possible.
Hello, Bundle feature is very nice. I'm wondering if you have plan to make fields replication working on date and dependent fields? Best regards, Rodolphe
Is there a way I can setup an e-mail notification to my agents when a ticket is resolved? This will allow our agents to monitor their e-mail box to know whether or not a ticket was worked on by someone else or if it is still hanging out there.
Being responsible for our Freshdesk installation and ensuring we are all using the system correctly, I frequently need to check ticket details to find out what happened in a situation. I'm finding it very difficult to look through Agent's tickets where the Agent has used Scenarios or where rules have been triggered. The "Activities" of the ticket show the actions that were taken as part of the scenario or rule, but if there is any content such as an email, I can't see that content - it's not added to the ticket itself. Only an activity that says, "Email sent to <user>" - with no actual information about what was written to the user. The way to you have to work currently, is exit the ticket or open Freshdesk in another tab/window, navigate to the rules or scenarios option in the admin tab and then hope you can find it when at least my team, has the same rule/automation perhaps four times, because we have different teams to communicate to. This is very inefficient and cold be solved in one of two ways: First, tell us and also link us to the rule or scenario that was triggered. Then, if there is a message sent to the customer, hyperlink the activity entry to the actual message sent, OR Simply put that message sent into the actual ticket, just as if you replied to the customer.
We want to be able to offer Freshdesk access to our customers but allow them to use their own SAML SSO services to perform authentication.We are able to perform this in our own SAML IdP however we need a mechanism to pass the company information to our IdP so we are able to authenticate them correctly.
I have looked through the admin panel and the forums and haven't found if there is a way to do this. Is there anyway, in agent settings and/or roles, to restrict who can and cannot adjust due dates? We need to be able to restrict this, especially since the ticket history doesn't show you who/when a due date was changed, and to what it was changed.
The current Agent Reply Template is a nice feature, but kind of crude.Unlike the other Email Templates the Agent Reply Template refers to the whole reply content, nut just the email content.That means everything inside the template (i.e. ticket link, other additional information) is added in the reply itself and is included in the ticket overview thus.But these information out of the template is unnecessary in the overview and repeated in each reply.The solution would be to transform the content template to an email template with placeholders (like {{reply.content}}) as it is handled with the other ones.
Hello Freshdesk!It would be awesome to be able to create a folder structure within the overview for the automations.We are in the progress of automating many things, and would like to order this correct.Would this be possible?
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.
