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

andyhornApprentice

Multiple Agent Email SignaturesClosed

Please add multiple agent signatures as a feature.For a product which offers it’s clients various management capabilities when dealing with multiple brands/products, I find it very odd there isn’t default functionality for adding multiple agent signatures so each agent has a signature per brand/product.We can manage email flows, repsonses, automations, and portals for each brand/product, but we can’t easily allow our agents to communicate with our customers with an appropriatly branded email signature. Why not? It’s a natural feature for Freshdesk.I would expect to be able to setup an email signature per brand, per agent, and have the system automatically insert the correct signature when the agent starts a reply based on the brand/product the email came in on. An option to set a default signature might be useful if an agent didn’t have an appropriately branded email signature setup.I’ve tried using Personal Canned Responses to get around this, and while they almost work they don’t accept full html like the signatures do, plus it requires the agent to manually delete the default signature and manually insert the canned response each time.I’ve tried using the Signature Management App but the images we have in our signature break when the reply is sent, it’s manual, and several agents could access other agents signatures this way.Please add multiple signatures as a standard feature of Freshdesk along the lines as described above.

BakeryTechApprentice

Automation Action: Remove Tag/sClosed

The inability to automatically remove Tags from tickets using Automation is severely limiting. I am aware of the API work around users have devised, but API calls take time to execute and occur outside of the Automation itself. This means that a single Ticket Update event cannot both remove a tag AND run an Automation which is looking for tickets that don’t have the same tag. A second update even must occur.Use Cases; Too many to list, but here are two examples;1. Say you have multiple different auto-replies which are sent to Requesters of New tickets, depending on which department the ticket will be routed to. Multiple times per year, your company shuts down for Holidays. You want to send a special auto-reply to let Requesters know that you are closed and will get back to them when you reopen, but you don’t want to also send them the regular auto-replies.To solve this issue, you make the regular auto-replies not run if a Ticket has the “Holiday_Time” tag. This automation needs to run on both Creation, and every time a Requester updates the ticket while you are on Holiday.When your company returns from Vacation, you disable the automation adding the “Holiday_Time” tag and replace it with an Automation that removes the “Holiday_Time” tag from all tickets when they are updated by anyone.To expand on the above, the auto-replies in question don’t apply to just Ticket Creation. In Zendesk we previously used a setup where an Auto-Reply would be sent-out if a Ticket was moved to a different Department.Further more, the above Holiday Time method works up until a ticket is open for multiple Holidays. In our case, some customers take 6+ months to respond to an invoice. Meaning a single ticket can easily cross multiple Holidays. Currently, it is outright impossible to implement the above without using the API Workaround, but that is inherently inconsistent. 2. Say you have a sorting rule that pushes tickets to a specific User when a variety of different conditions are met. The possible combinations of conditions required to prompt the auto-assign are too complex for a single Automation, requiring multiple automations which all add the same Tag. Then downstream the auto-assign automation looks for the existence of this tag and assigns the ticket.Now we have an issue, either the ticket will be re-assigned every time a ticket with the Tag is updated, or this Auto-Assign can only ever run ONCE for a single ticket. This makes complex ticket routing and escalation setup nearly impossible to implement.Ticket Creation automation suffers the most from this limitation, since not even the API workaround can help. As mentioned above, a second update event is required to trigger Automations looking for Tickets without the tag being removed.

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.