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.
Side effect is that vendors should no longer need to show as requesters.
While the Arcade feature is all good fun for most of our agents, there are some individuals who may find it uncomfortable being rated in such a public manner. Also, in certain geographies we will definitely be running into challenges with worker unions/councils about the feature. Requesting a way to opt out individual agents from the Arcade.
This idea is related to an Item and it's Comments section. When utilizing the Ordered List functionality, there is no way to change the ordered lists indentation and logic to numbering. For example, I want to change the indentation location of #2 below to the left since it's a primary bullet, not a sub-bullet.Thanks,Brad
Idea to add custom fields to All Items view. It was requested with https://support.freshrelease.com/support/discussions/topics/50000000510 and it would be address in the near future.By being able to add a custom field to the view it helps scenarios when you are working with other parties who maintain their own board/backlog and you want to reference their unique identifier to the Freshrelease item. Thanks,Brad
It would be good to have Location, Division and Department as choices under Filter, to create more specific requestor's searches and Dashboards. For example, in our business we are interested to see and compare tickets raised by different locations to find patterns and create improvement plans based on geographical aspects.Thanks.
We use Freshservice for our staff to request leave. I'd like to be able to create a task that spans multiple days to show in the Freshservice calendar when they're away.Additionally, using the Workflow Automator, I should be able to have these tasks appear in my integrated Google Calendar (The option to make it appear in the Google Calendar only appears when you manually create a task, not when it's done through the Workflow Automator).
Importing a list of products into the Service Catalog or allowing an import to go into a Drop down box under a dynamic field.Anyone been able to intergrate a SQL database into the Service Catalog at all to allow the users to select a product (Hardware)
Hi, It would be great to be able to schedule tickets for non-specific dates. For example, being able to schedule a ticket for the 'first Monday of the month', or the 'third Thursday of the month'. It would also be great if we could add Tasks to scheduled tickets. Thanks, Reuben.
We would like the ability to edit the Priority "Description" field values. Priorities like "Urgent" and "High" can be defined differently by different individuals and having a generic description as in "This is the description for Urgent" adds no value.Thanks,Brad
It would be useful to be able to create tasks that are not related to tickets i.e. so we can use it to manage day to day tasks, which currently we do in other applications
When signing up for a Pro plan, or any future plan that requires payment, there needs to be functionality to assign a primary owner of the environment along with what user(s) receive invoices.Currently in Freshrelease, there is really no transparency on who created or who is the owner of the environment. From what I can view, the only way someone can tell what user represents the owner of the environment is they cannot edit or delete the user from the Users section. With below Brad Freshour is the owner so when the cursor is placed over the section for the user the icons do not display.Also, there is no way to designate who should receive invoices. With Freshrelease, the functionality is present. For example with below, brad@beginproj.com should not be receiving the invoices and someone else should.Thanks,Brad
I like the ability to create rules for tickets, but what about rules for the support forums as well.Conditions for these rules could be: When the number of votes are [greater than, less than, equals] a set amount for a topic. When the number of replies on a topic are [greater than, less than, equals] a set amount. When the forum type [is, is not, is one of, etc.] specific type(s). etc. Actions could be: Create a ticket with the user who posted the topic as the reporter (if it was a problem or idea posting). Notify user(s) and/or group(s) of the posting/user who posted the topic, via email notification or as an option to third party interrogations. etc.
I have just found that if I go to another browser, navigate to a KB article and hit F5 several times, it actually increments the count of views. That pretty much negates the usefulness of any KB analytics since they can be falsely driven up like this. Is there something I am missing perhaps?
As a Project Manager, I would like a work breakdown view to sprint to better see the dependencies and progress of my product backlog or roadmaps.Something like this:http://prntscr.com/q5omzz
I understand that SLA is useful for many scenarios, but I don't find it useful for mine. The relationships we have with our customers are long running, and to force use to use a SLA whose max time is 1 month leads to a lot of tickets being "overdue" when in fact they are not by our standards. I'd love SLA to be optional.
When using the Kanban only project template ("Manage task lists and use boards to visualize progress") ...can we have the ability to hide Task fields? For example, the Sprint field is not needed so it would be nice to hide the field.Thanks,Brad
In FreshService we can have multiple departments associated with an individual.This is useful for us so that we can pick up that individual on multiple queries (dashboards, reports).We also have been forced to create a virtual department in FreshService for those individuals who are able to use the OnBoarding feature.So, Fred is a team leader in "Software Engineering" and has the department "OnBoarding", has 2 departments.When AD Synch works, if Fred moves to "Mechanical Engineering" then the Department field in AD overwrites both the FreshService departments.It feels like we either need "Groups" to be more flexible so that we can populate specific individuals, as well as using the current rulesORWe need some additional logic in the AD synch to know which department to replace. I can only think that each department entry would have to be marked as "synched with AD" so that the synching knew which department entry to replace.
Would be good to have these additional ticket types, or entry types under an "Other" section which may make more sense: - Project - Task - Improvement I currently have these item types in FreshService and it doesn't work well (use tags or a description in the title to differentiate). These particular things have differences from incidents and service requests. Different field requirements, tend to last longer than tickets, different SLA requirements, and different purposes. I think it would be useful to have these for these benefits - Will become more holistic for the management of time for IT staff. Option to use FreshService as a complete task and time management system - Can time track all this in a single system - SLA respect for Incidents and Service Requests only - Separation and filtering - Improvements could form a Continual Service Improvement (CSI) register - Can link all those items to CIs, tickets, change requests etc for data, context, and reporting - API magic
We would like to have an option to set up video recorder inside of feedback widget in Freshdesk (e.g. how we can now integrate HippoVideo for instance in the support portal - we would like the same in feedback widget)
The capability to sort newest to oldest versus the default oldest to newest would eliminate unnecessary scroll time in the item. Users who's activity is hourly or daily don't need to scroll to get to the most recent comment and would prefer to see the most recent comments at the top of the thread.Thanks,Brad
On the Ninja forum, a few people have requested this directly to a Freshservice rep, and supposedly something may be in the works. Just putting this out here publicly. I left freshservice back to RepairShopr for the Ninja integration, but am missing Freshservice's workflow and KB. If this becomes an Integration, I would surely come back.
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.
