Olemme auttaneet yrityksiä valitsemaan
parempia ohjelmistoja jo 15 vuoden ajan

Freshservice
Mikä on Freshservice?
Freshservice on älykäs, sopivan kokoinen IT-palveluhallinnan ratkaisu, joka tarjoaa työntekijöille poikkeuksellisen hyvän käyttökokemuksen helppotajuisen, skaalautuvan ja koodittoman ratkaisun ansiosta. Freshservicen huipputason tekoäly- ja koneoppimisominaisuuksien ansiosta organisaatiot voivat keventää IT-tukihenkilöiden työtaakkaa ja parantaa heidän tuottavuuttaan automatisoimalla arkisia tehtäviä. Tekoälyominaisuuksiensa lisäksi Freshservice on riittävän joustava ja skaalautuva sekä vanhoja järjestelmiä käyttävien että modernien yritysten käyttöön.
Kuka käyttää tuotetta Freshservice?
Freshservicen asiakkaita ovat esimerkiksi managed services -palveluntarjoajat, rahoitusalan organisaatiot, oppilaitokset ja monenlaiset valtiolliset organisaatiot.
Mietitkö vielä, onko Freshservice hyvä valinta?
Vertaa suosittuun vaihtoehtoon

Freshservice
Arvostelut tuotteelle Freshservice

Probably the best tool for Help Desk Management
Kommentit: This is probably the best I used for ticketing. The support is really good, the only bad thing is that you have to contact mostly via chat.
Hyvät puolet:
The features it provides are really good. The ticketing flow is easy to follow, we can handle our Service Catalog, integrate with Active Directory, manage Asset Inventory and now we started using the Project management tool.
Huonot puolet:
The configuration (Initial Setup) is kind of complex. Design the flows is friendly, but complex if you have many rules, but the good thing is that support guides all the way during this process.

You can do a lot of great things with Freshservice
Kommentit: Complete platform for IT service management and reporting on client needs. It gives me the ability to develop material that can be provided as assistance to customers, as well as report back internally to the team and to top board management.
Hyvät puolet:
I appreciate that it is not only affordable, but also demonstrates a lot of value due to the fact that it comes with a lot of features considering how much it costs. FreshService is capable of competing with ServiceNow in terms of IT service management, and I am accustomed to utilizing ServiceNow.
Huonot puolet:
The constraints placed on portal design, in addition to the requirement of having HTML coding skills. I have not been able to determine whether or not it is possible for us to have parent portal sites that include kid pages, and the process of developing these pages will require experience in coding.
No bang for the buck, an overpriced form submission tool that disappoints in reporting and integration
Hyvät puolet:
Friendly user interface. Copy screenshots directly into the form (although there's a bug for the last 3 months that screenshots are displayed double in edit mode.) Plenty of fields to configure for more complex workflows.
Huonot puolet:
Default categories and labels with awkward naming (synonymous use of "Tickets" and "Incidents" for "Issues", "Change" for "Change Request", "Problem" for "Bugs") No possibility to convert issues to change requests. Agent needs to recreate the entire case in the back resulting in significant adminstrative overhead. Reporting is practically inexistent. REST API not covering many functions and object attributes. (You cannot substitute reporting externally.) HTML editor limited and bugged. (CSS code in support articles not supported, Bootstrap not supported, code gets changed or reformatted upon saving articles) No access to the file and image repository. Frankly, with every new cosmetic change and "functionality no can do" message from the Team, I am growing more and more wary of this application. At this point, I am thinking of it as an overpriced form tool with practically no reporting, a gimped Knowledge Management base, and an asset list functionality that quickly drains your wallet. I am spending significant time rewriting issues as change requests in order to subsequently manually attach them to the original issue ticket and explain to the user why I would want to close his ticket after all. Writing knowledge articles is best done in a separate HTML editor. The Text Editor lacks basic functionality, removes formatting and images in unpredictable ways with undoing, and stores images and files in a central repository you have no access to. You might as well do that with a forms tool readily available on the internet.

Freshservice is a top-notch help desk solution
Kommentit: I use Freshservice to stay on top of my workload and respond quickly to any incidents that arise, most of which are related to technology at the company where I work.
Hyvät puolet:
The best thing about Freshservice is how simple and straightforward it is to use, both for end users and for the system administrator. Even first-time users will have no trouble grasping and implementing workflows because to the intuitive nature of the UI.
Huonot puolet:
Since I use Freshservice on a daily basis for both my job and my company, and since it is so intuitive and simple to operate, I really can't think of anything bad to say about it.
Freshservice is the best ITSM, our users love it!
Kommentit: After using several ITSM tools, Freshservie deployment was very easy and it fits 100% with our needs at an affordable price.
Hyvät puolet:
Ticket management is great by itself but if you uses it with workflow automation it's awesome. You can configure as many user portal as you want and it was a requirement. Inventory is also great module. Project management help us not only in the helpdesk team but also in other areas of the department.
Huonot puolet:
The knowledge base could be better. You can't create more than two category levels and sometimes is not enough.