What is your primary use case for Freshservice?

We are using Freshservice for the IT ticketing system for business users.

We use the solution primarily for ITSM, but also in the capacity of ESM. It incorporates ITIL elements such as changes, problems, asset management, and ticketing, which is the main concept in use.

We use it for our case management solution, knowledge-based repository, and for service delivery case management as well.

We are using Freshservice for IT service management.

We primarily use Freshservice for ticketing, contract management, and asset management.

It's a major lead to work with the IT architecture.

I use Freshservice in my company as an ITSM tool for incident management, service requests, and change requests.

We manage all tickets and service requests needed for our company. We started to offer it for IT mainly to manage all requests and ticketing. There are some Oracle-added services like HR that is also integrated, for onboarding and offboarding.

I use Freshservice as an attendant for the internet in the legal department of a real estate company.

We use it for IT service management. We use it for HR service management. We also use it in an operations capacity in combination with some other tools. We use a combination of Freshdesk, Freshservice, and Freshchat. We use the whole suite. We're the third largest customer of theirs. We have the Enterprise plan, and we have its latest version. We are in beta testing for another upgrade that they're doing, but it is still in beta. So, it is not live yet. It is a cloud solution. Freshservice owns everything. We just use it as a cloud platform.

We're using the product for an HR service center.

We use it for receiving internal services provided by IT, HR, VR, facility management fleet, financial affairs, and legal affairs. It is used for any service provided internally by our departments. We have a large number of branches and departments. We have about 40,000 requesters.

At my previous organization, we had an alliance partnership with Freshservice. Part of that alliance involved me implementing Freshservice for North American and Europe clients. Freshservice is an ITSM product. The PLC would be done by the thresholds and as part of the alliance, and we would implement the Freshservice ITSM solution for the clients. It's completely based on the customer requirements, which modules need to be implemented. We will do the data collection, the requirement gathering, et cetera, and we will do the solution and implementation for the Freshservice to cater to the client's needs. As part of this, we'll do the infra, we'll do automation, orchestration, and everything as part of this integration with multiple sources. We'll do the portfolio management.

We use the solution primarily as a ticketing system and help desk.

I was mainly using it for the functionality related to changes, such as tracking and reporting production changes going into our live systems. I also used it for APIs for the automatic generation of changes based on triggers from Jira. In terms of deployment, I'm pretty sure it was SaaS, and in terms of version, it would've been a fairly recent version because they'd only been using it for about a year or so.

We are using Freshservice for customer service.

We have only started the process of certification with Freshservice. We are in a training phase right now.

We extended Freshservice for one of my customers to integrate their business workflow. If the customer needed a new mobile, VM, or something else, they traditionally use a portal, but we have changed that. We designed an extension to manage business demands. In the past year, we've been implementing customization for change management.

It is a solution for help desk ticketing, as well as for knowledge base and inventory. We also deploy a fresh service agent that actually goes and gets installed on all of our PCs and any of our computer clients within the organization. That provides Freshservice with inventory information so that we can go and track assets. I am currently using the most recent version of it. It is cloud-based, so it automatically updates. It is a public cloud, though it is accessed through Okta SAML single sign-on. It is private in that aspect. I have a feeling that their services are on an Amazon Web Services server, but I could be wrong.

We're primarily using the solution for incident management. We use it for ticketing for end-users. We are using also all the functionality around change management, release management, and this year we implement project management and software license management. We also make use of the analytics.

We use it for IT help desk purposes and tracking the inventory. Specifically, we use it to do ticketing for the end users to handle IT requests.