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

Hazell
Apprentice
HazellApprentice

Built a free tool that scores why Freddy AI isn't delivering ROISubmitted

Hi everyone,I’ve been working on a small tool for Freshservice teams who have Freddy AI enabled, or are planning to roll it out, but aren’t seeing the value they expected.The idea is simple: Freddy AI is only as good as the setup underneath it. If the knowledge base is thin, ticket categories are inconsistent, canned responses are duplicated, SLA rules are incomplete, ticket data is vague, or routing/service catalogue setup is weak, AI features tend to underperform.So I built a free Freshservice AI Readiness Audit.It connects read-only to your Freshservice instance and gives you:An overall AI readiness score Scores across 7 areas Freddy depends on The top issue blocking AI performance in each area A “do this first” recommendation Quick wins you can act on before investing more in AI rolloutIt looks at things like knowledge base coverage, ticket data quality, categorisation, canned responses, SLA configuration, service catalogue setup, and routing.The free audit doesn’t require a credit card, and it doesn’t store your API key.If anyone here is trying to work out why Freddy AI, auto-triage, or chatbot features aren’t delivering yet, I’d really appreciate feedback from actual Freshservice admins.You can try it here:https://www.servicedeskbuilder.com/ai-readinessWould love to know what it gets right, what it misses, and what would make the output more useful for a Freshservice admin.

Architectural Feature Request: Scope Automations and Configurations directly to Service Catalog ItemsFuture Consideration

Dear Freshservice Product and Engineering Teams,We are writing to propose a fundamental architectural enhancement to the Freshservice platform: the ability to associate key configurations (Workflows, Form Rules, SLAs, Fields) directly with individual Service Catalog Items.The Current Challenge: A Centralized, Condition-Based Configuration ModelCurrently, critical business logic components are managed in centralized, globally-scoped admin sections. To apply logic to a specific Service Item, we must create rules with explicit conditions, such as IF "Requested Item" is "New Laptop Request" THEN....While functional, this model presents significant challenges as an organization scales: High Maintenance Overhead: To understand or modify the end-to-end behavior of a single Service Item, an administrator must navigate to 4-5 different sections (Workflow Automator, Business Rules for Forms, SLA Policies, Field Manager). This fragmentation makes management complex and time-consuming. Increased Risk of Errors: A single large list of workflows or rules for all items is inherently error-prone. A minor mistake in a condition can have unintended consequences, impacting unrelated services. Lack of Scalability: As the service catalog grows, the list of automations becomes an unwieldy chain of IF/ELSEIF conditions, making it difficult to manage, debug, and audit. Poor Encapsulation and Portability: A Service Item is not a self-contained entity. Its logic is scattered across the platform, making it impossible to easily clone, export, or manage a service and its complete set of rules as a single unit. The Proposed Solution: An Item-Centric, Context-Based Configuration ModelWe propose a shift towards a model where business logic is encapsulated within the Service Catalog Item it governs.Instead of managing global lists, administrators should be able to configure rules and policies from within the Service Item's settings page. This would mean having dedicated tabs for "Workflows," "Form Rules," and "SLA Policies" directly on the item's configuration screen.Under this model: Any workflow created under the "New Laptop Request" item would only trigger for that item. The IF condition becomes implicit and unnecessary. The form rules would only apply to that item's form. The SLA would be inherently linked to that service. Key Configurations to be Scoped: Workflow Automator: Workflows should be creatable at the Service Item level. Business Rules for Forms: Form logic should be defined within the item's form editor. SLA Policies: An item should have its own specific SLA assignment, overriding workspace-level policies. Field Manager: The association of which fields appear on a form should be managed exclusively within the item's form designer, creating a clear boundary. Benefits of this Architectural Shift: Reduced Total Cost of Ownership (TCO): Drastically simplifies administration and reduces the time spent on maintenance and debugging. Enhanced Reliability: Isolates the logic for each service, eliminating the risk of cross-item interference. True Modularity and Scalability: Enables the creation of self-contained, reusable Service Items that can be managed, cloned, or migrated with their entire logic intact. Increased Administrator Agility: Empowers service owners to manage their items without needing to navigate complex, global rule sets. This evolution from a centralized to a distributed, object-oriented configuration model would represent a significant leap in platform maturity, aligning Freshservice with modern DevOps and "Configuration as Code" principles. We believe this would be a game-changer for enterprise customers managing complex service catalogs.We are eager to discuss this proposal further and understand if it aligns with your long-term product vision.Thank you for your consideration.

anthony castanoSkilled Expert

Native Analytics and Lifecycle Management for Canned ResponsesSubmitted

Currently, managing Canned Responses in Freshservice is a "blind" process. As our service desk grows, we can accumulate hundreds of templates with no way to track accuracy, relevance, or agent adoption. We are currently facing: Knowledge Decay: Old responses remain in the system with no "Last Modified" visibility, leading to agents accidentally sending outdated instructions or broken links. The "Manual Typing" Efficiency Gap: Admins cannot see which agents are ignoring canned responses and manually typing repetitive replies, leading to inconsistent customer experiences and lower productivity. Menu Fatigue: Agents must navigate through "Ghost" responses (unused for months), slowing down their response time. The Solution (The Request)We are requesting a built-in Analytics and Lifecycle Management dashboard. To effectively manage our communication library and team performance, we need:1. Content Lifecycle Data: Last Modified Date & Author: A timestamp and name showing when a response was last edited. Last Used Timestamp: To identify which templates are currently active vs. those that are "dead weight." Usage Tracking: A "Total Uses" counter visible in the Admin list view. 2. Agent Adoption & Audit Data: Usage by Agent Report: A native report showing which agents are using canned responses most frequently and which are not using them at all. Education Identification: Ability to see if certain groups or new hires are under-utilizing specific folders, allowing for targeted training. Sortable Admin List: Ability to sort by Last Modified, Usage Count, or Last Used Date. 3. Automated Hygiene: Bulk Lifecycle Actions: The ability to bulk-archive or delete responses that have a "Last Used" date older than 180 days. Proactive Alerts: Notifications to Admins when a high-use response hasn't been modified in 12+ months to trigger a content review. Business Value Quality Assurance: Ensures customers always receive the most current, branded, and accurate instructions. Targeted Education: Admins can identify agents who need coaching on using the internal toolkit to improve their "Average Response Time." Admin Efficiency: Shifts the audit process from manual "polling" to data-driven decision-making. Onboarding Speed: New agents can rely on a lean, curated library of high-performing responses rather than 500+ confusing options.  At the very least could we have an API for this information?

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.