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.
It would be nice to have the option of a required length on fields. We have a culture problem where the resolution information block that we have setup on tickets to allow for a brief description of the fix used to close the ticket is just being filled out with a single letter. If we could require a minimum length, like 15 characters, it would help to force agents to fill out the ticket completely. Similarly, having a max length requirement would help as well. At a previous org of mine we used resolution codes that were 4 character shorthand to allow for a little better description of what we did to fix the issue and for a field like this having a max length would help ensure good data. I’m guessing this would be a loved feature for many teams as they look to collect the best data possible out of a ticket.
We are able to pull all company records fields as well as all Custom Object fields into Analytics, but we cannot do this with contacts. I have spoken to various people over the last 2 years, as we really need this feature. We need to see how many contacts are certain job roles, we also have a tick box for release notes and we would want to use analytics to see how many contacts have this tick box as well as adding their email address so we can use it as a report. I know its not analytics as such, but I use Analytics as a reporting tool for company details, not for tickets. Just using the export option is not ideal, as we don’t want all 10,000 contacts, we want to filter to a specific set of contacts, but using Analytics and then export out.
We are able to pull all company records fields as well as all Custom Object fields into Analytics, but we cannot do this with contacts. I have spoken to various people over the last 2 years, as we really need this feature. We need to see how many contacts are certain job roles, we also have a tick box for release notes and we would want to use analytics to see how many contacts have this tick box as well as adding their email address so we can use it as a report. I know its not analytics as such, but I use Analytics as a reporting tool for company details, not for tickets. Just using the export option is not ideal, as we don’t want all 10,000 contacts, we want to filter to a specific set of contacts, but using Analytics and then export out.
Hello Team,I’d like to request the addition of emoji support in canned responses within the Helpdesk system.Why This Matters:Emojis are a simple but powerful way to improve communication tone—especially in customer support. Right now, the system doesn’t display emojis correctly (often showing as question marks), which limits our ability to personalize messages or make them more approachable.Benefits of Adding Emoji Support: Improved tone and friendliness in responses, helping us sound more human and less robotic Clarity of intent, especially in short replies (e.g., 👍 for confirmation or ✅ for completion) Stronger customer connection, particularly with churches and teams who appreciate a warm, relational tone Consistency, since many of our communication platforms (email, SMS, chat) already support emojis Even just basic support for standard Unicode emojis would go a long way in making canned responses more expressive and aligned with modern communication standards.Thanks for considering this request! Let me know if you need more context or examples—we’d love to see this enhancement in a future update.Best,Josiah
Hello, Our distribution partners love the fact they can use the search engine to find articles pretty quickly but they also need to share some of these articles to their resellers, who don’t necessarily have access to our KB. Our distributors are urging us to add a “Add a button to download or share an article in a PDF file (by email as a first step)”.Can we do that already ? We didn’t find such an option in Freshdesk.If not, can you please add this feature to the next release ? Thank you 🙏Chris
Managing locations using the hierarchical view is very difficult when doing mass updates or a major reconciliation. It’s tedious and requires repetitive actions. Presenting the information in a tabular view which allows you to sort, filter, and initiate edits in one place would be extremely helpful. Related to this, the ability to export the entire list to CSV, perform cleanup, then re-import the list for update would be very helpful!
This is a very basic feature that a lot of other CRMs got it but Fresh hasn’t.It would be very helpful, if I could get a real time notification, every time a warm lead open up my email or is currently visiting a webpage, therefore I can act when the intend is there.Fresh already has the widget to add to the website, so really the only think missing is the automation to allow people to get those notifications.
Due to security requirements, users have started sending digitally signed emails. But in freshdesk we just see “not given” and smime.p7m attachement is visible.Please support decoding or displaying the content of S/MIME encrypted attachments.
We would like the option to add new ticket activities directly into an active Journey without editing the template. We want these tickets to have full visibility to onboarding/offboarding details without extra clicks. We currently create normal (manual) Freshservice tickets and link them (parent/child or related) to the existing Journey ticket, but this creates extra clicks or lack of information for the agents working the ticket.
It would be incredibly helpful to have the ability to filter associated tickets within a problem. We frequently need to determine which tickets are still open and need specific actions if the ticket is pointing to a workaround or still need the permanent applied fix. This would enhance communication with impacted customers and give better understand to impact over time.
I recently installed the Powershell Orchestration and there’s a few things I’m not in love with from a security perspective.The password is in plain-text. Even after you save the workflow, the password is still in plain-text. This is not a good security practice. Any way to block out the password and not display it to the user? Additionally, profiles are created as part of the Powershell Orchestration settings, but then you aren’t even using a profile in the Inline Command. Instead, you have to manually supply a username and password. When a script is called, it looks as if NTLM is being used to access the script. Can we have a choice of what to use? When I use the Execute Command to run a script, it only loads in the first part of it and says it executed successfully - not executing any of the commands in the script. If anybody has any insights, I’d love to hear them to get this to work. Thank you!
Microsoft Sharepoint is a very common intranet platform for businesses; However, the FreshService status widget does not function in SharePoint Online due to iframe and CSP restrictions common across M365 tenants.A more compatible approach would be for Freshworks to provide:A documented, read‑only Service Status JSON API, and... An official SPFx-based SharePoint Web Part that consumes this API. This would align FreshService with Microsoft modern development standards and eliminate widget compatibility issues across SharePoint and Teams.Thank you for your consideration in making a major enterprise-grade improvement to the platform!
Currently, in Freshdesk workflow automations, the available email actions are limited to:Send email to requester Send email to agent Send email to groupThere is no option to send an email to a custom email address or a list of email addresses entered manually. This limitation makes it difficult to notify stakeholders who are not directly involved in the ticket as requester, agent, or group member.Proposed EnhancementIntroduce a new workflow action:Send email to custom email address(es)Key capabilities:Allow entering one or multiple email addresses Support comma-separated addresses Use the existing email template editor Optional validation to ensure correct email formatUse CasesNotify external stakeholders when specific tickets are created (e.g. VIP customers, escalations, outages) Inform management or leadership about high-priority or SLA-critical tickets Send alerts to distribution lists or shared mailboxes Notify third-party vendors without making them requesters or agentsExample ScenarioIf a ticket is created with:Category = “Security Incident” Priority = “Urgent”→ Automatically send an email notification to:security-team@company.com, it-management@company.comExisting ReferenceThis functionality already exists in Freshservice, where workflow automations support sending emails to custom email addresses. Bringing this feature to Freshdesk would create better feature parity across Freshworks products and significantly increase automation flexibility.Business ValueReduces manual forwarding of emails Improves visibility for critical tickets Enables better communication without changing ticket roles Aligns Freshdesk workflows with Freshservice capabilitiesExpected ImpactHigh — this is a frequently needed automation feature for growing support teams and enterprise environments.
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.
