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

8947 Ideas

tpurcellContributor

Initiate Client Contact via Email by Specific Product (Variant of Compose Email)Closed

Use case scenario: We support multiple products/services. For one of our products/services our work flow is as follows: Client signs up for service Implementation team gathers information for setup of service Service is setup via phases: 1-3 Development works on phase 1 Phase 1 completed, customer must be notified and prompted for more interaction to move on to phase 2. CLIENT IS SENT NEW EMAIL Work flow repeats as above for all phases until service is fully implemented for client.  We need to track these email communications via a central support tool. Previously it has been done via standard email, but that isn't scaleable as we need agents to be able to reassign tasks or shift responsibilities by assigning the work to other team members. For the new agent to jump in, they need to see the client interaction history. Using Freshdesk for this would be ideal as the ticket will track client interaction and keep a central history of interaction. Currently email is sent from one agent to the client and then the agent cc's all other agents who may need to back them up. This is terrible because it generates so much email noise and isn't an automated or complete contact history based on a number of factors. We MUST have a tool/process for centralizing this client communication that looks and feel like email to the client but functions as a Freshdesk ticket on our side.I've attempted to use a combination of Dispatcher rules and custom ticket fields to create a ticket that looks like it is composing email to the client, but have hit two significant road blocks. Ideally, there will just be an expanded specific feature that address this issue/workflow, but if there isn't then the next best solution will be to expand the function of the Dispatcher rules to address the two primary roadblocks I've encountered.My current "work-a-round" solution that is close, but not close enough for actual use: Agent that needs to initiate client contact creates a new ticket In the new ticket it is filled out with the following method:Requester = Email To (Recipient)The Ticket Subject = Email SubjectThe Ticket Description = Email Body Agent sets a custom field to "Initiate New Email" (arbitrarily named) Then I have a Dispatcher Rule set that any new tickets with the custom field set to "Initiate New Email" will then have an action of Send Email to Requester, formatted with the following email placeholders: Subject = {{ticket.subject}}, Body = {{ticket.description}}. The client then gets an email with the details without a "RE:" in the subject line and it looks very close to the way we need it with two deal breaking exceptions.Two Primary Problems: The sent from address isn't product specific. So the client receives the email from our Global Support Email. This is a major deal breaker as we need the reply to address to be product and group specific. We will often need to send these new email messages to a group of stakeholders in the client's organization. We commonly have to send these new email/tickets to 2-6 recipients. We we attempt to use the "Add CC" feature in the New Ticket process in Freshdesk it send an email formatted with: "RE:" added to the subject line, and this line "{{Agent}} submitted a new Ticket to {{The Support Center}} and requested that we copy you" Thus, if the new email composition feature can't be added, I'd request the following features be added to work with our Dispatcher work flow: Select a "From/Reply to Address" in Dispatcher -I feel this should be added regardless in order to make Freshdesk better at Multi-brand support. Add the ability to have multiple requesters on a ticket, that way the dispatcher rule would work and we wouldn't need to use the "add CC" feature. -I feel this should be added regardless, as it is common that a ticket will be worked on for multiple client contacts and it would be nice to search a client history and see all the issues they had input on even if they weren't/aren't the ticket's primary "Requester" Add the ability to change the canned response for every automated reply from the Freshdesk system. We can change almost every thing else, why can't we change the "Add CC" notification format? As it stands, I can't fully migrate all my agents to Freshdesk until this work-flow is addressed. 

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.