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

tim_13447
Apprentice
tim_13447Apprentice

Canned response formatting again *sigh*Closed

I see this has been brought up several times for various reasons but not the specific reason I want to ask about.  I have reached out to support a few times and after the last disastrous attempt at discussing this issue (other support questions have been good except the question about analytics which has resulted in hair loss from me ripping my hair out) I have decided to ask here to see if other see what I see.After the forced migration to Mint we have adapted and overcome for the most part.  One thing I love much better is response formatting with the new editor.  It's clean and easy to work with.  Adding a link is super easy and it's relatively simple to make replies look like you want them to.  Links in particular are a problem for me because I need to link to relevant documentation some times.  I click the link button and a nice little popup shows up and lets me add the link and change the text.  I can even say to open the link in a new window.The canned response editor, on the other hand, is the same horrible one from old Freshdesk.   When I have typed something in and highlight it with the mouse and then click the link to link it (like when editing a previous canned response) the link sometimes will be added, other times it shows up blank like I never highlighted anything, and other times will display a cryptic  javascript:void(null); instead of the word I highlighted.    It makes typing and editing a royal PITA to do.  Trying to bold something is equally frustration.  Sometimes it bold the word or sentence you wanted it to, and sometimes it bolds absolutely nothing.  I asked support previously about being consistent and having the same editor in tickets be the one for canned responses too.  I don't think I ever got a satisfactory answer back.   Mint has been out long enough so surely they have had time to make things the same across the board.  Lastly, what the heck is the deal with canned responses sometimes having the same font as the response when I insert them by using the /c command?  Sometimes I have to clear the formatting on the whole canned response I entered (which has bolded words, links, etc).  The text font should also be consistent across the board.  Also, if the  Mint editor could stop randomly removing extra spaces as I type that would be awesome.   Sometimes I am leaving them there intentionally to be filled in by information I don't have yet, like when I leave space for a refund transaction id.  I want the 3 spaces there to more easily spot where to add it.  Thanks.  Tim

thanos.massiasContributor

Email header in emails from Freshdesk that I can use for filteringClosed

My problem: I want to filter emails that our staff ( this applies to both agents and non-agents ) receive from our Freshdesk. I also want this filtering to not be fooled by emails we receive from other Freshdesk installations ( we were glad to discover that some partners also use it ). Possible solution: Freshdesk could add something in the headers that uniquely identifies an outgoing email as coming from a specific account and indicate the type of email ( notification or not ). For example, Freshdesk could add an X-Fresdesk-Source custom header. In this case, if my Freshdesk account is myaccount ( => myaccount.freshdesk.com ) then: X-Fresdesk-Source: freshdesk_myaccount_notification_agent means that the email is an agent ( = Agent Notifications tab ) notification from myaccount X-Fresdesk-Source: freshdesk_myaccount_notification_requester means that the email is a requester ( = Requester Notifications tab ) notification from myaccount X-Fresdesk-Source: freshdesk_myaccount_notification_cc means that the email is a cc ( = CC Notifications tab ) notification from myaccount X-Fresdesk-Source: freshdesk_myaccount_reply means that the email is a reply ( = Reply Templates tab ) from myaccount etc The list is not complete as it should include, for example, qualifiers for emails generated through ticket watch or rules but it illustrates the idea. Using this I could then create rules in my Mail Client that use conditions based on  data from that header. Example: If I want everything from myaccount moved to a specific folder then I would use this ( partial ) match: X-Fresdesk-Source: freshdesk_myaccount_ or just freshdesk_myaccount_ If I want all notifications from myaccount moved to a specific folder then I would use this ( partial ) match: X-Fresdesk-Source: freshdesk_myaccount_notification_ or just freshdesk_myaccount_notification_ I can also be specific and target only agent notification with a full match: X-Fresdesk-Source: freshdesk_myaccount_notification_agent or just freshdesk_myaccount_notification_agent Obviously, any recipient could also benefit from this to categorize Freshdesk generated emails ( ours and from anyone else ). An added benefit is that since the account is mentioned specifically ( i.e. myaccount ) the filters will not be fooled when processing email from another Freshdesk account ( like the  account of one of our partners or customers ). PS1: I have though about other ways but none is satisfactory: - Message-ID: References: Received: and other system headers should not be touched in any way. - Subject: is not ideal for a number of reasons, including: Adding this info ( account identifier plus identifiers for notification/reply/etc type ) to the subject of every outgoing email would lead to some very ugly and confusing/intimidating subjects. Some emails like watch or rule generated ones, have subjects I cannot configure. When I change a subject, even a little, everyone will have to change their rules. A particularly bad case of that is when someone else is using a subject like mine ( because, for example, they saw our subjects and thought it would be nice to copy them ), forcing me to change everything in order that our rules do not mistake their emails for ours. PS2: I use the underscore '_' as the separator of qualifiers above ( as in freshdesk_myaccount_notification_agent ) but this is a poor choice. A better choice is some character that myaccount ( the Freshdesk account name ) is not allowed to contain, so that I could reliably process this header if needed.

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.