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

SnuffleRoeSkilled Expert

Remove font for placeholders in e-mailsClosed

When sending a mail (either via the default e-mail notifications or via a node in a workflow) and using Placeholders in those mails, the text font is very weird for the text provided by the placeholders (it least if you use Outlook as mail client).The first indented text is the ticket description and the second indented text is the latest public comment.Nowhere in FreshService is a specific font set, even under the E-mailnotifications it says “Default font”, so why does each text area have their own font?In an attempt to have all text in a mail set to a specific font I've tried:Setting the font in E-mailnotification in the admin panel Edited the mail in the HTML editor and set the code below in each <p>, <div> and <span>  tag style="font-family: Verdana;" But still it comes out as pictured above. I'm no perfectionist and if the font it would come out as in the mail would seem similar to Verdana I would be fine with it, but this just looks absolutely atrocious.I've already raised a support ticket with FreshWorks for this and I got this as a reply:Thank you for reaching out regarding the font family issue in your HTML email sent through the workflow.Our developers have confirmed that the description field in Freshservice uses a rich text editor, which comes with its own HTML properties and inline styles. Unfortunately, this means that it is not possible to impose a specific font family (like Verdana) for the description placeholder content. The rich text editor applies its own inline styles, which can be seen in the ticket details page as well.Sorry for not being much of a help here.I understand the reply, but I just can’t leave it at this.I have three possible solutions (of which the last is least favourable): When sending an e-mail from a FreshWorks Product using Placeholders, allow the font in the placeholder to be ignored and use the font defined in the e-maileditor. Font colour, bold, underline, italic and such should remain. Allow admins to disable different fonts in text area in their forms. Again, font colour, bold, italic and such should still be available. Allow admins to disable rich text formatting entirely. This is least favourable, but there will at least be uniformity in communication.

JoramP
Contributor
JoramPContributor

Collaboration Feature for Approval ManagersFuture Consideration

Hello Freshservice Community,I’d like to propose an idea that could greatly enhance the approval process in Freshservice. Currently, approval managers often need to consult colleagues or project leaders before making a decision on a service request. This typically happens outside the platform via email or other communication tools, which can be cumbersome and slow down the process.What if Freshservice had a built-in collaboration feature for approvals? This could take the form of a chat function or an option to "Request Confirmation" from another colleague or project leader directly within the approval workflow.Benefits: Streamlined Communication: By integrating discussion capabilities, approvers can collaborate in real-time without leaving Freshservice. Faster Decision-Making: Reduced dependency on external tools like email means faster turnaround times for approvals. Improved Transparency: Keeping all discussions tied to the specific service request ensures a clear record of decisions and inputs. Enhanced Collaboration: Approval managers can easily involve project leaders or subject matter experts, ensuring better-informed decisions. Proposed Features: A chat or comment section directly within the approval request interface. A "Request Confirmation" button allowing approvers to notify specific colleagues for input. Notifications to keep all involved parties updated on discussions or status changes. A log of all discussions tied to the service request for reference. I believe this feature would make the approval process more efficient and user-friendly, enhancing Freshservice's value as a centralized IT service management tool.Looking forward to hearing your thoughts and feedback!

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.