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.
The Card View of tickets is great - but it is missing a really important piece of information - the ticket type! It would be so simple to add, and is a far better experience than the table view. Can this be considered?
We want to be able to create a quick alert on a Company for agents when creating a ticket that shows them important information. For example:“If the requester is asking for access to product, please refer them to the Security team.”
Hi! It would be great if the getDay() function could be added into the list of Javascript functions for Bot flows. We could use this to have the bot route our customers to our weekend agents on Saturdays and Sundays.
Viewing the Number of Tickets such as Unresolved ticket's in the IOS App would be helpful for management to manage the team. Similar to FreshDesk.
It would be nice to be able to embed a button (or even a URL link) in an email notification when a ticket is Resolved that lets the Requester change the status of the Incident to Closed. We created a Workflow to automatically notify the Requester when a ticket is Resolved, but they will need to go change the status on their own, and our user base is likely to not do things that take more than 1-2 clicks.
Hi! Currently with Omnirouting, you can enable the system to pause chat and email assignment while on a call. We would really love to see the ability to pause phone assignment while on chats. This would be a game changer for our staffing setup and would give us a lot of flexibility for interaction assignment
It would be great to be able to display project widgets on dashboards in Freshservice.
Analytics - Changes Module - Filter on future datesThe ability to set default filters on future dates exampleNext 2 daysNext 2 weeks This is required since changes are all set in the future so it does make sense to include these default date ranges to visualise future changes in a dashboard rather than just in a list.
It would be so helpful to include canned responses within Changes Module. Especially since when you want to forward details of the change to an external entity.
We have API users that control a few automated processes that open and close tickets and keep a record of approvals. We also have a few other automated "alert" process where a ticket is opened and closed if the service comes back up or remains open if need agent intervention. Either way this API agent and/or ticket types should not qualify for the automated process or API agent to show on the dashboard. Is there any other way to control who or what does not qualify to show on the leaderboard?
Is it possible to report on the SLA time used by us rather than by the customer? For example; If we only used the 4 built in status; Open, Pending, Resolved and Closed. Open means the SLA timer is running Pending means the SLA timer is stopped (e.g while waiting for a customer response) Resolved/Closed obviously means SLA timer is stopped. Lets say the following happens / Chronological Example: 10:00 - customer logs a ticket (ticket is open and SLA timer has started) 10:10 - we respond with a question / saying it's fixed and mark the ticket as pending (and therefore stopping the clock [(A) we have used 00:10 - (B) the report will show 00:10] 10:20 - the customer reponds saying it's not fixed (ticket is set back to open) [(A) we've used 00:10 - but (B) the reports will show 00:20] 10:30 - we respond again and set as pending [(A) we've used 00:20 - but (B) the reports will show 00:30] 16:00 - customer responds (ticket is set to open) [(A) we've used 00:20 - but (B) report will show 06:00] 12:10 - we resolve the ticket and it stays resolved [(A) we've used 00:30 - but (B) report will show 6:10 ] Can you confirm this is how it currently works? Can you confirm if we are able to report on (A) rather than (B) please? Thanks in advance Chris
How can i inform my agents that a new solution/faq is published? Email notification? RSS?
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.
