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

FVNJB
Apprentice
FVNJBApprentice

MCP Usage Breakdown per Agent & Custom Reporting DataSubmitted

Requesting MCP Inbound Usage Breakdown per Agent & Data Source for Analytics / Custom Reports Hi Freshservice Team and Community,We are currently utilizing the Model Context Protocol (MCP) integration in Freshservice to streamline agent workflows and tool execution. While the Data Usage Analytics dashboard under Admin > Account Settings > Data Usage provides solid high-level metrics (total volume, system modules, execution status, and monthly usage trends against plan limits), we are encountering two key limitations regarding granularity and custom reporting.We would like to raise the following queries/feature requests with the Freshworks Product Team:1. Granular MCP Usage Breakdown per User / AgentCurrently, the Inbound MCP Report aggregates usage across the entire account level. When authentication relies on central service tokens, it is impossible to audit individual usage.Question / Request: Are there plans on the product roadmap to introduce agent-level granularity in the Data Usage Analytics dashboard (e.g., showing which agent triggered which MCP action/tool call)? If OAuth or user-specific API keys are used, is there a recommended way to extract agent-specific consumption metrics today?2. Exposing MCP Usage Data in Freshservice Analytics (Custom Reports)To monitor our API budget effectively and correlate MCP adoption with agent productivity, we need to build custom reports, set up custom alerts, and schedule automated exports.Question / Request: Will Freshworks release MCP Usage data as a native data source within Freshservice Analytics? Having access to an "MCP Logs" or "Data Usage" dataset inside Analytics would allow us to slice and dice consumption by department, group, or time frame alongside standard ticket metrics.Has anyone in the community found a workaround (e.g., via the Freshservice API or Audit Logs) to trace MCP calls back to individual users?We’d appreciate any insights from the community or updates from the Freshworks Product Managers!Thanks!

PeterAnderson
Community Debut
PeterAndersonCommunity Debut

Sort tickets by multiple columnsPlanned

Currently, when viewing a list of tickets, you can add, remove and rearrange columns using the setting on the right-hand side. You can also sort the list using the setting on the left-hand side. However you can only choose one of the columns to sort by. For example, say you have columns for Priority (low, medium, high) and Status (open, in progress, resolved). You can choose to sort by Priority (asc. or desc.), or you can sort by Status (asc. or desc.) - but not both. If you sort by Priority desc. for example, you get a list of all the high priority tickets first, then the medium ones, then the low ones. But out of all the high priority tickets at the top of the list, the Status of those tickets could be in any order. I’d like to suggest a feature that lets us sort a ticket list by multiple columns. This would mean that, for example, you could sort by Priority desc., then Status desc. This would give you a list of all the high priority tickets first, and out of those, all the open ones would be grouped together, all the in progress ones grouped after that, and then all the resolved ones grouped at the end (followed by the medium Priority tickets, etc.). My desire for this feature is to sort my ticket list in such a way that I know that the ticket listed first is the one I need to work on first (be it the most urgent, the one I haven’t responded to yet, or the one that’s been sitting there the longest (or all of the above!)).

gokhanrzApprentice

Cross-Workspace Ticket Visibility for AgentsSubmitted

Currently, when an agent creates a ticket in another workspace to which they do not have agent access, they cannot view that ticket in the agent interface. Instead, they must switch to the requester portal to access it. This creates unnecessary additional steps, particularly when agents need to follow up on tickets they have submitted to other teams.Furthermore, when someone replies to such a ticket, the agent receives a notification, but the link in the notification directs them to the agent interface rather than the requester portal, where they can actually access the ticket.It would be very helpful if agents could view and track tickets they have submitted as requesters in other workspaces directly from the agent interface, without requiring additional workspace permissions.The situation is even more problematic with child tickets.For example, when an agent assigned to a parent ticket creates a child ticket in another workspace, they may lose access to that child ticket entirely. In our experience, the child ticket is accessible neither from the agent interface nor from the requester portal. This makes it difficult for the agent responsible for the parent ticket to monitor progress, follow up with the other team, or coordinate the overall resolution.This significantly limits collaboration between teams operating in different workspaces.Suggested improvementIt would be extremely useful if Freshservice could provide ticket-specific cross-workspace access with the following capabilities: Requester access: Allow agents to view tickets for which they are the requester directly in the agent interface, regardless of the workspace in which those tickets are assigned. Parent-child ticket access: Automatically grant agents assigned to a parent ticket visibility into its child tickets, even when those child tickets belong to other workspaces. Restricted access: Ensure that this access applies only to the relevant tickets, without requiring agents to become members or observers of the other workspaces or their agent groups. This would enable agents to track their requests, monitor dependent tickets, and collaborate more effectively across workspaces while maintaining appropriate access restrictions and workspace-level data isolation.

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.