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.
Hey everyone!I’m currently helping run a content-streaming platform that offers live sports, movies, and anime via Android APKs. We’ve started to grow our user base, and support requests are increasing — mostly about login issues, app errors, and device compatibility.I’m curious how others in the entertainment or app-based industries manage their support channels. Do you prefer Freshdesk over Freshchat for mobile-first users? Any automation tips for repetitive issues? How do you deal with users on modded Android OS or low-end phones? Would love to hear your workflows, tools, or any customer success tips that work well for high-volume but low-ticket-value platforms.Thanks in advance!
Using MSP mode, I have Quarterly reports that are sent out. Due to not having an option to automate these on a Quarterly basis I have set them up Daily and just turn them on each quarter, let them run and then turn them off again. (Not ideal and I have asked if a Quarterly option will be available - still with FreshService Support).Until such time as this is an option it would be good to have an option at the right hand side of the report:to turn these on rather than having to open each report, click on Export, click on schedule report and turn on
Training becomes more effective when users can apply concepts instantly. Integrating simple learning tools like an interactive calculator (similar to https://ti84calculatoronline.org/) within Fresh works products could help users test formulas, metrics, or logic in real time. This would bridge the gap between training and real-world usage, improving understanding, confidence, and long-term adoption.
Content platforms and tech podcasts receive feedback frommultiple channels such as websites, apps, and communities.A unified CSAT feedback loop inside Freshdesk would helpcreators and support teams analyze user satisfactionmore effectively.We tested a similar feedback workflow on our platform:https://www.smartsplay.com/This approach helped improve response trackingand engagement insights.
We have a serious need for the ability to use placeholders within the action node for adding a name for the approval groups. Without this, we are having to run additional API requests; 1x to GET the approval groups, 2x to GET 2 different custom objects, and another to PUT or POST either creating the approval group or update the approval group. This would be a huge performance saving feature.
We have teams who want to work more transparently with each other due to the nature of work on tickets they are submitting. There are often times they need to refer back to an older ticket for information that was provided. If John is out, he may need to search that information on a ticket James submitted. The team shares the tickets they create with each other for just this reason.The catch: although they can view the “shared with me” tickets, they can’t use the search feature in Freshservice to search those. It surfaces only KB content and their own tickets. Can this be changed to include also tickets shared to that requestor?
It would be really helpful to have markdown support on the Editor. It is really painful to format the solutions.
Traveling can sometimes feel overwhelming—between managing schedules, packing, and making sure everything goes smoothly. One thing that makes a big difference is reliable transportation. Having access to car rental services in Florida not only gives you the freedom to explore at your own pace but also takes away the stress of depending on public transport or ride-sharing.
Currently, the system forces a ‘Related Ticket’ to be a ‘Child Ticket’ and the same ‘Type’ of ticket (Incident to Incident, Service Request to Service Request).Currently, when a Child Ticket is re-opened, it will force-re-open the Parent Ticket. When a Parent Ticket is Closed, it will Force Close the Child Ticket. This appears to be hardcoded functionality with no ability to change. “Related Tickets” should NOT be dependent, they should be “related” as in “linked” - e.g.:I want to be able to add links to tickets - any status, any type - to other tickets. Ideally, I’d be able to say “caused by” or “preceded by” or “caused” or “ongoing” Furthermore, it would make sense if in the “Similar Tickets”, Freddy did better at suggesting not only similar titles/Subjects, but also tickets from the same person, department, and that had the same Assets attached.
Within a workflow I may want to take different actions based on a condition however later actions may be common regardless of result of that condition.My idea is functionality be added to allow modules (action/condition etc) within a workflow to be joined together with connectors manually.Image below demonstrates a simple example. Were I able to add the green ling the action within the red box could be deleted as it’s a duplicate of the line above.
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!
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