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

Roxwell
Top Contributor ⭐
RoxwellTop Contributor ⭐

Interim Document Generation for Wet Signature ProcessesClosed

 Use Case Overview Many organizations, particularly universities, public sector institutions, and organizations handling visa or compliance documentation, require physical (“wet ink”) signatures or official stamps on generated documents before the process can proceed to completion. Currently, Freshservice allows document generation (e.g., via workflow automations or integrations), but this action typically represents a finalized step — triggering completion or closure of the associated request or workflow. However, in scenarios involving wet signatures, this breaks the real-world process, as the document must first be:  Generated, Printed and physically signed or stamped, Re-uploaded into the same request, Then verified or marked as complete.   Example Scenarios  University Letters & Certificates: Administrative teams generate official confirmation letters (e.g., enrolment, visa, or award letters) which must be printed and stamped with a university seal before being returned to the requester or external authority. The generated letter should not be visible to the requester until the final stamped version is uploaded and verified. Travel Visa Requests: HR or mobility teams generate supporting visa documents (e.g., letters of sponsorship, invitation letters). These require wet signatures by authorized signatories before submission to embassies. The document generation should pause the workflow at an “Awaiting Signature” stage, allowing manual intervention before continuation. Proposed EnhancementIntroduce a “Generate Document (Interim)” action type within workflows or approvals, enabling:  Document generation using existing template logic (variables, placeholders, etc.). Workflow continuation hold until a file is re-uploaded. Optional visibility control, hiding the draft/generated document from the requester until the final version is uploaded. Configurable status or stage name (e.g., Awaiting Signature / Awaiting Stamp). Resume automation once the signed/stamped version is attached and verified.   Key Benefits  Aligns Freshservice workflows with real-world administrative and legal processes that require physical document handling. Prevents premature request closure or visibility of incomplete documents. Supports compliance, especially in education, HR, and visa-related processes. Reduces the need for workaround solutions (e.g., manual ticket transitions or parallel request types).  Example Workflow Flow  Request submitted → Workflow generates draft document → System transitions ticket to Awaiting Signature → Agent downloads, signs/stamps, and uploads final document → Workflow resumes, transitions to Approved or Completed, and sends the signed document to the requester.  

xTofC4Be
Apprentice
xTofC4BeApprentice

Recurring on-call patterns with custom repeatsFuture Consideration

Hello Freshworks team,I would like to request an improvement on the On-call schedule module We rely on it daily and would love one enhancement that would remove a lot of manual work and scheduling errors.Request summary:Add native support for recurring on-call patterns that can repeat every X days, weeks, or months, while respecting a manually configured day-by-day plan and permanent delegation rules.Concrete use case:Team of 5 covering a 7-day on-call, weekends and holidays included. We run a 35-day sequence where some people have two or more consecutive days not always in the same rotation order. The exact 35-day plan must repeat identically every 35 days.Problem today:Schedules do not support repeating a custom, manually built pattern on a cycle such as every 35 days or every 5 weeks. The current rotation model prioritizes an automatically calculated order. In real life we often need the same person on consecutive days or irregular sequences that do not follow a simple rotation. Workarounds involve cloning blocks by hand and then manually adapt as the rotation order takes the priority, which is error-prone and time consuming.Proposed solution:Recurrence engine: let admins define a cycle that repeats every N days, or every N weeks or months, with a start date and optional end date. Pattern-based planning: allow building a manual day-by-day assignment for one cycle where any agent can appear on any number of consecutive or non-consecutive days. The manual pattern is the source of truth. When the cycle repeats, the exact same assignments repeat in the same order and that order is copied when schedule is cloned. Rotation priority control: provide a setting to disable automatic rotation priority so the manual pattern is kept and used exactly as configured.I would be happy to share examples if the request is unclear. Thanks for considering this. It would be a significant quality-of-life improvement for teams running complex, real-world on-call patterns.Kind regards,Christophe Doguet

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.