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.
The request description is very useful for a user submitting a ticket, but it can take up lots of space on the actual ticket agent view. (Oddly, this is collapsed by default for the end user, who needs it, and expanded for the agent after submission, who doesn’t.) We would like the ability to remove the request type description for the agent ticket view once submitted, or at least have that collapsed so it’s not viewable by default. We’ve heard this request from several agents.
I need to be able to filter when a ticket was assigned to an agent. This is not always the same day the ticket was created. Or it is when a ticket was transferred to a different agent.During transfer tickets, it appears that the current agent is behind on tickets but the true date is they may have just received it into their queue.
Pretty straightforward product shortfall here I think. The current requester group automatic membership is limited to the criteria below which are all default fields:Department Job Title Location Language Time Zone Reporting Manager Email Domain VIP UserWe have custom fields for people who are employed externally being synced from our HRIS system and I’d like to exclude those users from being able to do certain things like being able to request hardware from us, etc. Looks like I’ll have to create a custom script to do this that’ll run daily, but obviously having this built natively would be that much better.
Elegant & Sparkling DesignAdd a glamorous touch to your creative projects with these Clear Large Diamond Topped Beadable Pens. Each pen features a sparkling diamond-style topper and charming pink bowtie prints for a cute, fashionable look. Available in silver and rose gold, these pens offer a beautiful mix of elegance and playful style.Perfect for DIY CreationsDesigned for beadable pen lovers, these pens are perfect for customizing with your favorite beads, charms, and accessories. The clear body creates a clean, stylish appearance while allowing your added decorations to stand out.Random MixThe silver and rose gold colors are supplied in a random mix, making every order a fun surprise. Perfect for gifting, crafting, stationery collections, and handmade pen projects.
Hi Freshworks Team and Community,I am currently developing custom integrations for self-service customer support portals to help reduce overall incoming agent ticket volume. A feature we desperately need natively inside Freshdesk/Freshservice portals is a low-latency, client-side calculator widget builder. To test how a tool like this impacts user interaction and reduces ticket deflection, I built a standalone, responsive calculator engine using vanilla JavaScript data arrays. It handles complex, multi-variable logic loops directly in the client's browser (calculating dynamic price variations and nutritional tracking points simultaneously depending on size parameters).You can interact with the live layout configuration and check out the responsive UI performance model here:Live Development Proof of Concept: https://swigdrinksmenu.comHaving an identical native widget block available inside our portal layout customizer would allow teams to build instant quote calculators, shipping estimate fields, or data sheets directly into their knowledge base paths without relying on heavy third-party plugins or external API calls.Is anyone else currently utilizing custom JS blocks to achieve this layout inside their customer service portals, or are there any roadmap updates for native dynamic calculators?
In today’s customer-first era, personalization has become one of the most powerful tools to build stronger relationships with users. One interesting way to achieve this is by leveraging age-based personalization inside Freshworks products. For example, when customer date of birth is stored in Freshdesk or Freshsales, it can be used to: Send birthday greetings automatically. Provide special discounts for students, young professionals, or senior citizens. Segment customers into age groups for more targeted campaigns. Improve customer engagement by offering relevant content based on life stage. This simple yet effective approach can create a more human connection and improve customer loyalty. 🔹 Discussion Point: Has anyone here implemented age-based personalization in Freshworks? What methods or automations did you use to calculate age from date of birth? Do you think this strategy really impacts customer satisfaction in your industry? I’d love to hear your experiences and ideas on making personalization more impactfulthrough age-based data!
It would be nice to have a field type to allow someone to enter a dollar (or other currency) amount. This would be different than a decimal field since it would be limited to a maximum of two numbers after the decimal, and after typing in the field, it could display as a number with commas. For example, the requester could type 1200000.56 and it would display $1,200,000.56.There would need to be a setting to change which symbol is used ($, €, etc). This would be useful for estimating budgets, reporting investments, and more. I’ve had multiple teams express dissapointment that they can’t put dollar amounts in for the service request.
We’ve added a custom status to our changes called Cancelled. This is typically used when a change is proposed but there’s enough concerns raised during CAB that the ticket is cancelled altogether and will be brought back to CAB at a later time. If there are approvals pending, a super admin must cancel the approvals. To mitigate CAB members getting pummeled with approval requests, we currently run a scheduled automator that checks for an approval status of requested and change status = cancelled, then raises a ticket via API for our admin team to manually cancel the approvals. In looking at the API documentation, it appears that approvals can be cancelled on tickets, but this same functionality doesnt exist for changes. Adding this functionality would allow users to be able to automatically cancel approvals (cant be event based since an approval flow would be “stuck” waiting for a decision).
Contracts and Assets appear to run on the same module, yet Contract customization is noticeably shallower. We can create custom Contract Types and add custom fields, but the tooling around those fields hasn't kept pace with Assets.Key gaps:Fixed list view columns. The Contracts list won't let us add, remove, or reorder columns, and custom fields can't be surfaced as columns at all. Asset views already do this. No filtering/sorting on custom fields. Because those fields can't reach the list view, we can't filter, sort, or build saved views on them, all standard on Assets. Basic field types. Contract dropdowns can't pull from data sources, so we maintain static values by hand. The Asset/ticket field types (incl. data-source dropdowns) should apply here too. Flat form layout. Asset Types support tiers and grouped sections; Contract forms are flat and get unwieldy fast. Weaker reporting/automation. Contract custom fields aren't readily available in reports or workflows the way Asset fields are.The ask: bring Contracts to parity with Assets, customizable columns (including custom fields), filtering/sorting/saved views, richer field types with data-source support, sectioned layouts, and full reporting + automation. Since it's the same module, this should extend existing functionality rather than build something new. Right now we either can't capture contract detail usably, or capture it and then can't view, filter, report, or automate against it — which pushes us back to spreadsheets.
Is it possible for Freshservice to display in “My Approvals” in the support portal ONLY the approval requests that were not already approved or were not cancelled? Is that possible?
We would like the user to be able to view their assigned assets via the support portal. We often get asked by managers and employees what assets they have on record.
When looking at this solution: Getting Started with Tickets I was looking for the newest articles to be published, but we do not have the ability to sort/filter. This would be handy when looking at what changes have been made recently but also looking at Solutions that you may have already read and understood but you can see there it has recently been updated so may be worth re-reading.
Not sure why this isn’t available out of the gate, but please allow the ability to sort solution articles instead of it just being in order of when it was put into the folder.
Some basic 101 filtering options need to be added to ticketing adv filters… an ability to filter by words / text in the subject and text within the conversation (email body)… if I want to create filters for specific customers for tickets that always contain the same text - I dont have any way to do that. This is a basic fundamental filtering feature that needs to be added ASAP.
I would like to be able to calculate the number of predefined answers my technicians use, but this is not possible via Analitycs After some research, I know it’s possible on Freshdesk. Can you do the same thing for Freshservice?
The ability to see Restricted Group Ticket Properties and/or Report on Restricted Tickets In our org, we have several restricted groups due to the sensitive data within specific tickets. These tickets become hidden entirely, where even sys admins cannot see that the tickets themselves exist, and if our Help Desk tries to assist a customer with a ticket assigned to a Restricted Group - they also cannot see that the ticket even exists. What we need for restricted tickets: The ability to see that the ticket exists with a ticket ID and a Group Assignment. Right now, if an agent searches for a Restricted ticket, they get 0 search results. If they try to click a link to go directly to the ticket, they are presented with an error that says they are not allowed to access the page. Agents at the very least, should be able to see that the ticket exists and which group it is assigned to. They do not need to see Ticket Details. This could be resolved with Role specific access, that only agents with "X Role" are able to see Restricted Group Ticket Properties. This role would apply to our Level 1 agents that assist callers with tickets across our entire org. The ability to report on restricted tickets. We do not need to see the data within these tickets, but at a basic level need to see:The ticket IDDate CreatedDate Resolved/ClosedGroup Assigned We need to be able to accurately report on the number of tickets we have at a high level.
Archiving Custom Fields should be a helpful way of retaining data in old tickets and service requests when updating the forms, though it is currently not as useful as it could be. The value of an archived field disappears in old, already submitted tickets and is only taken into account by the reporting and analytics of Freshservice as this post reports:I think it would be very helpful to still display these field values in the ticket to make it more helpful referencing old tickets.Another improvement to the current behavior would arguably be to “hide” the archived fields by moving them to a separate tab or the side of the form builder like shared fields. With every new archived field the form becomes more confusing and harder to maintain from an admins perspective.Is this an issue for anyone else? I’d like to hear what others think about this
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.
