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.
We wish to have a better product description format on document. They are all packed without proper formatting. Price can be set to zero
Feature request for adding a "Is not" condition for currently available only a "Is" condition for dependent fields for time trigger automations in Freshdesk.
This really is a requirement. We have customers that queue up with no visbility into their queue position. It would be amazing if we could have a queue position counter for customers that updates as their queue position updates.
Hi commuinty.I would be a great upgrade if we could use custom objects lookup relation ship fields in ticket forms directly for customer.Here is a usecase : Customer are raising tickets concerning a product, today they’re typing the product name and serial number, then Agent has to search in the lookup so he can link the product record (custom object) to the ticket.It would be lovely if customer is able to do this by him/herself.If you think this feature can help your business or your customer, don’t hesitate in upvoting this post.
When emails in a long chain are forwarded to our servicedesk email, the last message is at the top and the first message is at the bottom. FreddyAI reads from top to bottom, so it starts with the answer and ends with a question when summarizing the ticket Would be great if it could recognize an email chain or has an option to reverse the summary order
I think it would be really beneficial if within the Assets custom fields, you would be able to get drop-down menu items from a data source.Additionally, new field type Multiselect would be appreciate as well!
HiToday, Workflow can be based on tickets, problems, release, assets…We are not able to base on users (requester and agents) valuesYet this functionality will be helpfull with OffBoarding.For example, generate an alert to the manager when the end of contract is reaching (could you confirm or do you want to extend it ?)» Could you able to create WF based on user data ?This is very important to improve OffBaording module
HiIn OffBoarding form, we need to fill all fields about the user who leaves.These actions are not necessary since all data are in his profile» Could you just define a field where we could search a user. We select the leaving user. Then FreshService fill all fields with his current values (departement, function, locations, name, first name, manager, etc...)
HiCosmetic is very important from end-user point of viewToday, there are three satisfaction icons (yellow, yellow, green). These colors are not clear from end-user point of view» In order to be more user centric, could you purpose more icons ? (red, yellow, green)
HiCosmetic is very important from end-user point of viewToday, the available values for Impact and Urgence data are Low / Medium / High.These values are not always clear for end-user» In order to be more user centric, could you create a label for these values (= Low, Medium, High) and show these labels in incident form ?
HiIn OnBoarding form, all locations values are available in the Location field.Often we do not use all these locations and/or some of them are just used to organize these locations.» In order to be more user centric, could you hide unused locations in the form (not in the organization)
HiToday in FreshService, articles in the KB are showed automatically depending of the words used by the requester in “Object” field. I undertsand because this is the new and modern way of working?Yet numerous of our end-users are not familar with this way of working. They like to be guided and binary way of working.» Could you show the KB articles depending the choices about Category/Sub-Category in the Incident form ?This would be more user centric
HiIn FreshService, to access to dashboards, a user needs an agent licence. OK. But he needs to use back office screen for that.Yet we need to share some dashboards with directors, managers or end-user… Back Office screens are not end-user centric for them.» Could you share the dashboards directly in the Portal ? Very important for IT team to share data/analyze with business. So very important these screens are nice - Be able to define some favorite depending the user - Create new type of licence for these users ?
HiIn FreshService, we find “Tickets”, “Change”, “Release”, “Problem”… like type of tickets.Each type has its own setting.Unfortunetaly “Tickets” type groups INCIDENT and STANDARD REQUEST wheraes these two sub-types are very different. Therefore they share the same label, category, sub-category, email, etc….This common setting is difficult from cosmetic point of view (= for end-user)» Could you split the settings of these two types of tickets ?
HiI need to create some analytics reports based on user (requesters and agents) data and filterred by DepartmentDepartment field exist on User profile page but it seems that there is no link between Department and User in the analytics tables.That’s strange since this link exist between Asset and Department.» How to filter requester by Department ?If not possible, could you integrate this functionality in a next release of FreshService ?» Important, this filter has to be able for other elements (for example : be able to filter software by User Department)
For data analysis and auditor purposes, it would be super helpful and useful to export all the information within a requested item. Currently, if an auditor requests information, we have to print to pdf the tickets one by one since the data export does not include the requested item information.
In the ever growing regulation and compliance required world the current custom Roles in Freshdesk in limited. The ability to remove Agents from having access to edit Notes is locke out. for our business this is just not acceptable as staff are able to edt notes and no real Audit history is recorded. This means that no time tracking on the note of when it was first created, what was in the note at the start and what was edited in the note as well. For this reason I dont understand why the platform does not allow us to remove this ability in Customer Roles, its locked out, and to me that is not having the ability to Customize Roles to our business to allow us to meet the Regulations and Compliance needs that we as a company need to follow under local laws.
I need my automation to check whether the latest reply came from a certain email that is not necessarily the requestor or the agent.
I think it would be much appreciated to disable the Send button when creating new e-mails until the attachments are being uploaded. Currently if the added attachment is still being uploaded and the users hits the Send button the e-mail gets sent without the attachemnt, the user has to create another reply to send the attachment. I would reccomend disabling the option to click the Send button when the attachemnt is currently being uploaded or to wait for the Send button action until uploads are completed.
I would like to be able to view tickets and associated service items in reporting and analytics. Currently, only the Service items when requested via SelfServicePortal are visible.As a workaround, we have to automate using tags when adding service items
RequestA percentage deflection metric made from the inverse of:Number of portal sessions that included submitting a ticketDIVIDED BYNumber of portal sessions that included viewing an article Example40 sessions to the portal that included submitting a ticket100 sessions that involved viewing articles= 60% deflectionWhy?As an admin, I want to know how effective my content is. The article ratings are useful but only capture a very small percentage of users.
Often we are required to save a client's password or his credit information, I think it would be fantastic to create a customized note field for the agent to be able to specify the client's private data there and the field would be locked using a password or a predefined 2FA authentication
We have some scheduled tickets created that should include a checklist that the agent must fill in and re-upload. It would be ideal, to be able to attach the template document within the ticket upon creation through the scheduler or through a workflow
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.
