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.
Option “Create Child Service Requests for each of the items above“ is active. One of the child Items is required to have attachments (which is also activated in the corresponding Service Request item)But unfortunately when requesting the parent item and selecting the child items, you only can attach files to the parent item!Please make it possible to attach files in the child items. In the “Bundle” where the additional service items are, when you click on them and the associated form for that item presents itself you should see “Add Attachments” as a part of that form. related question:
Feature Idea: Hourly Ticket SchedulerCurrent Behavior: The Scheduler allows automated ticket creation at daily, weekly, monthly, and yearly intervals. Requested Enhancement: Add support for an hourly interval, so tickets can be generated every hour (e.g., “at 00 minutes past each hour”). Use Case: Automated health checks or data imports that need to open tickets immediately when an hourly threshold is met. Ensuring prompt visibility for issues or maintenance tasks that occur on an hourly cadence without relying on external cron jobs or scripts. Benefits: Full in‑platform scheduling flexibility across all common time intervals. Simplifies workflows by removing the need for external scheduling tools. Improves responsiveness for time‑sensitive monitoring and operations.
Is there a way to add “To-Do” as a View or a Filter so that all “To-Do” items are listed in a list? Just viewing and scrolling through the very small window on the dashboard is very cumbersome as this small window cannot be expanded. Small TO-DO Window on Dashboard
It would be a great idea to be able to reuse announcements. This would save lot of time in drafting a new announcement. Additionally, it would be wonderful recurring regular announcements can be scheduled as recurring. E.g. Monthly system update notification sent few days before the fixed monthly announcement schedule.
We have a lot of our service items automated through web requests and API calls. I would love to see a way in the workflow automator to select a “Delay Until” timer node.Example use case:We have a Agent Access request form in our catalog, where people can request for an existing or new hire to receive an Agent License. They select which agent group(s) the person will need to be assigned to and we have standard agent roles for each agent group. They also indicate when the agent access is needed. In the event of a new hire, it is often 2-4 weeks in advanced.Benefit:With a “Delay Until” timer node, we could have the workflow pause on the request until the start date and then use Web Requests in the automator to create the Agent account or convert the requester to an agent, then add them to the appropriate agent groups and agent roles, without any manual touch.
When building workflow automators, it would be beneficial to have State as a useable value. Being able to use “Customer Responded” to be able to trigger events for agents would help bring awareness to a response for agents can get back on a ticket.
When writing articles in the Solutions or knowledge base section of FreshService, it can be a dangerous game there is no auto save. Not sure why in 2025 there is no autosave but it sure does suck when you spend an hour working on something and lose it. You can’t even write it in a Google Doc and copy and paste because it loses the formatting. An auto-save feature should be top of the list, but the entire screen could use some modernization and formatting features.
The way we have to create Items in a strictly vertical fashion is a waste of space!! It makes some items VERY LONG when they could easily be 2 - 4 columns wide. Base it on a grid and allow the ability to click and drag the shapes around easier. My previous software allowed that and it made for a much nicer format in a smaller area.
While creating new email, we have option to add only one email address in To column, we want option to add multiple email addresses, if want to address multiple people.same as it has option to add multiple email addresses in CC column.
It would be very helpful to have an Agent Role to create Vendors, possibly an option in the Procurement Manager and Contract Manager Roles. It seems a bit overkill to require an Admin to add vendors as staff continually make purchases from various vendors or enter into contracts.
Currently, we can use the ‘Push to Teams’ action in many of our automation rules as a way to connect with people that aren’t involved with customer support every day. This action does not appear to be available in Scenario Automations.For example, if a customer adds a CSAT rating and comment, it is posted in the ticket. Some comments are worthy of posting to teams where other business units can follow along or reply - but it really depends on the context of the comment. We would like agents to be able to execute a scenario that posts to the appropriate channel in teams without having to go through all of the steps each time.
Hi,this is an easy thing and it will help to all of distracted technicians, who just add a note and realize that the note should be public from private and vice versa. If it will be possible in no more than two clicks, it will be great!.In these days you have to delete the note and write it again with the correct private/public settings.Thanks :)
I would like to put forward to have the ability to include additional columns from the Assets fields within the Ticket - Asset Association process. This way, if we have multiple assets but for different, specific locations, we can identify them easily.
There are many use cases for using the data source feature of a drop-down selector field inside a service request. Currently however, they are too permissive/expansive for our data privacy and simplicity needs. For example, I would like a requester to be able to select a colleague/subordinate from the “requester” data source to make the process more accurate and faster for everyone. But, we only have the choice of a filtering by requester group or other ‘hard coded’ attribute like department. This means If I want to restrict staff in HR to only being able to select a colleague, I’d have to make an SR per department and make them department specific. I think we should have the ability to add dynamic filtering that works in the requester’s context. e.g. the below would let us have 1 form for all staff that shows only the relevant colleagues to them. We are also wanting our parents to only being able to select their child when doing an SR. Currently, if we use the requester group = Students…. they can choose (and see the email address) all our 2700 students. This is far too permissive and forces us instead to use a ‘dumb’ version where they have to type in their child’s name or email. Additionally, agents are often not selectable in these requester filters. We are using Freshservice as an ESM and have 110 agents across many different internal teams. It is not just IT staff as agents. We need agents to be selectable in these filters. Filtering is also needed for the data source “Locations”. We should be able to filter in/out locations so that people can only select relevant locations to the SR and not all. And again, filtering is required in the assets data source. We should be able to add a user-context filter that only let’s them select from the assets assigned to them or their department etc. This way they can accurately select items that might need servicing.
We are starting to heavily use the Solutions area of Fresh Service. Some features we would like to see: Allow customer facing solutions home page to view articles by: alphabetical, date published, category, tags, folder, etc... Search results to show more information: date published, tags, category, folder, etc… More options around solution status (DRAFT to Publish). Need ability to edit a published article without the published version of solution switching to Draft status. If published solution is in draft status for weeks while it gets updated to version 2, I need the published version 1 to still be accessible to customers.
Hi,Refreshing an idea here, as I previously raised in Question section with a similar context.We have a customer who asks for these features in Freshdesk Support Desk (formerly Freshdesk) and Freshdesk Contact Center (formerly Freshcaller):The capability to have a dashboard widget on time interval basis for ticket. For example at 08.00-09.00 How many ticket is Open, Overdue, Resolved and Closed and the same with 09.00-10.00 and so on. The capability to have time Interval field in the analytics report for ticket, and call module. This discussion has been raised on a Support ticket ID: 11517765 as Feature Requests with Freshdesk team and we were suggested to raise this discussion on the Community Forum that display a case might be related to other global customers/ users of Freshworks so these features can be possibly determined in the future product roadmap. Please keep us updated.Thanks.
✨ What is the feature?Allow API access to the same fulltext search capabilities available in the Freshdesk UI. Specifically, enable searching tickets by subject, description, and ideally also conversation content, similar to how the internal /api/_/search/tickets endpoint works with { term: "...", context: "spotlight" } - in the UI, this is what appears when you type in the “search” field (magnifier icon, top right). 🔍 Why is it important? This search is available in the UI but not via the public API, which is inconsistent and frustrating for automation. There’s no way to query these fields via /api/v2/search/tickets or filter tickets by custom fields (if the field is too short, e.g., 255 characters). Automating ticket audits, tracking frequent issues, or building support insights becomes impossible unless you manually export everything or reverse-engineer internal endpoints using cookies/sessions. Has been requested before several times, 📦 What we tried Tried using GET /api/v2/search/tickets?query="subject:xyz" → doesn’t work; subject and description are not valid fields. Tried using internal endpoint /api/_/search/tickets (works in browser), but this requires a session token and CSRF token, which makes it unsuitable for stable automation (e.g. in custom apps using API keys). 🧰 Suggested solution Either open up the /_/search/tickets endpoint for API-Key-based use. Or extend the /v2/search/tickets endpoint to support subject, description, and ideally also conversations.
It should be possible to translate the system as well as the customer portal including the personalized fields, service catalog, knowledge database, etc. from a central location.We currently have the problem that the translations are very inconsistent and often outdated. We have to maintain the translations manually in many different places. Since Freddy AI can also translate conversations directly, for example, it should actually be possible to translate the rest of the content automatically. The current process is very tedious and takes a lot of time.
I would like to propose an enhancement to the SLA featureSLA Response target can be less than 15 minutes, for some case like social media we would like the response target within 5 minutes Selectable SLA due time reminders & escalation can be defined in weeks, days, hours and minutes, pretty much like the SLAs are currently defined. And we’re also looking forward to have the reminder less than 30 minutes so we can have more flexibility in configuring the reminder and escalationThanks
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.
