Skip to main content

Ideas portal FAQ

Find, vote on and share ideas for Freshworks products. Here is how it works and what happens next.

1. Idea stages and what they mean

Every idea has a status. It shows where the idea is today.

How does an idea move from submitted to delivered?
  1. Submitted
  2. Under review
  3. Planned
  4. In development
  5. Delivered

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.

What does each status mean?
Submitted
We received the idea. It is open for votes and comments.
Under review
Product is looking at the idea.
Planned
The idea is on the roadmap. We have not started building it yet.
In development
Our teams are building it. We expect to release it within 12 months.
Delivered
The idea is live in the product.
Future consideration
We are not planning it now, but it stays open. Votes help us see if demand grows.
Closed
We are not taking this idea forward. See "Why was my idea closed?" below.
Does Planned mean a release date?

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.

2. The basics: from your idea to our answer

Six questions most people ask before they post.

What is an idea?

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.

Should I search before I post?

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.

How do I submit an idea?
  1. Search. Choose Submit an idea and type a title. Similar ideas appear. Vote on one if it matches.
  2. Describe. Tell us the task you are trying to do and what gets in your way today.
  3. Add context. Pick the product area and tell us how much this affects your team. Add a screenshot if it helps.
  4. Submit. Your idea shows as Submitted.
How will I hear back?

You get an email when the status of your idea changes. To follow an idea you did not post, subscribe to it.

Why was my idea closed?

An idea can be closed for one of these reasons:

  • Merged. A similar idea exists. Your votes move to it.
  • Bug. It is something to fix, not a new request. Contact Support for help.
  • Retired. It no longer fits the product.
  • Already available. The product can do this today.
  • Not planned. We have no plans to build it.

Closed ideas stay searchable, so you can still read the comments.

3. Find ideas and share your thoughts

The quickest way to make an impact is to back an idea that already exists.

How do I find an existing idea?
  • Use the search bar on the Ideas page. Try two or three keywords.
  • Filter by product, so you only see ideas for the product you use.
  • Filter by status to see what is Planned or In development.
  • Sort by votes to see the most requested ideas first.
How do I vote on an idea?

Open the idea and select the vote button. Voting shows us which ideas matter to you. You need to be signed in to vote.

How do I add a comment?

Open the idea and add your comment. The most useful comments say:

  • What you are trying to do.
  • What stops you today.
  • How you work around it, if you do.

"I agree" helps less than a short example from your own work.

How do I follow an idea?

Select Subscribe on the idea. You get an email when the status changes or when someone replies.

I could not find my idea. What now?

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.

Ideas Status Pipeline

Filter by idea status

Filter by product

8951 Ideas

ITMike
Top Contributor ⭐
ITMikeTop Contributor ⭐

Notification for comments while in approvalClosed

Currently Freshservice suppresses workflow triggers from comments/replies while a ticket is in the awaiting approval stage.  This suppression makes it to where any questions asked by the approver and then answers submitted by the requester don’t notify the approver.  Automators don’t work because of the suppression feature. Asking for a feature to stop suppressing notifications or automating triggers when in the approval stage.  Example below:This scenario isn't for reminder purposes to approve an item, we do have that feature turned on and it does work as expected.  This scenario is for when the requestor adds a comment to the ticket either Ad-Hoc or in response to a question that the "approver" has asked.  Our approvers are missing information being given to them because nothing is notifying them that a comment/reply was added.  For instance, in the system ticket SR-XXXX. Approver asked the requestor a question and the Requester replied in the ticket.  Since I'm just the approver and not "assigned agent" of the ticket or part of a "assigned group" the approver is not being notified that the comment was added.We use approvals for every service request and in most cases multiple times per service request and quite often a conversation takes place, we are having a lot of misses and delays because the approvers aren't being notified.  Some of them have 20/30 approvals and I can't ask them to go through each individually to look for responses.

Mahdi.abuhait
Contributor
Mahdi.abuhaitContributor

SLA Consumption Tracking by AgentClosed

The current SLA (Service Level Agreement) system in Freshservice tracks the overall time taken to resolve a ticket but does not provide insight into how much of the SLA was consumed by individual agents who handled the ticket. This can lead to a lack of accountability and visibility when multiple agents are involved.Proposed Feature: SLA Consumption by Agent BreakdownThis feature aims to track and report the SLA consumption per agent on a ticket. When a ticket is handled by multiple agents, the system will calculate and report how much of the total SLA time was consumed by each agent during their ownership of the ticket. This will help provide a more detailed view of team performance and individual contributions.Key Features: SLA Time Tracking Per Agent: The system will automatically track the time each agent has ownership of a ticket. The SLA will be split and calculated per agent. For each ticket, a detailed log will show the duration the ticket was with each agent and how much SLA time was consumed during their ownership. Ownership Transfer Handling: When the ownership of a ticket is transferred from one agent to another, the SLA timer for the current agent stops, and it resumes for the next agent once they take ownership. The system will ensure the remaining SLA time is recalculated correctly for the subsequent agents. SLA Consumption Report: A new reporting feature will show SLA consumption by agent, detailing: Total time the ticket was in each agent’s queue. The percentage of SLA consumed by each agent. Total SLA time used up by the team in resolving the issue. Enhanced Accountability: By assigning SLA consumption to specific agents, it will improve accountability and allow teams to identify bottlenecks, inefficiencies, or areas for additional support or training. Integration with Current SLA and Reporting Tools: The feature will integrate with the existing SLA and reporting systems, allowing users to generate reports that compare SLA performance between agents. Custom filters can allow users to sort tickets based on the highest or lowest SLA consumption by specific agents. Use Case Example:Ticket #12345 was handled by three agents: Agent A owned the ticket for 2 hours (consuming 30% of the SLA). Agent B owned the ticket for 4 hours (consuming 50% of the SLA). Agent C resolved the ticket after 1 hour (consuming 20% of the SLA). In the final report, you can see exactly how the SLA was split across each agent and identify if one agent consumed more time than expected or if another agent quickly resolved the issue.Benefits:Improved Visibility: Managers can see who contributed to the SLA consumption and pinpoint where delays are occurring. Fair Evaluation: Agents will be evaluated more fairly based on their actual contribution to the ticket's SLA, not just the final resolution. Better Resource Allocation: The data can help reassign tickets to the right agents or improve response times based on historical performance.

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.