OpenAPI has been a standard for years. Especially today when engineers are using AI tooling to develop integrations quickly, you should provide a version of your API spec that can be easily understood and consumed by humans as well as automated agents. Having that would drastically reduce friction for your customers who use the FreshService API or who struggle with shortcomings and poor support for the Effiy offerings.See this topic for information:
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.
We are wanting to have a field added so a requester can type a topic (ie. printers) and that will provide option(s) that when selected, fills in the fields at the “Category” level and should also extend into Subcategories / Items without having to search specifically at that level to assist the requester or agent in finding what they’re looking for.Ideally, if I search “Printer”, I would be presented with the available items I can select from and choose the appropriate scenario.Hardware (Top-level category containing search term) |_Printer |_Purchase |_Printer JamandSoftware |_Windows |_Add A Printer (Item-level category containing search term)This would alleviate so much hunt/peck for requesters, especially new employees to the organization.
I am curious if the ability to sync the Service Desk Rebranding from a Sandbox to Production will be allowed at any point in the future? We are working on finishing touches to our Sandbox and getting prepared to schedule those changes in Production, and after looking at the Modules support for sync, we saw that Account Settings are not supported. Will this be allowed at any point in the future?
Add the ability to disable or hide fields from use for asset types in which they are default. (For example, be able to hide the “Last login by” field from Computer fields.)Presently, there are a good number of fields with a good number of asset types that are inapplicable for our organization and it would be nice to be able to hide the fields to keep asset entries neat and tidy. At the moment the only workaround is to completely recreate the entirety of an asset type and all of its sub-types, which is unideal.
I think it would be a good thing to allow the admin to be able to modify the hierarchy of asset types.Right now, we have a fixed root/child items (i.e. Hardware → Computer/Printers/…..)If for some organizational reason some type doens”t fit well for the company administrating the platform, the onlu workaround is to disable that category, rename it and create a new category where the admin want it to be, and after that still need to add the fields (and many of them already exists in the “misplaced” category).I had the case not so long ago where the users saw that a server is a child of computer, and wanted it to be straight under the hardware node (which i can understand since a computer nowadays is a workstation contrary to a server whic is more of a “Service Station”) Besides, when modifying this, after, all inventory records which were bind to that category needs to be edited to point to the new one.
The employee onboarding captures all data from the onboarding submission into text data. This makes functionality in other parts of FreshService not work correct. For example This text data does not flow into the mobile app because the mobile app only shows ticket description and ticket field data. It is impossible to work on the ticket. You can’t use business rules on any of this text data or questions because business rules rely on fields. You are unable modify any of the answers captured during the stakeholder submission process in the portal like a regular incident. Example, HR needs to change the start date, or Modify job title or name due to typo. None of this can be edited from the support portal ticket view because it’s all text data. Only form fields can be granted permission to be modified in the service portal. The onboarding module needs to have it’s own form fields in field manager. By moving the questions created in employee onboarding setup to Field Manager it fixes all of the above 3 problems.The mobile app will show everything correctly business rules will work you can modify the form field to allow requesters to view/modify as needed.
It would be really helpful to have markdown support on the Editor. It is really painful to format the solutions.
Actualmente, el formulario inicial de creación de tickets de Freshdesk dentro de Microsoft Teams muestra campos base que no pueden ser modificados, ocultados ni deshabilitados.En nuestro caso, varios de estos campos no aplican a nuestros flujos de soporte y generan confusión en los usuarios finales, afectando la experiencia y la adopción del canal de Teams.Solicitamos considerar la opción de:Ocultar campos base no requeridos Modificar qué campos se muestran Configurar el formulario de Teams de forma similar a los formularios web de FreshdeskEsto permitiría una mejor experiencia de usuario, mayor control del flujo de tickets y alineación con los procesos internos de cada organización.Impacto / BeneficioMejor experiencia del usuario final Mayor adopción del canal Microsoft Teams Menor error en la creación de tickets Consistencia entre canales (Web, Email, Teams)
Our organization receives a lot of Excel tables embedded in the email body.We typically used Outlook to quickly add or remove rows and columns without having to use Excel.FreshDesk is currently limited to using HTML Block for tables, we cannot add or remove rows and columns easily and its requiring us more time to edit tables being shared in an email body. Could we add an app or Excel capability to edit the table from within the email body directly?
Hi team. Wouldn’t it be amazing if you could clone an entire Page in Analytics with all the widgets within?Currently, you need to create a new page, go back to the original page, and clone widgets one by one to the newly created page. It is time consuming, when you have several widgets on a Page for real Analytics. We work with hundreds of KPIs and, have several reports (due to the limit of 10 pages per report), with several widgets per page, and this has taken longer than expected to get them properly set. Hope someone else misses the same. Sincerely,Elvis.
The best way to migrate Exchange mailboxes to Office 365 is to use an automated solution that would easily migrate from Exchange to Office 365 mailboxes. One tool that does this and offers numerous other exclusive features is Shoviv Office 365 Migration Tool.Feature of this tool-:• It swiftly migrates the numerous numbers of mailboxes with no limitation on size.• Options to preview added source mailboxes and filter according to the message class and Item date are also embedded within the software.• Mapping option for the source mailbox with target mailbox and search option to search source mailbox is also provided in the software.• Facilitates to migrate Live Exchange/Office 365 Public folders and Archive mailboxes into another Live Exchange/Office 365 public folders and Archive mailboxes.• A Free demo/trial version of the software is also available to check its working efficiency and functioning. It allows the migration of the first 50 items per folder. For more info - Exchange to Office 365 Migration
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 !
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