Find, vote on and share ideas for Freshworks products. Here is how it works and what happens next.
Every idea has a status. It shows where the idea is today.
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.
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.
Six questions most people ask before they post.
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.
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.
You get an email when the status of your idea changes. To follow an idea you did not post, subscribe to it.
An idea can be closed for one of these reasons:
Closed ideas stay searchable, so you can still read the comments.
The quickest way to make an impact is to back an idea that already exists.
Open the idea and select the vote button. Voting shows us which ideas matter to you. You need to be signed in to vote.
Open the idea and add your comment. The most useful comments say:
"I agree" helps less than a short example from your own work.
Select Subscribe on the idea. You get an email when the status changes or when someone replies.
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.
Hi there, I know I am not alone in my despising of the documentation process and it is quite a job keeping up with the changes across all of our vendors. That said we are on the make the service desk smarter (using Freddy) kick like many others.I thought it would be a great idea to link to the vendor help pages that they already have written and maintain. It felt great not having to reinvent the wheel if you will. Then I discovered (and confirmed with support) that Freddy does not know about Solution Articles using External URLs even though we entered the keywords and the URLs are public. So the is the jest of my idea is to allow Freddy to index articles using external URLs. Thanks,Steve Stryhalaleck
Good morning, Freshdesk Community!I'm reaching out to share an idea that could enhance our experience when creating knowledge base articles. Currently, I'm facing a challenge with consistently formatting headings. Each time I create a new article, I find myself spending significant time manually adjusting the font, size, and color of my headings (especially Heading 1) to maintain consistency across articles.To streamline this process, I propose the introduction of a template-based system for paragraph formatting. This system would allow users to pre-set styles for different text elements such as headings, normal text, quotes, etc. Once set, these styles would automatically apply when creating new articles, ensuring uniformity and saving valuable time.I'm curious to know if anyone else has encountered similar challenges and if you have found any workarounds. More importantly, I believe this feature could be a valuable addition to Freshdesk, benefiting all users who regularly contribute to the knowledge base.I look forward to your thoughts and votes on this idea!Thank you for considering this suggestion.
Over the past 6 months I have built out our entire Production Environment in the sandbox spending no small amount of time on Analytics and Custom Objects. After syncing everything to Production, yesterday in preparation for a GO LIVE Training on MONDAY I found that I cannot sync my weeks worth of work up to Production from the Sandbox. Why, oh WHY? PLEASE make this something that can be synced and spare future admins weeks of wasted work. Custom objects also? At least this will only take me a couple of hours… but the Analytics is going to keep me working 20 hours a day from now until Monday.
We would like the ability to delegate approvals to multiple users with the option to either require all delegates or only the first responder. A lot of times we don’t have another sole individual who can cover off on the original approver’s knowledge/role. Being able to elect multiple delegates would help alleviate that.
The on-call management features are great but teams are starting to ask good questions about features that are not available. Would it be possible to add the Acknowledge function to bulk actions and/or scenario automations? This would allow the agent(s) to more quickly process tickets that came in as part of an event or error. That way they would not have to acknowledge 100 tickets one at a time.
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.
It would be nice to have the option to make comments mandatory for certain options of the CSAT scale.For example: if a customer wants to send in a negative CSAT, they would have to add an extra comment with their reasoning.That way, there’s a higher chance of us having the required information to help the customer.
A configuration option for the cards on the Kanban View (currently in beta) to be able to select which ticket attributes/fields to display on cards (e.g. hide Status field, and add Type instead).
I am writing to formally request the addition of a new feature to the Freshdesk platform. The proposed feature is an hourly automation that operates based on the business hours schedule rather than the standard calendar schedule.Currently, the platform's automation capabilities are tied to a calendar schedule, which may not always align with the varying business hours of different organizations. Introducing an hourly automation feature that adheres to the business hours schedule would greatly enhance the platform's flexibility and efficiency, allowing businesses to better manage their time-sensitive tasks and workflows.Key Benefits:- Aligns automation processes with actual business hours, ensuring tasks are performed during operational times.- Increases efficiency by automating tasks in accordance with business hours, reducing the likelihood of delays.- Enhances customization for businesses with unique operating hours, supporting a more tailored user experience.We believe this feature would greatly benefit many users and improve the overall functionality of the Freshdesk platform. I appreciate your consideration of this request and look forward to any updates regarding its potential implementation.Thank you for your time and attention.
For the community page; it would be great if ideas that I have upvoted showed a different color in the list view. I’ll frequently scroll through and see an idea to upvote, click it and the number goes down. If there was a color differentiation between upvoted and not I would do about 50% less clicking!
I believe this must be an oversight, but we cannot edit the system email templates in Journeys. Tickets -- CheckProjects -- CheckJourneys -- Nope
I use FreshService and love the dark mode, but I still miss it in the Freshworks Community. I can’t find any option to change the theme, and unfortunately, my organization doesn’t allow installing plugins that would handle this automatically. I think many regular forum users would appreciate adding such a feature. 🙂I’m selecting the product area as Freshservice since I don’t see a more fitting option.
When you generate a document from a ticket and click “generate and send custom email”, this response message appears:“Hi XXX XXX,Your document request has been fulfilled. Please click here to access the document directly from the ticket.Regards,XXXX“It would be nice to be able to change that default text.
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
Through the Workflow Automator, we have the ability to add watchers but we do not have the ability to remove watchers.For some background, all service items that require approval for our organization get sent to an Automation Agent Group until the request has been approved or rejected. The reason behind this is that our organization has accepted that IT will not work on items without the approval when approval is required so we use our Automation Agent Group as a triage space since some of our request items have true automation through web requests to fulfil the request. The gap we have is that often times, the approver responds to the request with questions that will drive their approval decision and no one regularly monitors the requests pending approval. Since there is an Action in the WFA to add a watcher, our idea was to build a custom object that will identify who the IT Business Partner for each department is and add them as a watcher to field any questions for requests coming from their respective teams while it’s pending approval. Once an approval decision has been received, we’d like to remove them as watchers so they aren’t receiving unneeded notifications.We would love the ability to either remove individual watchers or all watchers through the WFA so that after the Approval Status changes from Requested, we can update appropriately.
We are newer customers but I have had several complaints from my agents already that they would really like a dashboard widget that shows them how many unassigned or open Tasks their agent groups have. So I came to this Idea site and found that this has been a backlog request for over SIX years!? That doesn’t give me a lot of confidence that we will see this in our lifetime...but I’m going to ask for it again. Can we please move the request for looking at Agent Groups from the Dashboard Widgets as it applies to tasks be added? My Groups Task In Dashboard | Freshworks Community
Loading your ideas...
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.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
