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.
I would like to suggest that the following is considered for better Software Contract and License management: Short description: Allow (software) contracts to have a hierarchy with primary, secondary and tertiary contracts.In addition, allow the Installed function (an automatic feature) and the Users function (a manual feature) to both consume licenses from the Software License Count in the associated contract(s), including if in a hierarchy. Or create a dynamic association with the machine installed and the detected user? The manual assignment of Users to licenses are tedious and ineffective, causing this module to be fairly useless. (As a case in point: I have implemented Freshservice in 4 different companies that I have been IT Manager for in the last 8 years, and none of them could effectively implement and use the Software Tracking and Contract management modules, and opted for another solution...This does mean that in the Contracts Module will need to calculate the total of all licenses purchased or removed and report on it as such. We have used the "Relationship" feature, but again it is manual at best and extremely labor intensive and it does not maintain license numbers and cost.Example:Component Association to Main Contract:Tracking of Licenses and financial calculations currently only works with the first line entry of the contract. It does not calculate the individual additions/removals. To illustrate, I will use an example we came across in our business (multiple times in different organizations).We have a number of licenses covering different components of a solution, each licensed and tracked separately under a single license agreement (and in fact a single solution).Ideally the Contract should therefore look like this:It does make sense to have separate "Dependent" contracts related to the master (if the above does not work and if each component has different license agreements and/or purchase/renewal dates), as the software tracking will need to understand that the detected licenses for actual installs needs to be allocated to the "Dependent" contracts, but roll figures up to the "Master" contract. Especially if hierarchical software (incl budgets) is managed by different individuals. This should make your implementation of such a feature much easier. This could be true for a service agreement (MSP) with multiple services (with different SLA, agreements, implementation/renewal dates, etc) as well.Additionally, there is a glaring shortcoming to the software tracking and contract management modules. Currently your tracking solution (automated discovery) uniquely lists every detected piece of software with version and publisher information, which is great. The issue is that often the information in the detected software install is different as the version data changes over time. Example:WebStorm is installed on 5 desktops, one is listed as WebStorm 2023.2.1 and the others just as WebStorm. This duplicates (or even many times over) the entries for a particular piece of software. It is essential to know which versions are installed, but it would be great to be able to have a single master entry associated with the contract to accurately calculate consumption & usage and have the ability to associate other detected versions (possibly with a RegEx for automation) to this “Master”.In context of my suggestion:Master Software: JetBrains SolutionTotal License Count to be used for allocation and tracking: 28 (= sum of all of the below) WebStorm 2023.2.1 = 5 LicensesWebStorm = 15 LicensesDataGrip V1 = 3 LicensesDataGrip Vx = 5 Licenses This will greatly improve the efficiency and accuracy of software licenses/contract tracking and management and will, in fact, make the Software/Contract/License part of your solution truly professional. It will provide Freshservice customers with a single view of Software Contract Tracking, cost and actual utilization. Currently it is mediocre at best, sadly. It is almost easier to use a spreadsheet or another solution.
Currently, when you send a reply as an agent directly from your mail client (i.e. Outlook), it is added to the ticket as a Public Note. I temporarily worked around this by setting up an automation for ticket updates, but it results in the same message being sent as a note and reply. Workaround for others interested:Event: AgentAction: Send email to requester AS A reply in the existing email Hello {{ticket.contact.firstname}}, {{ticket.latest_public_comment}}Regards,{{helpdesk_name}} support team
Is there a way to add a field to a report that shows you the last time a ticket was opened/viewed but nothing on the ticket was changed or saved? We have an aged ticket report and want to see if tickets are just being ignored or if someone has viewed but not taken any actions on the ticket
Would like the ability to store data at the agent level. You have custom fields at Company and Contact - I would like the same for Agents
Hi all,We recently started using skill based automated ticket assignment for one of our support teams. This feature has added a new ticket field in the ticket properties section called “Skill”, which only appears if a Group associated with automated ticket assignment is selected.When a Group that has automated ticket assignment is selected in a ticket, in this case the “Assignment Testing” Group, then the “Skill” ticket field appears.When a Group that doesn’t have automated ticket assignment is selected, then the “Skill” ticket field doesn’t appear.Our support team managers prefer that agents don’t need to scroll through a bunch of ticket fields in the properties when handling tickets so that they can instead focus on answering questions and resolving tickets as efficiently as possible. Because of this, we are using an app in Freshdesk called Hide Fields which hides many unnecessary ticket fields from the ticket properties. The fields are still preserved for reporting but agents don’t need to scroll past all of them or fill them all out when resolving their tickets.Unfortunately, this new “Skill” field is not available to hide in the Hide Fields app. It is also not visible in the Ticket Fields page in Admin, so I’m unable to order it at the bottom of the ticket properties and out of the agents’ way.This causes a great annoyance, as the fields have all been shifted down due to the new “Skill” field being where it is and the agent’s muscle memory causes them to click it by accident or taking extra time to find the field they were actually looking to edit. It is also another field to have to scroll through, which our managers want to avoid.Please consider allowing the “Skill” field to be hidden through the app or its position to be edited in the ticket properties so that it is out of the agent’s way.
Currently only the following parameters are taken into consideration when activating the advanced mail setting ‘Create a new ticket when subject line changes’:FWD:RE:FW:[EXTERNAL SENDER\]:EXTERNAL SENDER:EXTERNAL:\[URGENT\]:\[EXTERNAL\]:\(EXTERNAL\):\[EXTERNAL\]:EXT:\[EXT\]:RES:ENC: We kindly ask you to add AW at the earliest as we have a lot of German speaking clients and adding AW in front of the subject is creating a new ticket every time. It would be great if not only English parameters are supported.
In a dynamic work environment, it's common for agents to move between departments or leave the organization. This can create gaps in our knowledge base management, as articles owned by these agents may become outdated or unmanaged. To ensure continuity and maintain the quality of our knowledge base, I propose a system for the mass re-assignment of knowledge base articles when an agent is no longer onboarded or moves to another department.Proposal: Automated Detection: Implement a system to automatically detect when an agent leaves the organization or transfers to a different department. Trigger an alert to the knowledge management team upon detection. Re-assignment Workflow: Develop a workflow to re-assign the articles owned by the departing or transferring agent. Allow for bulk re-assignment to a designated team or individual responsible for the knowledge base. Notification System: Notify the new owner(s) of the re-assigned articles. Provide a summary of the articles and any pending updates or reviews needed. Audit and Review: Schedule regular audits to ensure the re-assigned articles are up-to-date and accurate. Implement a feedback loop for the new owners to report any issues or improvements. Benefits:Ensures continuity and accuracy of the knowledge base. Reduces the risk of outdated or unmanaged articles. Streamlines the transition process for knowledge management.
Hoy en día, aprender matemáticas puede ser mucho más sencillo gracias a herramientas online como Calculadora Alicia. Esta plataforma está diseñada para ayudar a estudiantes de todas las edades a resolver operaciones básicas de una forma visual y educativa. No solo ofrece resultados rápidos, sino también una explicación paso a paso que facilita la comprensión.¿Qué es Calculadora Alicia?Calculadora Alicia es una calculadora en línea gratuita que permite realizar operaciones como sumas, restas, multiplicaciones y divisiones. A diferencia de otras calculadoras, muestra todo el procedimiento, ayudando a entender el proceso completo y no solo el resultado final.
The Closure or Business Rules should include an optional condition requiring the following for ticket resolution or closure: Any pending approvals to be updated or cancelled The status of any Requested Items to be marked as (Delivered/Cancelled/Fulfilled/Partially fulfilled), rather than allowing the status to remain 'Requested’
My customers would like to be able to have improved sorting in their customer support portal.One sorting option that would be really helpful is to filter ticket status the same way agents can - preferably the “Unresolved” option.This will allow customers to easily discover all their open tickets with us in a faster and easier way than using existing sorting options.
CSAT Surveys are never sent to AGENTS (https://support.freshdesk.com/support/solutions/articles/225424-why-the-customer-satisfaction-surveys-are-not-being-sent-). We have several GROUPS in our Freshdesk where the AGENTS in one group are often the REQUESTORS of other groups. This severely limits survey functionality since we won’t get CSAT Surveys to most of our REQUESTORS. I propose that the scope of this restriction be configurable in the hands of tenant admins. I’d like to see options like:No agents can receive survey links. (CURRENT DEFAULT) Agents outside the GROUP of the ticket can receive survey links. Agents in only these GROUPS can receive surveys (selection box to choose groups). All Agents will receive surveys. Warning: this means agents can fill surveys of their teammate possibly padding stats.
It would be great if when reviewing a workflow from a ticket/change/etc., if there was a intelligent pathway that highlighted the route the ticket took in the workflow and call out where in the workflow it failed, without having to go through the execution log.
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.
