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.
In manager approval workflows, I think it would be a nice feature to be able to select if I want the managers remark text to be mandatory also for approvals.For rejections this is already mandatory (could be nice to have the option to disable that as well),
Maybe I am doing this wrong, but a lot of the integrations from the marketplace (and webhooks initiated in the automations) require a users api key. I think this is really poor practice, as a lot of the integrations are using my API key. So if I leave, that API key will no longer be available and all the automations and webhooks will break. Unfortunately there’s no static API key outside of a user granted in the freshdesk system, and I feel like it’s kind of insane to have to pay extra money for an additional user license to have this all not be a SPOF.
I have several monthly meetings with our customers to report on our helpdesk performance. Thanks to the great Analytics tool, I have compelling reports to show them about how we continue to give them fantastic support.However, all I really need is for them to have access to such a dashboard themselves. I build the report for them, and share the link with them. They can access it anytime and it would save my team a lot of work.As an example, it could be made a part of the customer portal - where I can not only raise a ticket or find an overview of existing tickets - but access a dashboard based on a report assigned to the specific customer - allowing me to fully view the report just like an analytic role can from the agent side.
One item I really miss from previous applications is the ability to filter the requester based on the value of department, location, or similar fields. Example: You may have several John Doe requestors, different emails, but the all work at different Locations or Departments. For both internal teams and MSP teams we should be able to select the Location or Department and then when selecting Requestor have the list filtered based on the entry. It would be a huge QOL for teams and save time in the verification process on the phone or chats. Been asking for this for 6 years.
Hello,Hope you are well.Just thought I would mention that if there are a lot of tickets being displayed on the Tickets view, the Horizontal slider bar scrolls out of view when scrolling up the ticket list.See images below: Horizontal scroll bar not available after scrolling up ticket listHorizontal scroll bar available after scrolling to bottom of ticket listIt would be helpful if the horizontal scroll bars position was fixed, so it could be utilised wherever a user was in the ticket list.Thanks
We would like to see a few new fields added to the General Details section of service items. We use the description field to manually create a few "sections" applicable to both requesters and agents that would be nice to make permanent fields. The ability to hide/show these fields to agents/requestors/managers would be key:request instructions - instructions on how to properly fill out the form below for the requested itemapproval process - list the owner, approver(s) and creator(s) for the service item including any related instructions/documentation about the request/approval process works so requesters know exactly what will happen after the request is submittedagent instructions - any instructions, typically hidden from the requestor form, that need to be provided to the agent(s) to fulfill this request such as next approval steps, etc.Not only would this information be great to provide/collect for requestors/agents but our service items effectively would become good change management documentation to support our IT process as well. In addition to this it would be great if the General Details section was always expanded by default when a service item page is loaded so users don't have to further expand it to see this information.
Hello everyone, As of today, the on-premises Active Directory Orchestration Server (SCIM) use SAMAccount as primary ID. It can cause issue if you remove users and reuse the SAMAccount. My suggestion would be better to use SID as primary ID when synchronize the users to Freshservice
I am curious if the ability for agents to ‘acknowledge’ incidents (low/medium priority) from the mobile app will be available in the future? Currently agents can acknowledge High/Urgent tickets via notification from the app via on-call events. We have agents that move between locations (different buildings, miles apart) and are not always in front of a computer.This would give those agents the ability to pick up and acknowledge tickets driving down acknowledgement time as well as providing service at the location they might be currently at in a quicker fashion.
We have separate portals set up for separate business unites. Currently, you cannot use Freddy AI if you are using separate portals. Please allow the use of Freddy AI for separate portals.
We have many IT agents with managers that assign those tickets. Managers currently do not have a quick way to group tickets by assigned agent. There’s also no way to sort by assigned agent. We used to have this in Zendesk before moving to Freshservice. Please add this ability to Freshservice. We have managers complaining about Freshservice and they are generally unhappy because of a simple feature like being able to group tickets by assigned agent.
When creating a CAB meeting, you can add the changes to be discussed during the meeting. Upon saving, an email is sent to all attendees. In that email, the default placeholder {{cab_meeting.change_list}} is added (see screenshot below). This placeholder contains a table with the following columns:Change ID Subject Planned Start Date Planned End Date Change Type Priority Risk Impact CommentsAt the moment, we have to enter the requester and change status manually in the comment field. The feature request consists of adding "requester" and "status" as columns in the placeholder {{cab_meeting.change_list}} so we don't need to enter it manually.
When creating an activity, it would be very helpful to have the ability to assign a task to someone who is not listed as a stakeholder on the journey. Ideally, tasks could be assigned to agents or other internal users, not just individuals included in the initiator form.In our organization, during onboarding and offboarding processes, there are team members outside of IT who are responsible for creating or deleting accounts. At the moment, we use activities to send email notifications to these individuals. The challenge is that there is no built-in follow-up, and we have no visibility into whether the request was actually completed.If we were able to assign a task instead of sending an email, it would allow us to: Ensure continued reminders are sent until the task is marked complete. Maintain a clear record confirming the task was completed. This enhancement would significantly improve accountability and tracking across departments.thanks
In general, we prefer to Default using the System address as the sender for Freshservice emails, replys and comments. However, there are situation where the Agent would prefer to have the email form a ticket or comment sent from their personal (profile) email address. An option to allow the Agent to select the sender’s (system vs the Agents) email for individual messages. Possibly default to system setting but allow user to select their profile address.
Instant response time is something all of us strive for, but that is very difficult to meet when interacting with human agents. As a chat queue increases, the response time increases and our customers start seeing messages like "Replying in under 2 minutes" or "Replying in under 35 minutes"While our customer is waiting for an agent to reply, can we allow our agents to play a small mini-game that can keep them engaged.
The Freshservice Ideas forum should be a living feedback loop between customers and Freshworks.Customers invest time submitting ideas, documenting real-world use cases, voting, commenting, and helping other organizations get more value from Freshservice. Many of us are also strong advocates for the product within our organizations and the broader community.For that model to work, the Ideas forum needs to be actively maintained.Ideas should be regularly reviewed and their statuses updated to reflect where they actually stand: Open, Considering, On Roadmap, Implemented, or not planned. Even knowing that an idea will not move forward is better than seeing it sit indefinitely without an update.The value is bigger than maintaining a webpage. It keeps the community engaged and shows contributors that their time and feedback matter.Customers contribute → Freshworks responds → the community sees progress → customers keep contributing.Freshservice has customers willing to share ideas, solve problems, help others, and advocate for the product. Keep that community strong by keeping the Ideas forum active, current, and connected to the product roadmap.
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.
