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.
Do new tickets from email messages from deleted contacts get assigned ticket numbers before being marked as spam?
It would be good to be able to set the default timezones for new contacts.Also, it would be nice to display the ticket contacts current time on the ticket so you know if it is a suitable time to contact them.
Where an agent is a member of multiple groups it would be helpful if we could flag one of those groups as the agent's primary group. This would be useful where creating rules such as auto assigning i.e when a ticket is opened assign it to the current agent and their primary group.
I would like an extra 'sort by' field added so I can see the latest interaction either by client or agent. At present, when you sort by last modified it also includes any ticket property updates which means a ticket property could be updated but there hasn't been any interaction for months yet this ticket will go to the top. If a 'sort by' of latest interaction was added I could then see which tickets haven't been updated with any communication for some time. Thanks, Rich
We would like to see the ability to restrict visibility to certain internal announcement to certain agent groups. I see the ability to restrict visibility for requester groups, but it's currently all or nothing for agent groups.
Hi there, You've finally added a type of Roadmap using forum posts, not really a developers roadmap but better than nothing (it's basically feature requests with a different name). What if we want to give feedback regarding things on the roadmap, or ask questions about them? These items are locked for comment so what's the best way to keep this info together without just starting a disconnected forum topic that will soon get lost amongst all the others? My first question is in regards to the reasoning behind putting resources on something like "Team Huddle". Yes it seems cool but there are so many other products out there that already provide this functionality outside of Freshservice (Teams, Slack, Skype etc). Why wouldn't you work on integration for Teams which I have seen requested many times in the forums but I've never seen "Team Huddle" requested. With the effort to increase transparency I'm curious to the thought process, to me it seems logical to put resources on integrating exiting tools vs "re-inventing the wheel". Anyway, I think it would be helpful to be able to discuss the roadmap items, so what do you recommend as a best way to provide feedback and ask questions? Thanks, Phill
Hi, we would like the option to be able to email/share a solution with a recipient or recipients without the need to use an incident.
Hello, I would like to disable the feature that automatically generates tickets from incoming email. Can this be done?
On the SLA form, in the section titled 'Set Escalation Rule when a ticket is not responded to on time' and 'Set Escalation Hierarchy when a ticket is not resolved on time', it would be useful to be able to use % (percent) to measure time. It would be useful to see 'Escalate when SLA reaches' and then the option to select a % (percent) value rather than a time. Such as Escalate when SLA reaches 50% complete OR Escalate when SLA reaches 75% complete. This will mean the different SLA levels for the different priorities become dynamic. As an example when the Medium Priority 1 hour SLA reaches 30 minutes complete an escalation will happen for 'Escalate when SLA reaches 50% complete' and when 45 minutes complete 'Escalate when SLA reaches 75% complete' will mean an escalation goes out. With the same rule, a Low Priority 4 hour SLA reaches 2 hours complete an escalation will happen for 'Escalate when SLA reaches 50% complete' and when 3 hours complete 'Escalate when SLA reaches 75% complete'. will mean an escalation goes out.
Can you add more SLA rules so that the SLA 'counter' is only running when the ticket is waiting on agents, i.e. the ticket status is Open or Pending. When the ticket status is any other status, it doesn't count towards the SLA. For example, if a ticket which has a resolution SLA of 1 hour and the agent responds within 10 minutes of the ticket being opened with a question back to the customer, the status is then set to waiting on customer. Until the customer replies, the sla time elapsed will only ever be 10 minutes. Once the customer replies, the ticket goes to open automatically, and the timer starts again.
Is it possible to embed all survey questions into the e-mail, as opposed to only the first question? We don't want our users to have to click on another link which leads them to the survey, we'd like for them to answer the questions directly from the e-mail itself. Is this possible, or are there any alternatives? Adding the placeholder for the survey: {{ticket.satisfaction_survey}} Only adds a link to the survey, the questions don't actually get embedded into the e-mail (which is not what we want).
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.
