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.
Hello,I believe there’s a huge gap in the current state of the audit-log. There’s no way to monitor custom objects currently and i would argue this makes a big part of the audit-logs of workflow logs unreliable too.Many people like me refer to their custom object lists in workflows for things like approvers. So it’s currently possible for someone to edit - for example an approval list in a custom object that is used in a workflow.This is a must-have feature in the near future to be able to rely on the audit log. In essence it means that parts of the workflows are currently outside of the audit-log and I would argue this is a security risk.
Hello,It's great to see that FreshService (Enterprise Level) offers HIPPA Compliance. It would also be great to see FreshService support Public Sector/Government customers who need to meet CJIS requirements by ensuring FreshService is CJIS compliant (i.e., AWS Government Cloud). AWS Cloud for Government (amazon.com)
It would be a nice feature to run a GET request to get who is currently on call so we can automate updating that information in other systems that we use. As it currently stands, outside of exporting the on-call calendar, there’s no good way to inform other departments of that information. With a GET request, we could set up automation to automatically update who’s on-call and better handle when we have to make changes to the schedule.
We want to synchronise some of the department data to another service. Being able to filter on the updated_at field would help reduce the number of API calls we need to do. This would improve the sync's performance and help us stay within the Freshservice REST API rate limit. Thanks,Dexter
Service Catalogue items are subject to field limits (https://support.freshservice.com/support/solutions/articles/50000000600-do-we-have-limitations-on-the-number-of-custom-fields-that-can-be-created-in-a-service-item-). Once these limits have been surpassed, there are no warnings or indications to suggest this and as such hours can be wasted creating a complex form only to find that you are unable to save it - let alone publish it.A simple warning to suggest that ‘You have reached the field limit for {{field type}}’ would be sufficient, however greying out the field type in addition to this so that further fields of the type cannot be added would be great. Also a counter for each field type at the top of the page would be very useful, something like:Text/Dropdown - 34/50Checkbox - 12/25…
ATS (Applicant Tracking System) suggestion:Would be nice to have branded resume. Resume is a tailored version of the original, including your chosen logo in the header and a transparent text or image watermark in the background. The only visible text will be the candidate's name.
Ability to create Child Tickets from Workflow Automator. This would be a very powerful feature that will allow for deeper automation. The ability to automatically create child tickets based on specific conditions will help create more intricate and detailed automation, increase efficiency, and solve many problems Tasks currently cannot address.
In the automator, it would be good to have a “do nothing” action block to symbolize the workflow ends. Example: We have an automation that will route all service requests based on predetermined groups to handle them and if there is no group listed in the service request, it routes to our L1 team to triage (in case we forget to add the new SC Item to the Custom object table). If a scheduled SR is created it will be routed to L1 despite having the group specified on creation. If we create a condition that forces the automator to do something only if the group is empty, it results in a condition that has no opposite output) see below)Example conditionI have seen workflows where this lack of “no” condition causes following automators to not run because, according to the activity log, the workflow is waiting for automation (or similar).Having an “action” of “end workflow”, “exit” or similar would be helpful with troubleshooting and even representing that the workflow is intended to be completed instead of just being empty.
I guess everyone came across that behaviour when trying to configure business rules.The idea is to have the same field as condition for that business rule to apply and the same field/dropdown as action. Can one of you think of other interesting use cases?Here a few from my side. Hiding status "closed"Freshservice implemented a feature for hiding the close button in the navigation bar of a ticket (editing a ticket). You can now disable the field “save and close” when creating an incident (new tickets). Great for us.As a consequence of disabling this button you can no longer see the status “closed” in a ticket dropdown. An agent checking a closed ticket now shows “open” in the dropdown as this is the first value and “closed” is shown at the top right. This could get fixed by this idea. Only when the ticket status is “closed” extend the dropdown and show “closed” again. Archived agent groupsWe disable archived agent groups that are no longer needed. We need this for history and audit purposes. Agents are not allowed to send a ticket to that group as we hide this group within the dropdown. Another issue is that in the overview you can still select that group as the ticket overview is not affected by business rules - bypassing business rules is possible which is also an issue for us in change management. This ticket for example is in an archived group, an agent checking this ticket shows no agent group. Same logic as use case before. Limit functionalities for a field to only specific personsImagine a checkbox that everyone should be able to check. But not everyone is allowed to remove again. Everyone can mark a ticket as a security issue. But only the security department should be able to uncheck this checkbox again, so I wanted to disable this field. Once checkbox is ticked, disable this checkbox - same field for condition and action which is not possible as of now. Change ticket typeYou are able to change an incident to a service request. No information gets lost in this case. But if you convert a service request (with a catalog item attached) to an incident, the information the customer entered is lost. So i could imagine a business rule: Condition: type is servcie request, Action: Disable type.I know this can be handled by the condition “service request item is attached”. Happy for anyone to share other ideas.
Currently for Business Rules for changes, to set a condition for start dates and end dates, the only option is to select a between range of actual dates. Could that be expanded to have a condition for relative dates? For example, set a condition for if the start date is after the current day.Currently changes are able to have their status closed even if the current date is before the start date. It was requested that this be restricted or give a warning of some sort. I tried to create a business rule and couldn’t because I could only select the “between” option for start date and then only select absolute dates - for example between February 4 and February 8.
In this thread, you could discuss how businesses can use Freshworks tools to improve their Instagram marketing strategies and track ROI. Here’s a breakdown of what you might include: Integration Tips: How to connect Freshworks with Instagram to streamline customer interactions and track engagement. Analytics and Reporting: Ways to leverage Freshworks' analytics to measure the success of Instagram campaigns and gain insights into customer behavior. Customer Support: How to use Freshdesk or Freshchat to manage Instagram-based customer inquiries and provide timely support. Automations and Workflows: Ideas for automating responses or workflows for Instagram messages and comments. Case Studies: Examples of businesses successfully integrating Instagram with Freshworks tools and the results they achieved. Encourage community members to share their own experiences, strategies, and questions related to integrating Instagram with Freshworks. This can foster valuable discussions and insights!
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.
