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.
Please allow us to make the comments field mandatory when a customer provides feedback on a knowledge base article, otherwise it’s impossible to get feedback that actually means something.
When creating a new ticket in general, or creating a new ticket from contact, the selection of Companies can take a while to browse through until the correct company is found (some have a list of more than 30 to select from). Can the companies drop down list be alphabetized please, but leave the primary company at the top?
Hello, I have idea to create new status cancelled. Sometimes we need this status, because we must reject support request. Status closed and resolved isn’t enough to do this. I created this status manually, but all tickets with this status are still unresolved in my Freshdesk. Will be good to have new default status: cancelled or turn on functionality to manage what status should do in Freshdesk. I found similar topic: Ability to create new status(es) that effectively "close" an item | Refresh Community (freshworks.com). Unfortunately is archived. I hope that this idea will be implemented
Think about this. You have a user community of 40 - 60 users. They operate around 1400 devices 24/7 through a software. What happens every time a devices is down? We ask them to put in a ticket. How do they do that currently? Drill through the dropdown menus. Final result? Unable to track asset incidents. Freshservice is good, but we are encountering the same issue. Users cannot enter tickets on devices. I added a multi dropdown that pulls the data from the assets data set, however it doesn’t associate the selected asset with the ticket. Ok, tried multiple scenarios, workflows, business rules, apps, orchestration, not sure why the last one, but gave it a try anyways. Ended up in the developer website, getting a postman request with the ticket information, my custom field is there with the asset id of the selected asset. Everything matches up until I have to update the ticket to add the asset. So, I can’t filter or search the asset by id, has to be by display_id, name or tag. So, before I copy all the assets to a database daily and search through that database to get the display_id, I thought that it would be easier to ask if the asset can be searched by id? Assets can be associated to tickets using custom fields? Or, some feature can be developed to do this? I want to believe that there is a simpler way for this, but I just haven’t understood the way assets can be associated to incidents, or our business logic is unique. If you have some way to do this, please let me know, hopefully before our trial expires. Thanks
I have several departments that have varying use cases for freshservice most of which requires the use of the ticket forms section. I manage visibility of the large number of fields using form rules and dynamic sections but now i’ve run into a field limit brick wall that prevents me from expanding the usefulness of this product. It would be beneficial to not be limited by the current number of fields, I understand there likely is an infrastructure reason as these fields are all probably part of a single table so maybe the solution would be to have multiple forms instead of one segmented by use case. If this would not work due to how automations work then maybe the solution would be multiple portals with their own forms/automations/rules ect. I could see this working in certain cases as not every use case requires integration with others, for example I have certain departments that prefer to have their tickets siloed from the rest of the organization, they have no need to share their tickets with others so having their own form, workflows, rules while not having the ability to integrate with other departments would be fine which would allow me to reduce the number of fields used on the default portal, it would also make my workflow automations and form rules less cluttered and would reduce possible conflicts.
Tags current show up as simple comma-separated text, in the “Contact Details” pane on the right-hand side when viewing a ticket. Tags should have the same appearance wherever they are - and when I click on “View More Info” and I see the contact’s details, I see tags, this way: Tags should have the same appearance wherever they’re used. IDEALLY, the tags should also have the option to customize the (text) color and background-color, in order to provide a visual queue for the tag.
Could we possibly get more depreciation types?Computer depreciation is measured by MACRSIn MACRS straight line, LN calculates the percentage for a year by dividing one depreciation period by the remaining life of the asset, and then applying this amount with the averaging convention to determine the depreciation amount for that year.
When ticktes are merged, the properties of the primary ticket should automatically copied to all other tickets.
Ability to resend ticket Customer satisfaction survey on erroneous click. It has happened multiple times where a client has accidently clicked ‘Extremely dissatisfied’ rather than ‘Extremely satisfied’In this scenario there is no way for the client to:1 - Change their response 2 - Have the agent request a change to that response if it was obviously erroneous. Examples:
We do not use the phone system within Freshsales, so we always manually log our call activity. It would be super helpful to be able to manually input the call activity date/time, as sometimes we’re not able to log the call until later in the day.
When closing a problem , allow it to update and close all associated tickets. This would make it faster to get updates to customers and easier on techs to make sure all tickets are closed in a timely manner.
The ability to have parent/child companies is a must have. This has been a longstanding feature that has been requested by many, however the workaround is to have Company Segments.When a company database crosses over a thousand companies, this becomes a must have as opposed to a nice to have.Eg:Corporate Company Branch 1 Branch 2
Presently, we only have one "Agent Reply Template" option in the Email Notifications section.For a better and more convenient approach for the agents working on Freshdesk, separate pre-written templates' option for first response and subsequent responses which are sent to the client can be added.
FreshService Administrators need to be able to specify app permissions to limit access to apps in the FreshService Automator. For instance, an agent that is not part of the IT team that is assigned the Automator can perform automations to just FreshService features (like assigning tickets to groups, setting priorities, etc) and not apps (like Azure which allows you to add users to groups, delete Azure objects, etc).
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.
