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.
if the ticket system uses a mail from the mail templates and sends them to requester and / or agent, they will not be displayed in ticket activities. I want these activities to be listed too.
If you enable the option to send a customer survery from Freshservice the customer recieves 2 emails when closing/solving the ticket.Is it possible to add the survery to your signature? so the customer does not get spammed with emails from us.Also im not using the other options because they are added at the bottom of your email conversation and might not be noticed by the customer since they have to extend the conversation to read it.
To limit the mail flood, it would help us to perform actions only if the event was executed by another user because we want to be informed by mail at every status update
Is there any customization which can be applied to the default "Install" button in the custom installation page ? Such as changing its display name to "Next" until the user reaches the last stage of the setup. Or to remove it completely until custom validation is done.Regards,Karthikeyan M
Many times it makes sense to leave a note on a task rather than a ticket due to task vs ticket assignment. A feature like this could greatly help with On-Boarding or Off-Boarding tickets where there are 20+ tasks associated all assigned to different users.
Hello,We just started to roll out FreshserviceWe would like to report on the number of ticket created by a specific groupWe need this kind of KPI for billing purpose, specifically for external partnerAt first, it seems that it is possible to search by requestor, but not by creatorIs it something we missed or is it a missing features ?Thanks
Is it possible to define custom automation rules via the developer API?
Thought i'd put this all in one request. Would like to see the ability across the platform to scope more things to groups. examples:- Surveys- Side bar apps in ticket view- Analytic reportsJust to name a few. Basically, the ability to better customize agent experience by group. For example, we build a Jamf Asset sidebar app for our IT team. They are the only ones that need to see that app in a ticket, but ALL groups see it (our legal team, travel, facilities, security etc.... all teams on the platform see it and they dont need to)Surveys: https://support.freshservice.com/support/discussions/topics/326963- Analytics: we have some teams that are power users of this section and it makes for a cluttered space for all agents groups. - Scope service items to an Agent group: all the time we make new service items and want to either test it live on the service portal and/or demo it to the agents that it is for, all without fully publishing. The hack we use right now is a requester group , but that still shows for ALL agents on the platform and ALL admins. Ability to scope to agent group would allow us to test before publishing live in the portal for a real world experience AND demo items to stakeholder agents. The list goes on. I think the ability cross platform to scope to agents groups on features is a huge win for freshservice.
I'd like to be able to use "wildcards" for conditions in Workflows, specifically when referring to "Requester Title." What's interesting is that the default workflow for "Approvals" came with its own placeholder "CEO" which is not in our list. However, when I replaced it with any other title that isn't in our system, it won't let me.Specific use-case: In our company, we have more VPs than... anybody. So I'd like to be able to say "If a VP" then "auto-approve" or something like that. However, I can't use "VP" as a wildcard to trigger all of the VPs in the company:
We'd like the ability to add conditional fields to our Service CatalogFor example:Q: Does the user need this feature?A: (Drop Down)Yes (displays the "Next question" fieldNo (hides the "Next question" field
Current Behaviour:- enabling surveys and the sending rules applies to all groups- This means groups that dont want to send surveys will have to or vice versa. Requested behaviour:- Create a custom survey- Scope to a specific agent group- allow the sending rules to apply only to that groupExample Scenario:- Agent group IT Specialists sets status of an IT ticket to closed- Specific IT customer satisfaction survey gets sent to requester automatically Meanwhile, - Agent group Facilities wants to only manually send surveys when they close the ticket and have their own wording in the surveyFinally,- The HR team doesnt want to ever use surveys automatically or manually. to accomplish the above, we would need the ability to scope surveys and survey rules by Agent group.
Currently we are seeing the need for a possible feature that would allow an agent to alter the subject line upon replying to a customer.As a specific example, we have tickets that we make and assign to requestors based off of phone conversations. We normally use a subject of "companyname - Issue synopsis." In some of these tickets, we may be looking at communicating different sets of information to the requester and different groups of CC'd individuals. Most commonly, we must indicate to the requestor and one specific individual that an account is configured with a specific setup. Then we have to reply to the same requestor but a different individual about a similar but different account setup. All of this must be captured in one ticket. Right now, we have to edit the subject using the edit option so that when replying it contains a subject of "Companyname - Accountname setup."This is a tedious process that could be simplified if there was an option that allowed an agent to check a box, and then it opens the ability to alter the subject line of the email being sent out. (it would be even better if it didn't actually alter the subjects of the ticket.)I imagine we are not the only company that would benefit from the ability to edit the subject line from the reply itself.
Easily add a choice to a drop-down list especially when this needs to be done alphabetically. Need: Have a dropdown field that makes use of a single list of choices to maintain and no longer have to complete form by form. The forms will make reference to this single list to be updated. Objective: administrative gain in terms of maintenance / ease of updating Example, in our case, every time we add a site we must review and update 80 forms.
The Customer record should include:Date CreatedLast LoginThe use cases are simple (and very common): Recognize customer loyalty (date created) Recognize inactive customers to try and win them back or purge them
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.
