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 great to be able to setup notifications for new tickets.
Our customers are very interested in being able to print our solutions. Could this be possible with FreshPlug?
We run a time sensitive organization and promise SLA responses of at least 10 minutes. This basically breaks using fresh desk since the min starts at 30 minutes.
Hey there, A quick search on the forums shows requests for a being able to see a roadmap that go back years and yet still nothing has been published. So I thought I would waste some time and ask yet again. Can we get a public roadmap for upcoming features? It would be great for your customers to see what's on the horizon, something to look forward to and follow up on. It would also be a great way to hold Freshservice accountable to your customers to ensure that you're delivering on what you committed to. Would love to see this published finally, at the very least I would be entertained to hear why it's so hard to do. Phill
Hi all, Newbie question, as an MSP I would like to have business hours on a company by company basis but I can't see a way of doing this. Any ideas? Thanks A
Hello,Currently the placeholder text seen in our Search Form snippet is, "Enter your search term here...". Is it possible to change this text and if so, where would one make this change?Thanks,Matt
We are using Freshservice in MSP mode and have a few hundred contacts (client users) added to the system. We need a way to be able to view only one Company's client/users at a time. Even better would be if an Agent is assigned to one or more companies they would only be able view clients for those companies. The current contacts list is rapidly becoming unusable with so many contacts from different companies.
Just a small change that would increase readability of approval pages. At the moment the Service Request form contents are displayed with the label headings in faint text and the responses darker - this can make it hard to read. An example screen shot is below: If the field labels could be made bold I think it would aid reading a lot. Thanks, Phil
Hi, I've been trying to automate some approval workflows and it would be a great help if you were able to build approval groups for use in Service Requests. This would be the same as the CAB functionality for the change module - a set group of people who the requester can pick from to ask for approval. At the moment for a Service Request I am only able to setup rules to ask for approval from agents or department heads/reporting manager. An example use case is below: 1. We have a Service Request form that a requester can complete to request change/additional development work to systems. 2. To enter the developers work stream the request requires approval from two parties: A Senior Business Lead and the Functional Product Owner. 3. At the moment, the form asks for the Senior Business Lead as a single line text field (could be a drop down). There is no way to use this to send an approval, so manual action is required on behalf of an agent to submit it. Using an approval group (like the existing CAB groups) the requester could select which senior business lead they want to sponsor the request and it would be done automatically. 4. A second group for the Functional Product Owner could then be used for the second tier of approval - at the moment I've fudged this automation in using dummy Departments and setting the product owners as the heads. It works but is not ideal!
Hello, When we try do a mass-assign edition (by selecting multiple tickets from the list and clicking on "Edit" at the top), changing the group and leaving the field "Analist" untouched don't clear the names that is not in the new group. An equal issue is found when trying to assign the ticket to an analist from the list, no group filtering. Example: Group A - Analist 1 - Analist 2 Group B - Analist 3 - Analist 4 Ticket 1 - Marked for "Group A" and "Analist 1" Mass-edit the ticket assigining to "Group B" don't remove the information of "Analist 1" even he not being on the "Group B" On the list, at the right actions, any of the 4 analists can be assigned even if ticket is from the "Group A"
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.
