Hi Freshworks Team and Community,I am currently developing custom integrations for self-service customer support portals to help reduce overall incoming agent ticket volume. A feature we desperately need natively inside Freshdesk/Freshservice portals is a low-latency, client-side calculator widget builder. To test how a tool like this impacts user interaction and reduces ticket deflection, I built a standalone, responsive calculator engine using vanilla JavaScript data arrays. It handles complex, multi-variable logic loops directly in the client's browser (calculating dynamic price variations and nutritional tracking points simultaneously depending on size parameters).You can interact with the live layout configuration and check out the responsive UI performance model here:Live Development Proof of Concept: https://swigdrinksmenu.comHaving an identical native widget block available inside our portal layout customizer would allow teams to build instant quote calculators, shipping estimate fields, or data sheets directly into their knowledge base paths without relying on heavy third-party plugins or external API calls.Is anyone else currently utilizing custom JS blocks to achieve this layout inside their customer service portals, or are there any roadmap updates for native dynamic calculators?
Instant response time is something all of us strive for, but that is very difficult to meet when interacting with human agents. As a chat queue increases, the response time increases and our customers start seeing messages like "Replying in under 2 minutes" or "Replying in under 35 minutes"While our customer is waiting for an agent to reply, can we allow our agents to play a small mini-game that can keep them engaged.
I was creating some Change templates for monthly maintenance that involves changes (like updating Freshservice Workflows, for one). It would be really nice to be able to build and assign the tasks from the template rather than having to build them each and every month. If there is a way to do this I can’t seem to find it. Thanks!
I’m sure that most of us will agree that the vast majority of IT services will require the ability to raise related Incidents (Report an Issue / Ticket) and/or Service Requests. Therefore for every new IT service being provided one needs to create both a new Category/Sub-Category in the ticket Field Manager and a Service Item.Our system integrator helped us to design a workflow that associates a Service Item with its corresponding Category/Sub-Category via a Custom Object. This is required for analysis and oversight. However, I strongly believe that there should be a built-in feature that allows you to correlate or align these two aspects (in the Field Manager or whilst editing a Service Item). I would like to hear your thoughts on this. What is your approach?
Dear Freshservice Team,I would like to submit a feature request to enhance ticket handling efficiency within the platform.We propose adding a dedicated “Observations” section within every ticket, allowing agents to document key findings, actions taken, and important notes in a structured and easily accessible way.Purpose and Benefits:Reduce time spent reviewing full internal and external ticket conversations Provide a quick summary of investigation progress and actions taken Improve visibility of ticket status for agents handling follow-ups Enhance shift handovers and team collaboration Increase overall efficiency in ticket resolution and response timeSuggested Functionality:A clearly visible “Observations” tab or panel within each ticket Ability for agents to add timestamped notes after each action or investigation step A structured format for quick summaries of progress Easy access during ticket follow-up without scrolling through entire conversation historyThis feature would significantly improve operational efficiency and agent productivity, especially in high-volume support environments.Thank you for considering this request.
Please can a CI module please be added to Freshservice. This is a massive part of the ITIL framework and an important thing for all Service Management teams to do. At the moment our process for this our clunky spreadsheets.
The addition of a dedicated task module in Freshservice would provide a centralized view of all tasks assigned to an agent—regardless of whether they originate from tickets, problems, changes, or projects.Furthermore, it should support the creation and assignment of internal tasks between agents that are not tied to any specific parent entity.This would enhance flexibility in workload management and improve internal collaboration across teams.
This whole tab should be a field in the Ticket Fields, which would allow us to use Business Rules to do something like mandate notes before a ticket is Closed/Resolved. I manually built a custom field and rule to do this, but it seems silly to have a whole tab for something that should be a standard ticket field.
We can configure a “Create ticket” activity in a journey. This activity creates a Service Request ticket. Currently, these tickets have to be created from scratch within “Configure activity”. We would like the ability to link the ticket creation activity to items from our Service Catalog and populate them with journey data. This saves us from duplicating work, and lets us maintain consistent behavior for services that are provided withing a journey but also provided directly in the catalog.
We need to be able to search custom asset fields that are defined as numbers. In our case we store mobile telephone numbers attached to cell phones so we normally would search by that phone number to bring up the asset. I am not sure why number fields are not searchable as it is.
Hi,I would appreciate moving all the items on the second page of the request service item to the first page, especially the "Requested For" input field and making it more visible.Because 90% of our users simply ignore or don't see it.
At the moment, there is no consistancy in functions for text editors throughout the system.In one place a text editor allows the function of using blockquotes where others don't.Some places allow the use of the HTML editor for sending mails (like sending mails from the workflow editor), in other places (like sending a mail from the Supervisor Rules) the HTML editor is not available.Can you please make all the editors consistent in functionality throughout the system?
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.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK