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

repattersonSkilled Expert

Enhance the Spam Ticket Handling with Bulk Delete and Additional Management EnhancementsSubmitted

The Spam ticket view in Freshservice has several functional gaps that impact our team's ability to manage spam effectively. We are requesting the following enhancements:1. Tickets from Deactivated Requesters Are Automatically Flagged as SpamWhen a ticket is submitted by or associated with a deactivated user account, the SYSTEM automatically marks it as spam — even when the ticket itself is legitimate (e.g., an offboarding task, an access removal request, or a ticket submitted on behalf of a former employee). This results in valid work items being silently routed to spam and potentially auto-deleted after 6 months with no agent awareness.Requested solutions (any or all):Admin toggle — Provide an admin-level setting to disable automatic spam flagging of tickets from deactivated requesters. Notification routing — When a ticket is auto-flagged as spam due to a deactivated requester, send a notification to a configurable group or agent for human review before the ticket is lost. Automation rule support — Allow admins to create workflow/automation rules that fire when a ticket is spam-flagged due to a deactivated requester, enabling custom actions such as reassignment, notifications, or reopening.  Currently any actions that are taken by the SYSTEM account do not trigger workflows.2. Limited Bulk Actions in the Spam ViewWhen tickets are selected in the spam view, the only available bulk action is "Mark as Not Spam." We request the following additions:Bulk Delete — Add a "Delete Selected" bulk action so agents can immediately remove confirmed spam without waiting for the 6-month auto-deletion window. "Empty Spam" / "Delete All" — A single button to purge all tickets in the spam view at once, consistent with how spam/trash works in standard email clients. Select Across All Pages — When spam exceeds one page, provide an option to select all tickets across all pages, not just the current 30-per-page view.3. Lack of Visibility and Context in the Spam ViewPer-ticket scheduled deletion date — The banner states tickets older than 6 months are auto-deleted, but there is no per-ticket indicator of when that will occur. Adding a "Scheduled Deletion" column would help agents prioritize review. Filter/Search within Spam — Allow filtering by requester, domain, subject keyword, or date range to identify patterns and locate misclassified tickets quickly.Business Impact: Without these controls, legitimate tickets — particularly those tied to employee offboarding or account transitions — are silently routed to spam and risk permanent deletion with no agent awareness, creating compliance risk and missed work. Additionally, with no bulk delete or empty spam option, agents have no way to proactively clear confirmed spam and must rely entirely on the 6-month auto-deletion timer. These enhancements would bring the spam view in line with standard IT service management expectations and give administrators the visibility and control they need. 

hazman112Apprentice

Enhancement Request: Add Hour-Based Date Conditions in Workflow AutomatorSubmitted

ProblemCurrently, date-based conditions in the Freshservice Workflow Automator only support comparisons using days (for example, "is exactly x days away" or "is at least x days ago"). This limitation makes it difficult to create automation workflows that require more granular time-based logic.Use CaseMany operational and service management processes require actions to be triggered within a specific number of hours rather than days. Examples include:Sending reminders 24, 48, or 72 hours before a task or renewal date. Escalating tickets if an activity has not occurred within a set number of hours. Triggering notifications shortly before planned maintenance windows. Managing approval and workflow deadlines that are measured in hours rather than full calendar days.Current LimitationUsers can only configure conditions such as:Is exactly 'x' days away Is at least 'x' days away Is exactly 'x' days ago Is at least 'x' days agoThere is no equivalent option for hours, forcing administrators to either:Use less accurate day-based calculations. Create complex workaround logic. Rely on external integrations or custom scripting.Suggested EnhancementExtend date-based conditions to support additional time units:Hours Days (existing) Weeks Months (optional)For example:Is exactly 24 hours away Is at least 48 hours away Is exactly 12 hours ago Is within the next 6 hoursAlternatively, provide a configurable time unit selector alongside the numeric value field.Business ValueIncreased workflow flexibility. Reduced need for custom solutions and workarounds. Better support for SLA-driven processes. Improved automation accuracy for time-sensitive activities. Greater alignment with real-world operational requirements.

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.