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

DevOps Freshdesk connectorClosed

 About IntegrateCloud Freshdesk - Azure DevOps Integration App: Azure DevOps (VSTS) Integration App by IntegrateCloud, allows the users to create work items inside the Freshdesk form. It also allows you to link Freshdesk tickets to an existing Azure DevOps (VSTS) work item. In addition, it allows Agents to notify the Azure DevOps (VSTS) team, by sending comments inside Freshdesk Support.You can Collaborate your support team and developers at one place.We also support customization based on customer request and tailored to your needs! We bring Azure DevOps (VSTS) closer to your business model! IntegrateCloud Freshdesk - Azure DevOps Integration app usage guide In order to use the IntegrateCloud app on Freshdesk, User’s required to create API Access token on Freshdesk and personal access token on Azure DevOps. please follow the below our article to create the Azure DevOps personal access token and Freshdesk API Token How to create personal access token on Azure DevOps and Freshdesk API Token please follow the below our support article to install and configure the app from Freshdesk marketplace How to install and configure IntegrateCloud Freshdesk - Azure DevOps Connector  Follow below steps how to use IntegrateCloud Freshdesk-Azure DevOps ConnectorLogin to your Freshdesk account with your login credentials Create a new ticket in Freshdesk or go to any existing ticket. You will see the Freshdesk - Azure DevOps Integration app on the right side of your ticket. In the App we have 3 Options.New Work Items which contain Bug, Epic, Feature and Task. Link to Work Item. Notify. How to create Bug The New Work Item tab, select the type of work item you want to create Bug, Epic, Feature, Task, User Story etc. Based on the selection it will load all the Azure DevOps (VSTS) fields. The User can make the selection and click on Create button which would create work item in Azure DevOps (VSTS) and then display the corresponding Azure DevOps (VSTS) work item Id in the App.  Similarly, user can create Epic, Feature and Task also. Link existing work item This tab allows you to link an existing Freshdesk Ticket. It can be linked to one work item in Azure DevOps (VSTS). Freshdesk-Azure DevOps app allows the user to create or link multiple work items to one Freshdesk ticket.  Select Project and Work Items from the drop-down options, then Click on Link. NotifyThe Notify button allows the user to send notifications to the Azure DevOps (VSTS) team which would show up as comments in Azure DevOps (VSTS)  Select Project and Work Items from the dropdown options, Write the message that has to be sent then Click on Send Show Item Comments:This tab shows you all the linked Azure DevOps (VSTS) work item comments log to the current Freshdesk ticket.  

BPJ
Apprentice
BPJApprentice

Splitting tickets when a reply spans old and new topicsClosed

We often have customers who reply to an open ticket, with an email that is partly about that open ticket and partly about something new.  As it works now the Split function cannot cope with this.  If we split the ticket at that user’s reply it MOVES the whole of that reply to a new ticket.  In the scenario where the email was partly about the old ticket and partly about something new, we would prefer that the email is COPIED to the new ticket, so that it exists in both places.  We can then reply to the old bit in the old ticket, and the new bit in the new ticket.  Some other, competing systems to Freshdesk already work this way and it seems more logical.It also seems logical that if an agent sees a need to split a ticket then it is inevitable that the new ticket should have a new subject line - so it would be sensible to prompt for that at the time of splitting, rather than the agent having to remember to go back into the new ticket to edit the subject.  If it was all about the same subject the ticket would not need splitting, so ask us for the new subject line when we split the ticket please.We did wonder if the Clone Ticket app would be a solution to this problem, but it isn’t.  Clone does copy rather than move, but it copies the first email in the old thread not the latest email in the thread.  That would be useful if the first email in a new ticket was about multiple topics that we would want to separate, but if the customer diverges from the original topic in a later reply then cloning the first email doesn’t help.Ideally perhaps it would be good to have a Split function that opens a small dialog with a choice to either “Copy the latest post to as new ticket” or to “Move the latest post to a new ticket”, and with an option to specify a subject line for that new ticket.  This might default to the current ticket’s subject, but could allow agents to change it if they wish.  Similarly if you make Move the default option then the current method (move and keep same subject) is preserved by default and you only add one extra keypress to the Splitting process - an OK button.  For users who prefer to copy rather than move and/or prefer to change the subject this would be possible.

stevemc
Active Contributor
stevemcActive Contributor

Improvement to Possible Connections cardClosed

Summary: Feature Request - Improve “Possible Connections” as follows:On Contact Page, separate “Possible Connections” to 2 lists: Known Connections - Other contacts in same account Possible Connections - Contacts matched by Freddy not already in the account On Account Page, add following (separate from “Account Hierarchy”): “Possible Connections” - Contacts matched by Freddy not already in the account Here is some background to the request:We love the Possible Connections feature as a way to help clean up data.  But because this feature does not distinguish between “Known connections” (because contact is in same company) and “Possible Connections” (as determined by Freddy), we find this to lessen the utility of the feature greatly.As an example, see the card below for one of our Hewlett Packard contacts: This tells me that there are 25 people. Match is for the most part on the email domain (hpe.com).  The problem is that I don’t know which ones are already part of HPE account and which are not and need to be connected.  I can’t really take action on them w/o opening each and reviewing.  This is cumbersome and means that many users will not try to clean up the data.  I would prefer instead that the tool have 2 separate lists:Known connections Possible ConnectionsNow for example, there may be only 4 people in possible connections.  I’m much more likely to decide to go clean up 4 contacts.Additionally on the HPE Account page, I only see connections who are actually in that company.  I would like to also see a “Possible Connections” based on same Freddy recommendations that are provided in the Contact Page.

j.nickellContributor

Improve Solution Article sharing experienceClosed

This request is based on my experience/frustration over the past couple of weeks and it’s possible I’ve missed something that would address it. If so, please let me know.Currently there are two distinct and incompatible ways to get to a solution article via a url:If the end user has their portal set as “classic” the following link format works:https://instance.freshworks.com/support/solutions/articles/articleIDIf the end user has their portal set as “ask Freddy” the following link format workshttps://instance.freshservice.com/home#solutions/articleIDIf the user is setup for the “other” portal style, the link doesn’t work.Almost more importantly the service doesn’t seem to contain a ‘handler’ if the user clicking on the link isn’t signed in to the portal when they click on the link. They are most likely to get a dead end kind of page rendering that doesn’t make it obvious that they need to sign in.  Then if they do sign in, they are not redirected to the original target page, they just land on the portal page.A better experience would be: a single url format that works regardless of the end user’s portal preference and a handler that identifies the need to sign in, handles the sign in process and then directs the end user to the original requested page.Why this is a problem for us. Our user base is accustomed first and foremost to email based support and communication. We want to educate them about the availability of the portal by including links to solution articles the in communications we send out, but we can’t reliably do this in the current format, because we end up fielding support requests on how to get to the support article.  We are configured for SSO, so it’s not a matter of them needing to setup a user account on the platform. 

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.