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.
Improvement to Current Status page.Support for SMS notifications, with toggle, as some services might require sms communication and for some email is enough Ability to set “critical” hours/dates on the services. I.e. if we have a service that is only critical during weekends, or end of month, etc. We should be able to set when to send email/sms notifications. Set target groups, e.g. we have different type of management levels, and only level-1 mgmt requires sms, level-2 is happy with email.Today we’re using work arounds to accomplish simple SMS communications. This should be out-of-the-box functionality for a status page / major incident communication tool.This may be equally good having for whatsapp, Teams (Servicebot) and other tools as well.
QuestVerse is a next-gen open-world RPG where players explore a dynamic, AI-driven universe that adapts to their choices. The game features procedurally generated quests, real-time combat, and multiplayer co-op modes for endless replayability.🔹 Key Features:✅ AI-Powered NPCs – Every character has a unique personality and remembers your actions.✅ Infinite Procedural Quests – No two adventures are the same!✅ Cross-Platform Play – Available on mobile, PC, and consoles.✅ Customizable Combat Styles – Switch between magic, melee, and ranged attacks.✅ Live Events & Seasonal Updates – Stay engaged with fresh content.With stunning graphics, immersive gameplay, and AI-driven storytelling, QuestVerse offers a unique RPG experience that evolves with every playthrough! Would you play it? Click here!
It would be nice if you can add asset state to be filterable from the All Assets and added as a column for viewing and export.
The Teams integration would be greatly improved if it allowed us to start a Teams chat with the Requester from the ticket and allow us to copy the chat back to the ticket notes.
We want to utilize the Software module in Assets more, but the interface is a bit unwieldy. When adding users for SaaS apps like some of our internal apps, I end up having to add each user one at a time and manually maintain the list of users. The module already has an Export function, can we get an Import function as well? Alternatively, using Agent and Requester Group filters could be a better way to dynamically track users of these applications as our workforce changes.
Hi!I can see plenty of topics related to Supervisor Rules here.What am I missing is the complete logic for triggering conditions. For example, I need to trigger more than one status (like pending and on-hold) and more than one Agent group in one condition. But there is no option to include more than just one status and group…Also, I don’t need to check the condition every 30 or 60 minutes (or how often it runs). The option how often to check would be nice too.This also comes on my mind: Why are the Supervisor Rules separated from Workflow automator? If you add time conditions to WA, it will solve everything at all.Also, there is no condition for tags in the Supervisor rules.
It would be great to have the ability to link multiple Service Bots to a single Teams tenant.
Good day, One of the valuable features of Freshdesk is the ability to send the entire form to the customer, along with customizable forms tailored to different cases. Enabling users/customers to request attachments within the standard 20MB limit would be highly beneficial. Adding another field like “Attachment” would just be a drag and drop and only one can be added in the form.
Currently time is logged in tickets when a note or a response is sent to the customer, it would be good to have lapsed time (in years, months, days, and minutes) in between those notes/responses to show how long it has been since previous update.Good metric to use in reporting to increase productivity and idnetify gaps Visual indicator of agent responsiveness helps guide coaching and increased levels of customer support.
Agents who have permissions to add notes on tickets should be able to delete their own notes without needing additional admin permissions.
Hi!we would like to have the ability to set time entry inside “Scenario Automations” for example.There is a lot of simple tasks, which can be solved quickly so the filling all the fields and adding time takes more time than doing the job. The bulk update of these jobs is always best choice, but there is no way how to set 5 minutes spent.ANDThe second request is to add time functions to “Workflow Automator”. I’m missing functions to manipulate (add, remove, edit) time spent on the ticket and functions to check the time spent (is the value set, <>=...)Thank you and have a nice day :)KarelPS:There are two related topics:
When can we export the multi-select field? We have already raised this issue long time ago, and almost customers asked for the multi-select field setup. The multi-select field should be the default field available on this product, compared to other competitors, they all have this field type as a default one.
Hello, I am reviving the recurring tickets feature in FreshDesk request. This is a basic function of a ticketing system that is lacking but your competitors already have it. I understand the workarounds that have been posted already in the community via API or Calendar. But come on product team…..we shouldn’t have to use workarounds to achieve this.
Problem: We have three different emails connected to our workspace. One of them is used exeternaly. It the case of the external email we do not want the to receive the standard “We have received your ticket”-email .Current solution: We have to turn off email notifications all together and make workflows instead based on how the ticket is raised.💡Idea: Make it possible to active different email notification settings for different emails connected to the workspace.
Please add a /e option to the ticket reply command list that lets me filter and select a scenario to execute.This way I can quickly select and execute a scenario that fills out all needed tags/fields and immediately start replying to the person with a custom response, or quickly reopen the command list and select a solution/canned response.
Currently you can only provide agents the ability to share ticket filter views if you give them the admin role of Manage Workspaces, Agents, Agent Groups, and Roles. It would be a big value add for managers and team leaders to be able to share ticket filter views with their teams, but I don’t want to give them this level of access.
Bulk update is nice and all, but it’s not applicable to every field type such as warranty information and serial numbers. This makes editing cumbersome, especially when the import/export process is so prone to failure (didn’t include the correct fields in the export for the asset type, times didn’t match, etc...) Being able to edit directly from the list of all assets with interactive fields would be a total game-changer, and hopefully let me toss out the duplicated work of having an excel spreadsheet!
We have a couple processes where we need to be able to block a user from submitting a request for themselves (aka not entering a requester when raising the request in the portal). An example is offboarding (we aren't using the module….yet) and adding a user to the change management process. This can cause automations to happen against the wrong value. It would be nice to have the ability to make a business rule that checks if requested for is the same as the requester and then pop a toast notification to prevent these from being raised.We can use a workflow automator to close and email the user, but that is a poor user experience if the form requires more than a couple seconds to fill in.
The issue that I am having between CC and shared tickets is that the experience is very inconsistent and easily leads to communication breakdowns or upset customers in Freshservice. As of right now CCs work just like emails (kind of), if a requester CCs a user to a ticket, the CC will get the direct email communication and also an email from Freshservice “Note added to Ticket”. Meaning the CC will get 2 notifications emails for 1 update. If he CC user doesn’t reply all and replies directly to the ticket, the original requester will not get any email notifications (not ideal). The same also occurs if the requester doesn’t not click reply all, the CC user on the ticket will not get any updates (not ideal). These 2 issues lead me to wanting to lean on the Shared Tickets feature. If the requester adds a shared user to a ticket then they should be updated on all activity that the original requester gets updated on. This should also apply to any public comments that either the original requester or the shared user add to the ticket. Both parties should always get any updates in relation to the ticket. This is my feature request. The original requester and shared ticket user should get all the following notifications via email.Ticket Approved or Rejected Requested Item Stage Change Agent closes the Ticket Agent solves the Ticket New ticket shared Note added to Ticket New ticket created
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.
