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

DanielRuff
Top Contributor ⭐
DanielRuffTop Contributor ⭐

Ability to monitor and restrict API usageUnder Review

What is the problem?Workflows in Freshservice are really great but the more you use them with external integration the more you rely on the API to be available and the API calls to work and not fail due to some reason. Main issues we’re facing and ideas for that:API Keys and restrict users Every single agent (300-400 for us) has an API key and can use the API even if I don’t want them to use it. There is no possibility to restrict this behaviour. It should be the other way around, I allow specific users to use the API instead of generally allowing the usage.   Rate limit and monitoring   Notification about errors in web requests E.g. my third party integration failed because the rate limit from freshservice was reached and I needed to pull data via API (or any other error). How do you get notified about this? In Freshdesk admins get an email about failed web requests - not in freshservice. If you want to get a notification you can use the best practice I documented in the community using this Link. We need a better overview of the requests, the results and if we want to get notified about errors.   Who uses the API? At the moment freshservice doesnt have the ability to see who used the API to see why the API limit is reached. I need to ask freshservice support, they send me an excel file and in the far background they themself can see the user who has sent so many requests to the API that my third party integration failed. We run into issues with rate limit very often and are hardly struggling to run our third party integrations speaking to our freshservice instance.   Unauthorized requests Tell me your freshservice URL and I can exceed your rate limit without having a valid API key. I could write a script that sends 1000 unauthorized api calls to your productive freshservice instance per minute and that would reduce your rate limit even if my requests are not authorized. My API integrations that rely on freshservice api can easily get ddosed. If you ask the freshservice support they can manually block IP adresses but that’s it. Unauthorized requests should not count towards the rate limit. Following my first point about restricting users from api usage that should help here as well. Also having a timeout for users that exceed the limit very often or I’d be happy about any other improvement.Example: Simple API call to support.freshservice.com without a valid API key. I sent 6 requests to their endpoint and the ratelimit is reduced by 6. A simple script with a loop and their productive instance API rate limit is reached.     Money Having a lot of external applications trying to access freshservice literally costs a lot of money as they all need a valid fulltime license + account. Best practice recommended by freshworks is to use single accounts for every integration. Just as a side note. See this topic in the idea section to get additional licences for tec accounts: Link

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.