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

JoramP
Contributor
JoramPContributor

Built-in Password Manager for Secure Credential Storage in FreshserviceFuture Consideration

Hello Freshservice Community,I’d like to propose the idea of integrating a built-in password manager within Freshservice. As an IT service management tool, Freshservice is already a central hub for handling incidents, service requests, and asset management. Adding a secure password manager would further enhance its capabilities by allowing teams to safely store, share, and manage passwords directly within the platform.Benefits:Secure Storage: Having a password manager integrated with Freshservice would provide a centralized and encrypted space to store sensitive credentials, reducing the need for third-party tools. Access Management: Administrators could control which team members have access to specific passwords, allowing for role-based permissions and enhanced security. Incident Resolution: When resolving incidents that involve access issues, the support team could quickly retrieve necessary credentials, improving response times. Audit and Compliance: The password manager could include an audit trail, logging access to credentials to help with compliance requirements. Ease of Use: Since teams are already working within Freshservice, having a password manager as part of the platform would reduce the number of tools users need to switch between, enhancing productivity.Proposed Features:Encrypted storage for passwords and sensitive information. Role-based access control to manage who can view, edit, or share credentials. Password sharing for secure collaboration on incidents or service requests. Audit logs for tracking access to stored credentials. Password strength checks and alerts for compromised passwords.I believe this would be a valuable addition to Freshservice, enhancing security and streamlining IT operations. Looking forward to hearing your thoughts!

espolleyApprentice

v2 API - Programmatic access to attachments on tickets and conversationsSubmitted

Programmatic access to attachments on tickets and conversationsMany of our tickets contain screenshots, screen-recordings, log files, and other binary attachments — both in the original ticket description/body and in subsequent conversation entries (replies, notes, customer screenshots). Our integration needs to retrieve those bytes so we can pass them to downstream tools (LLM agents, automated reproductions, etc.).Current stateWhen we fetch a ticket via GET /api/v2/tickets/{id}?include=conversations,requester,tags, the response describes attachments structurally — we can see filenames and sizes — but we can't retrieve the actual file content via the public API. There appears to be no attachments array with downloadable URLs at either the ticket level or per conversation entry, and no GET /attachments/{id} endpoint.Inline images embedded in the HTML body of a description or conversation reference Freshservice CDN URLs that require authenticated session cookies, not API key auth, so they can't be fetched programmatically.PM task descriptions/comments have the same limitation.What we'd like — any of these would solve it - A (preferred): Include an attachments[] array on each ticket and on each conversation entry, where each entry has at minimum { id, name, content_type, size, attachment_url } and attachment_url is fetchable withthe same API-key auth used elsewhere (or a short-lived signed URL). - B: A dedicated endpoint: GET /api/v2/attachments/{id} returning the binary, authenticated with the same API key. - C: Make inline image URLs in HTML bodies API-key-fetchable (i.e. accept Authorization / basic-auth on those CDN paths) so we can resolve the <img src="..."> references already present in body/description. - D: Same treatment for the PM task API — attachments on PM tasks and PM task comments should be retrievable the same way.Inline content-type info and size up-front (without an extra round trip) would let us decide whether to pull a file at all, which matters for large screen recordings. ---Why it mattersA meaningful fraction of bug reports are only useful with the screenshot or recording — text alone doesn't reproduce the issue. Today our tooling has to surface "see the ticket in the browser" as a fallback, breaking the automation loop.

Michael B
Apprentice
Michael BApprentice

Auto-generate Freddy AI ticket summaries on resolution (plus API & webhook support)Submitted

Freddy AI Summarize is genuinely useful, but generation is fully manual today, an agent has to open the ticket, click Ticket Summary, wait for Freddy, then click Save Summary. There's no auto-generation, no API to trigger it, and no webhook when one lands.In practice this means summary coverage depends entirely on whether an agent remembered to click two buttons (even making a Summary required to Resolve or Close the ticket may help). Anything built on top of summaries, analytics, QA, post-incident reviews, knowledge mining, is working off a biased sample of tickets. There's also no way to backfill historical tickets or wire summary generation into automation.For example:A setting to auto-generate the summary on ticket resolution or closure. Maybe a toggle in Freddy AI Copilot settings. By the time the ticket hits Resolved/Closed, the summary is already there. This solves coverage in one move. An API endpoint to trigger generation: e.g. POST /api/v2/tickets/{id}/summary. Useful even if (1) ships, because it covers historical backfill and custom automation. A webhook for summary creation: e.g. ticket.freddy_summary_created with ticket_id, summary, generated_at. Eliminates polling for anyone consuming summaries downstream.Freddy Summarize is the one part of the ticket lifecycle that isn't yet exposed to webhooks or APIs. Closing that gap would multiply its value without changing the core feature.Thanks for considering!

dapplebyklContributor

View similar tickets for resolution insights - Include Problem SuggestionSubmitted

When raising or triaging incidents, it is critical that Helpdesk analysts can quickly identify whether an issue relates to an existing Problem record. While the current “View similar tickets for resolution insights” capability is valuable, it focuses primarily on past tickets and does not surface active or related Problem investigations in our experience.Enhance the “View similar tickets for resolution insights” feature to also:Search and surface active Problem records linked to similar symptoms, keywords, or categories Highlight known problem associations alongside similar incidents Provide a clear indicator when a matching or likely Problem record existsExpected benefitsImproved accuracy in linking incidents to Problems, strengthening Problem Management data quality Reduced duplicate incident investigations, as analysts are guided towards known issues Faster triage and resolution, with visibility of ongoing investigations and workarounds Better root cause tracking, ensuring incidents are consistently tied to the correct underlying issueExample scenarioAn analyst logs a “Citrix login failure” ticket:Current behaviour: Similar incidents are shown Proposed behaviour: Similar incidents shown ✅ Active Problem (e.g. Citrix authentication degradation) also surfaced ✅ Analyst links incident directly to Problem ✅ Summary Extending similar ticket insights to include Problem record matching would significantly improve triage accuracy, reduce duplication, and strengthen end-to-end Problem Management within Freshservice.

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.