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.
Does anyone else want a delayed send on emails and ticket responses? I personally don’t care how it affects the SLA and would prefer to have some of our emails replied to during higher staffing hours. This would be a relatively simple, but powerful feature to add to freshdesk.
We could benefit from being able to “send” emails but have them sent on a delay. Allowing for emails to actual be delivered several hours after they were “sent” by our staff. Is this something in the works?
I recently setup an emergency notification system in the event of a Major Incident. My requirements for this project were to call & email approximately 35 people when a major incident occurs or when an incent is upgraded to a major incident.My first inclination was to create a custom object and add the 35 people needed to that list - boy am I happy I didn’t do that, because I noticed there is no way to get every value out of a custom list. You can get a single value, but not every value.We really need a way to iterate through a custom object to use every value in the list. This could be done in several ways For Each loop, while loop, etc.When I found that couldn’t be done, I had to tediously add all 35 members of the on-call team to a very long workflow. The problem with that is that it introduces the possibility of mistakes. Just take a look at the image below that shows my workflow - everything at step 4 and beyond is basically a clone of the steps before it - what a tedious process.
To make the WhatsApp template sending process faster and more organized, add a feature that allows users to select a template group before choosing the specific message. This can be implemented by adding a filter or tab in the message modal, so the user first picks the group (e.g., Claims, Installments, Renewal) and then sees only the related templates. This approach streamlines navigation, reduces errors, and keeps Meta’s grouping structure integrated into the workflow.
Hello,we changed to Enterprise because of our need to have a sandbox for development and testing. But my biggest problem is that the Sandbox is in no way an EXACT COPY of production. A lot of data is missing, One big issue is i.e. missing the ‘IT Operations’ section.But also contacts, assets, etc etc.A sandbox must be an EXACT COPY of the production otherwise developing and testing is useless. We do not pay this much extra for an Enterprise license to still have to test in production!Regards,Eric
We have recently migrated a portion of our company over from Zendesk - And with the Teams integration there Agents could spin up Direct Messages with Requesters from the TicketWe have also just moved another portion of the company from Salesforce Service Cloud - and also with the Teams integrationb there Agents could spin up Direct messages with Requesters from the Ticket.However, on Freshservice - A Dedicated Channel is created each time. Not only is this super messy, but also from a Channel Visibility / Security standpoint this is a complete non starter.I recently asked our account manager about this and was told that DM’s were not on the roadmap - So we have had to pay an extra $15k to use this third party app for this use case - https://www.freshworks.com/apps/rck_techiees_ms_teams_chat/Is this something that Fresh might reconsider? Would be great if this was something that we could do out of the box, as per your competitors.
There is an opportunity to make Status Page Services more manageable.1) Reordering services using the Status Page “Configure Services” interface is very difficult when there are many groups and many services.Drag and Drop is not effective with long lists. Instead, here are some suggestions:Alpha Sort as an option Reorder the list using numbers2) Ability to add a service directly to a pre-existing service group3) Include hyperlink from listed service back to the associated Service Management service for ease of reference and management
Change Management in FreshService is not very user-friendly from the CAB perspective.Running a Change-Advisory meeting is non-intuitive and follows what I might call a tortuous process.Here’s what I mean:I want to start a Change Advisory Meeting:Navigate to Changes Select “Change Calendar” (Why not “Start CAB” then pick from list of meetings, or pre-populate based on pre-filled date?) On the calendar, select the time block for the meeting and View Details Select “Run Meeting”Then, when running the meeting, if not all CAB members are in attendance, going if you wish to run through the approvals while on the call, requires deselecting absent team members for every change being reviewed during discussion.This could be improved by surfacing the Change-Advisory meetings as it’s own applet/function, and avoid such repetitive actions.
The ability to generate/update/manage a Status Page Incident from a Problem would be very helpful.An incident which affects many users is managed via a Problem. Managing a Status Page Incident from one of the originating incidents is counter-intuitive as it is just one of many “symptoms” of the problem. It would be more logical to generate the problem, then have the ability to manage the SPI from there. The problem already contains the means for addressing workarounds as well as permanent resolutions. This would address confusion about finding which of the many incidents related to a problem is the one that is being used to manage a Status Page Incident.
Most of our maintenance windows are planned for something like “Every 2nd Tuesday of the month”. There is no way to accommodate this in the current system other than to manually schedule ever maintenance window. This is cumbersome and difficult to manage consistently. Looking for something more like the below. While we’re at it, please make it possible to schedule the pattern for at least 1 year at a time.
When there’s multiple identical tickets from the same e-mail address, those tickets should be flagged as spam.
It would be very useful to have code blocks available in notes on tickets and other objects. There are times where I would like to add a snippet to a ticket and while this can just be pasted in, having syntax highlighting and formatting would be much easier to read.
Navigating to the Status Page from within FreshService requires locating the instigating incident, or navigating directly to the status page.We would like to see the ability to add the Status Page as a navigation item on the FreshService navigation pane for quick access.Ideally, this would be a version of the status page which would allow updating of the SPI’s directly from the view rather than having to go back to the instigating incident.
Over time, the count of workflows in our Freshservice instance has grown to nearly 200. With so many workflows, as we update our Service Items, there are times when the change we make accidentally impacts a field used as workflow condition resulting in that workflow no longer functioning.We often discover this accidentally when entering a workflow to make an unrelated update only to see an alert within a condition node alerting that that there is an issue with a field.Since Freshservice is clearly able to observe when this situation occurs, could a single viewing place we created or a flag appear in the list of workflows so we look in one place to see workflows that need attention?
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.
