Skip to main content

Ideas Status Pipeline

8484 Ideas

raja.pavankumar
Community Manager
raja.pavankumarCommunity Manager

Freshservice - Understanding relationship between custom objects, workflow automations and service cataloguesNew Idea

As a Freshservice administrator and application owner, one of the major challenges is to build a scalable service management architecture for your teams, especially with enterprise service management and workspaces in Freshservice, administrators will need to understand divide and conquer strategies, system dependencies and integrations with other enterprise applications available in their IT ecosystem.One such challenge is the ability to understand the relationship between your custom object databases, workflow automations, service catalogue items and forms. As businesses evolve, employees sunset their journeys, your operational platform should be upto-date.We recommend our customers to leverage custom objects in the first place for the below advantages.  Remove the need to hard code information in your automations. Minimize duplication of configurations such as duplicating form data in service catalogue forms and ticket fields. Manage configurations via APIs by integrating Freshservice custom object databases. Example: Lets imagine a service management process involving approvals for governance. Automations seize to trigger approvals to the concerned user or delegate approvals to authorized personnel, when they are no longer with your organization. Understanding which custom object databases to update, automation services and service catalogue forms that are leverage these databases need to be identified to ensure changes are in place before service management takes a hit ! Solution:Review automations and export all variables to custom objects. This will help you identify automations that have a static business logic, all variables leveraged in the automation can now be managed using Custom Objects and credentials using the credential store in Freshservice.   Build a CMDB and service management framework to manage the lifecycle of your custom objects. Consider Custom Object tables as databases managed in your asset inventory and Workflows as microservices.   Below is an example of a dependency map documented as a CMDB entry. If a change is needed to be made to a custom object, govern the process via a change request.Now, lets look at an employee offboarding process that is operational in Freshservice and a user that is part of the custom object table leaves the organization the request may not move forward as the approver is no longer with the organization, automations can now be designed to perform custom object validations and notify agents about changes needed to operations in Freshservice. Custom object databases can be managed easily by automatically create a change request in such scenarios and ensure the offboarding processes continue as defined with minimal outages and maximum visibility. The change request can now yield the below results, that will help you identify the related services that are associated to this custom object table.  Automate the process further by defining workflows that update these custom object tables via API and easily manage these routine tasks that are required to manage the sanity of your databases. Hope this helps you manage Freshservice better ! 

David-FlintoffApprentice

Convert Live Conversations into Freshdesk Tickets Using Voice-Based InputNew Idea

Hi Freshworks community,I’d like to suggest an idea focused on improving how support interactions are converted into structured tickets inside Freshdesk.The challengeSupport agents often handle conversations across calls, internal discussions, or quick handoffs. Important details issue summaries, next steps, or follow-ups—are usually typed into Freshdesk after the interaction, which can slow agents down and sometimes lead to incomplete ticket context.The ideaIntroduce voice-based input as an optional layer through integrations with tools like Gennie, allowing agents to speak ticket details naturally and sync them into Freshdesk.Potential use cases include: Converting call conversations into ticket descriptions using voice Adding internal notes or summaries hands-free Creating follow-up tasks or reminders without breaking flow Capturing key customer context immediately after interactions Freshdesk would continue to be the system of record, while voice acts as a faster input method during high-volume or real-time support scenarios.Why this could help Faster ticket creation during busy support hours More accurate and complete ticket context Reduced agent fatigue from repetitive typing Improved response quality and follow-through Would love to hear from other Freshdesk users: Where does ticket creation or updating slow agents down most? Would voice-based input add value to your support workflows?