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.
HelloAs of today Businesses agents can’t create change as they don’t have access to the Change module by design. So if Businesses agent need to create a Change they need a extra requester account or be change to a IT agent. My suggestion would be that they get access same as requester’s get the end user portal.
More griping:why are Tasks only visible in a separate list? It would be useful to have tickets and tasks in the same screen, and SORTABLE by Agent, ticket #, Category, etc…..In the existing tasks list, there is no method to sort the tickets displayed. It would be great to have some indexing, by ticket number, agent assigned, etc.
Current LimitationCurrently in Freshsales, when setting up dependent fields, the dependent field is automatically positioned below its parent field in the record layout. While this relationship makes sense logically, it creates limitations in designing optimal layouts for our teams' workflows.Use CaseIn our organization, we need certain fields to become required based on other field values, but we want to maintain our carefully designed layout that groups related information together. The current dependent field functionality forces us to compromise between having conditional requirements and maintaining an intuitive layout.Proposed EnhancementAdd the ability to make fields conditionally required without forcing them to be repositioned in the layout. This would:Allow fields to become required based on other field values Maintain the field's original position in the layout Preserve our ability to group related fields together logically Keep our forms clean and intuitive for our usersBenefitsImproved User Experience: Users can work with forms that maintain a logical flow and grouping of information Better Data Quality: We can still enforce data requirements when needed Flexible Layout Design: Administrators can create optimal layouts without compromising on data validation rules
Using MSP mode, no outgoing email setup, only use notes to update tickets, it would be useful to be able to add the ‘contact’s’ email address into the ‘notify to’ area when adding a note onto the ticket. Sometimes the ‘notify to’ person is different to the person who logged the ticket. At the moment it only allows Agent names to be added
It would be great if data labels where visible also on grouped bar chart in Analytics where you have >1 group by. Example 1: only 1 group by and data labels are visible Example 2: 2 group by and no data labels are visible
Hello,It would be very helpful to have a bulk update option for customer contacts in Freshdesk. Currently, actions such as sending activation emails, granting access to view all tickets of the organization, or updating the timezone must be done individually for each contact person, which becomes time-consuming when managing many users under the same company. It would be great if these kinds of updates (and other contact field changes such as phone, company, or custom fields) could be performed in bulk. Is there any plan to add this functionality, or could it be considered for the roadmap?
Our org would like to require tickets to have a note on a ticket before being transferred into another group. I realize this may be difficult if a ticket bounces around quite a bit, but considering orgs tend to have a T1/T2/T3 setup, it’s logical to think that you could use Agent Interaction count to drive this, but this isnt possible in Business rules. An example:All conditions match the below:Ticket Forms.Group includes T2- Service Desk, T2 - Phone support, T2- Infrastructure teamCurent Ticket.Agent Interactions is not at least 1Validate form on submission:“Please leave a note on troubleshooting steps taken so far prior to escalating to the next group” We could do this with automattors but it would result in an automation being needed for every different group that exists in the org as a trigger (If group is updated from T1 - Service Desk to Any group and condition of agent interactions is 0, return to T1 - Service Desk)
We are desperately needing better Task Management in Freshservice. The Tasks module section is laughable. The fact that you can’t even filter by status for all Task types in Freshservice is insane.I’m looking for a Board view of all Tasks regardless of it’s Parent.Also/Alternatively, have those Task sync (two way) with MS Planner and just hand off that Management.
I’m looking for to create a report that provides insights into the aggregated ticket volume over the last time period. Specifically, I want to create a line chart that shows:The data aggregated number of created tickets for the past 30 days, rolling backward from that given date in the time period selected.It would mean I can select as an example Tickets created last 30 days, and then select By week and Last Quarter, and I would get a line chart where the data point is the start of every week over the last Quarter, and the aggregated number of created tickets over the last 30 days from everyone of these dates. Example:On 25.11.24 - 530 tickets has been created the last 30 days.On 02.12.24 - 560 tickets has been created the last 30 daysOn 09.12.24 - 600 tickets has been created the last 30 days.etc etc…This data should be used to create a chart (I prefer a line diagram for this specific data) to represent accumulated ticket volume over time, so that I can understand if our ticket volume has been increasing or decreasing.I do not want to see how many tickets was created day by day, or week by week.
Context:A few years ago, Freshworks offered a visualization feature that allowed users to include tabular ticket data in PDF reports—essentially a summary table showing ticket attributes. This was incredibly useful for generating readable, graphical reports for customers and internal stakeholders.Unfortunately, this feature was deprecated around mid-2021. Since then, newer accounts no longer have access to this functionality. The current workaround—exporting data as CSV—is not ideal for many users and lacks the clarity and presentation quality of a structured PDF.Thread in the community: Report view tabular | Freshworks CommunityCurrent Limitations:No option to export ticket data in a readable, graphical PDF format. The “Underlying Data” feature does not support PDF export, making it an incomplete replacement for the removed tabular view. CSV exports are a workaround, but not user-friendly for all regions or use cases.Why This Matters:The removed feature was not redundant—it served a distinct purpose that is not currently met by any other feature. Many customers rely on clear, visual reports for audits, compliance, and internal reviews. The lack of a tabular PDF export significantly reduces the usability of Analytics for these purposes.Request:Please consider reintroducing the tabular data visualization feature for PDF reports or provide an alternative that allows exporting underlying data in a structured, readable PDF format.
To enhance the efficiency and management of the helpdesk team by providing a centralized dashboard for tracking and managing all pending approval requests for others For both SRs and Changes. A centralized dashboard on the helpdesk platform that aggregates all sent approval requests. This feature will allow the helpdesk team to have a comprehensive view of all pending requests, facilitating easier follow-up and management.Key Components: Dashboard Overview: A dedicated page accessible from the helpdesk main menu. Summary section showing the total number of pending approval requests. Filter and search options for quick access to specific requests. Request Details: Each request entry should display: Request ID Requestor's name and department Date and time of the request Request type/category Current status (e.g., Pending, Approved, Rejected) Approver(s) assigned Hover or click to expand for additional details, including the request description and any attached documents. Filtering and Sorting: Filters for request status, request type, department, and date range. Sorting options by date, requestor, status, or urgency level. Notifications and Alerts: Automated notifications for pending requests exceeding a set duration (e.g., 48 hours without action). Highlight overdue requests in red or with an exclamation mark for urgent attention. Actionable Insights: Metrics and analytics section showing trends (e.g., average approval times, most common request types). Ability to generate and export reports (e.g., monthly summary of pending and approved requests). User Permissions: Role-based access control to ensure only authorized personnel can view and manage the dashboard. Differentiated views for helpdesk team leads and regular team members.
We can create ticket views and share those views to all agents, or an agent group. But its limited to just one selection. We would like to be able to share the view with multiple agent groups at once. This would save time from having to duplicate the view just to share it out with another group.
avi tag sequence fusion proteins are engineered recombinant proteins that incorporate a short, 15-amino-acid peptide sequence (Gly-Leu-Asn-Asp-Ile-Phe-Glu-Ala-Gln-Lys-Ile-Glu-Trp-His-Glu) at the N- or C-terminus of a target protein. This tag is specifically recognized by the biotin ligase enzyme (BirA) and is enzymatically biotinylated at a designated lysine, ensuring a single, well-defined biotin attachment. The result is a uniform, functionally active protein that maintains its native structure while gaining the capacity to bind avidin/streptavidin with very high affinity.
Hi everyone, We have been getting more questions/requests from our users about using emojis and special characters (mainly those “black dot” bullet points when they want to provide a list) for several fields we have in Major Incident tickets and Service Request tickets. Anyway, not a priority at this point but I did notice that we get more questions on it so decided to post here to suggest this or to hear if it’s a possibility just in case. Thank you!
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.
