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

Net Metering: A Smart Way to Save on Electricity BillsClosed

Net Metering: A Smart Way to Save on Electricity BillsWith rising electricity costs, many homeowners and businesses are looking for ways to reduce their energy expenses. Net metering is an excellent solution that allows consumers to generate their own electricity using solar panels and sell excess power back to the grid.What is Net Metering?Net metering is a billing system that enables consumers to offset their electricity bills by producing their own energy. If your solar panels generate more electricity than you consume, the surplus energy is fed into the national grid, and you receive credits on your bill.How Does Net Metering Work?Install Solar Panels – First, a solar power system is set up on your property. Generate Electricity – The panels convert sunlight into usable electricity. Use What You Need – The generated power is used for household or business needs. Send Excess Power to the Grid – Any surplus energy is sent to the grid through a bidirectional meter. Receive Bill Credits – The utility company credits your account for the extra electricity supplied.Benefits of Net Metering✅ Lower Electricity Bills – Save money by producing your own power.✅ Earn from Surplus Energy – Get credits for unused electricity.✅ Eco-Friendly Solution – Reduce your carbon footprint by using renewable energy.✅ Energy Independence – Less reliance on the power grid.How to Apply for Net Metering?If you're interested in applying for net metering in Pakistan, visit FESCO Net Metering to learn more about the process, eligibility criteria, and required documentation.By switching to net metering, you can enjoy long-term savings while contributing to a greener, more sustainable future. Start your journey toward energy independence today!

adbi
Apprentice
adbiApprentice

Analytics discrepancy: Tickets are credited to the assigned agent instead of the actual resolverSubmitted

Hello everyone,I am facing what appears to be either a reporting limitation or a process compliance issue within Freshservice Analytics.ScenarioLet's consider the following example:Ticket is assigned to Agent A. Agent A becomes unavailable (vacation, sickness, etc.). Agent B investigates the incident. Agent B performs the fix. Agent B changes the ticket status to Resolved. Agent B closes the ticket.The ticket activity log clearly records that Agent B performed the resolution action.Example:Agent B → Set Status as ResolvedHowever, the Analytics reports appear to attribute the resolved ticket to Agent A (the assigned agent) rather than Agent B (the actual resolver).Why this is problematicFrom an ITSM and operational KPI perspective, these are two completely different metrics:Ticket ownership Actual ticket resolution effortIn the example above:Metric Expected Result Ticket owner Agent A Ticket resolver Agent B If Analytics only reports against the assigned agent, then the productivity metrics become inaccurate.For example:Agent A may be absent for several days. Agent B resolves multiple tickets assigned to Agent A. Analytics still credits Agent A.This can significantly distort:Individual performance statistics Capacity planning Team workload analysis Operational reportingInvestigation performedI searched throughout Analytics:Standard reports Custom reports Custom metrics Custom attributesI was able to find:Agent Name Agent Group Name Resolved Date Closed DateBut I could not find any field such as:Resolved By Closed By Resolver Last Updated ByThe information clearly exists in the ticket activity log, yet it does not seem to be exposed for reporting purposes.Questions Is there currently a supported way to report on the actual agent who resolved a ticket rather than the assigned agent? Is there any Analytics dataset exposing: Resolved By Closed By Ticket Activity Author Audit/Event Owner Is this expected behavior by design? Has anyone implemented a workaround that remains ITIL-aligned and preserves accurate technician productivity metrics? FeedbackMy concern is that Freshservice currently allows an agent other than the assignee to resolve a ticket (which is operationally correct), but Analytics may not provide a reliable way to measure who actually performed the resolution.This creates a potential mismatch between operational reality and reporting reality.I would be very interested in hearing how other ITSM teams handle this situation.Thank you.

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.