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

EvgenySmirnov
Community Debut
EvgenySmirnovCommunity Debut

Email Threading for Third-Party Ticket ReferencesClosed

Sorry, it’s a long one.We are a Managed Service Provider (MSP) and as such our clients are companies and all our communications in Freshservice are with clients who typically have their own ITSM system or with their and our suppliers who we need to work to resolve issues with the system under our management who also have different ITSM systems and all of them use their own ticket reference numbers. We have done an analysis and around 40% of all our Freshservice tickets are duplicates (many of them are maintenance notifications from clients or their suppliers which we do need) which come from the fact that Freshservice (as many other ITSM systems) could not thread emails using third party ticket reference numbers. A substantial portion of these emails is generated by automated systems, lacking the attributes currently employed by Freshservice for effective email-to-ticket threading.An example – comms provider doing maintenance. That maintenance might not be touching just us, so even if they could, they would not be able to insert our ticket number in any further communication on it. Their ITSM system sends us at least 4 new emails – initial notification, notification a day before, start of works notification, completion of works notification. That is 4 tickets in Freshservice as the only common thing between all of them is comms provider ticket number, which Freshservice could not use for threading to the same ticket on our side.  To address this challenge, we explored a solution using Power Automate as an email processor, coupled with the Freshservice API to accurately associate emails with the respective tickets. While we succeeded in achieving the desired threading outcome, unfortunately, we encountered a roadblock preventing the release to production. The impediment arose from the inability to insert embedded email images into Freshservice tickets using the API. Despite consultations with Freshworks teams, no viable workaround was identified.What we have done is not a rocket science and pretty straight forward – before an email is threaded to an existing ticket or new ticket is created the subject line is checked for Freshservice and Third Party reference numbers based on formats/patterns we have defined. Here's a brief overview of the features we had implemented, and we suggest getting it implemented in Freshservice:Hierarchy-based Ticket Matching - The system should check references in a predetermined hierarchy, prioritising certain systems over others. For instance, if there is a Freshservice reference, it should be checked first before exploring third-party references.Configurability - The system should be configurable to support multiple patterns for ticket references. This would allow us to adapt to different ticketing systems used by our clients and third parties.Linking Multiple IDs to a Single Ticket - It should be possible to link multiple references to a single ticket. This flexibility is crucial as emails may contain references from various systems (client, suppliers), and being able to associate them with a single ticket would streamline our processes.Updating Multiple Tickets from the Same Email - The system should support the updating of multiple tickets based on references found in the same email. This would be especially beneficial in situations where a single email corresponds to multiple tickets (for example same maintenance in multiple datacentres have different ticket numbers but update can be sent in one email).Visibility in Ticket Properties - Ticket references should be prominently displayed in the ticket properties, providing agents with quick and easy access to this information. This visibility is key to ensuring that agents have all the necessary details at their fingertips.Manual Addition of References - Agents should have the ability to manually add references to a ticket. This ensures flexibility and control over the matching process, especially in cases where references may not be automatically detected.Integration with Outbound Emails - References should be carried over to outbound emails if not maintained in the subject. This ensures consistency and avoids confusion when communicating with clients and third parties.Again, apologies it’s a long one, but it’s a sour point for us so hope to get some backing. 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.