JIRA Service Desk ist eine zukunftsorientierte Service-Management-Software, die IT und Unternehmen durch eine Lösung für eine schnelle und verantwortungsvolle Beantwortung von Kundenanfragen verbindet und unterstützt.
Basierend auf der Jira Workflow-Engine von Atlassian bietet Jira Service Desk eine kollaborative, agile Plattform und Wissensdatenbank, die kostengünstig, einfach einzurichten, zu skalieren und hochflexibel ist und über eine leistungsstarke, einfache Nutzererfahrung verfügt.
- Jira Service Desk ermöglicht eine schnelle und verantwortungsvolle Beantwortung von Kundenanfragen.
- Alle Tools, die Nutzer*innen benötigen, um ihr Team zu stärken.
- Richte erweiterte SLA-Metriken ein und berichte in Echtzeit über die Leistung.
- Bietet eine moderne, leistungsstarke und einfache Nutzererfahrung.
- Hilf deinen Kunden, sich selbst mit einer intelligenten Self-Service-Wissensdatenbank zu helfen.
- Für die Verwendung des intuitiven Kundenportals ist keine Schulung notwendig.
- Automatisierungsregeln, mit denen Nutzer*innen sich wiederholende Aufgaben rationalisieren und Agenten mehr erledigen können.
- Echtzeitberichte bieten Nutzer*innen und dem Management vollständige Transparenz.
Jira Service Desk basiert auf der Jira Workflow-Engine, einem führenden Anbieter im Magic Quadrant von Gartner, und wird von mehr als 22.000 Unternehmen weltweit eingesetzt. Jira Service Desk bietet Anwendern ein modernes, flexibles Service-Desk-Erlebnis für Kunden und ihr Service-Desk-Team. Begeistere deine Kunden, verbessere die Effizienz und steigere die Geschäfts-Performance. Jira Service Desk lässt sich direkt in Jira Software integrieren – die Issue-Management-Software, der von über 50.000 Kunden weltweit eingesetzt wird.
Gestalte auf der Firmenwebsite die Bedeutung der IT für Unternehmen neu.
Overall we are very happy with Jira Service Desk; it has allowed us to provide a higher level of support to users than our previous service desk, and non-profit pricing was very beneficial for us. The software is usable in its default setup but we have found that there is still plenty of customisation that can be done if needed to suit more complex requirements.
I find the UI of Jira Service Desk very clean and modern compared to other service desks software on the market. Included with the service desk is a customisable user-facing portal for users to raise tickets in, which proved very popular with staff when raising tickets alongside traditional email tickets. Due to the way Jira splits service desks into different projects, we were able to create service desks for other departments in the organisation which helped improve productivity and workflow. There are some very useful and well-designed default reports included for ticket statistics (which can be used to keep management happy!). We found the default setup of Jira Service Desk fit our needs very well, but it is very easy to customise ticket workflows and other features to suit more complex needs.
For a service desk technician using Jira Service Desk the back-end UI for managing tickets can be a little overwhelming, however this can be fixed by editing the default workflows for tickets to hide not required information and details. The administration settings are somewhat unintuitively set out for system administrators, but once you get to grips with the layout it becomes easy enough to find what you need from the settings page. We found the instructions on the Atlassian website for setting up an external redirect with a custom URL in IIS a little sparse on detail, but a quick trip to the Atlassian forums cleared up any queries we had with the process.
JSD offers a lot for any company needing to maintain a service desk to manage the support requests it handles from its clients/customers. Because it is a Jira (Atalassian) product, it is most likely utilized along with other Jira tools, and plays quite well with those. Due to this integration aspect, thought, the layers of security necessitated within user settings requires a considerable amount of learning/training, which is not easily attained without paying for it from Atalassian. And, while I understand, respect (and even applaud) the market-oriented principle of this, it does seem a bit intentional that there are no reliable helps available outside of Atlassian (for example, any tutorials you will find on YouTube for assisting with certain user configs, settings, steps, etc. are applicable to much older versions of the software, and to a great extent, are not applicable to the current version). This would not be a negative aspect if Jira did a much better job at keeping their own internal (free) help docs, etc. up to date, so as to apply to the current version, as well. Instead, if one wants highly dependable "helps" it appears the best way to achieve that is to pay Atlassian for their training courses (at prices that are obviously calibrated toward larger companies/corporations. And blindly undertaking such would seem risky if judged by the extent to which their free user tools are kept up to date. This is not, to my knowledge, the common experience with most apps.
- Lots of tools in one place
- Integrates well with other apps (especially other Atlassian products)
- UI is clean and user friendly (customizable to a sensible extent)
- Contains useful metrics that are easy to configure and gain reports from
- Has multiple layers of user settings available for custom configuration to correlate to preferred levels of access among agents, customers, etc.
- Email bounce in frequently fails (bugs?)
- Depth of Jira admin user knowledge required for strong mastery of this app; time consuming to acquire a reliable user knowledge (which is necessary to utilize the app with the least bit of efficiency)
- Help docs, support mechanism unreliable/outdated (needs to be fresh and current to be applicable to present version of app)
- Confusing settings requirements for some user modifications needs (esp. where mapping/editing workflow schemes are concerned)
- Completely inadequate amount of general helps/tutorials available outside of Atlassian (YouTube, Google search, etc. for example) which seems a bit suppressed by design. Atlassian offers extensive training, but at a premium cost.
- Costly for the overall effectiveness it provides, after factoring these negatives along with the user time required to really learn the application.
Customization, integrations, workflows, SLAs
Newbies to JIRA Service Desk can get a service desk project up and running in less than 30 minutes. If your organization is already using JIRA for issue tracking, then having a help desk with Service Desk is a no brainer. It allows you to integrate software teams and IT teams better within the same ecosystem.
The benefit of JIRA Service Desk, when compared with other help desk tools, is the customizability of your workflow. You can set up a workflow to be simple (with Open > In Progress > Closed statuses) or complex (with other statuses like On Hold or Waiting for Customer).
SLAs are highly configurable, with the power of JIRA's JQL functionality. So one can conjure up a query to fit their SLA needs. With the addition of custom fields, a Service Desk administrator can create fields to capture important information to streamline the help desk process.
Having Confluence also provides more benefits in which you can integrate an existing knowledge base space to a help desk project and self-serve your customers.
Finally, being in the Atlassian ecosystem enables you to add additional functionality and enhancements with the use of Apps. There are close to 1500 apps available for JIRA, and many are constantly updated by the app developers.
Administering JIRA Service Desk (and JIRA in general) can be daunting for a new user. With a number of customizations that one can do in a JIRA application, there will come a time where there can be a performance impact on the environment if the application is not governed well.
The Customer Portal (customer facing interface) is spartan in terms of customization. You can only customize so much, but it is limited in terms of branding it to suit your company's design specs.
With the help of Service Desk we get feedback from users about the bugs they find in the product. As the result, we fix them really fast. By adding fields that users need to add while submitting bug, we decrease time that is needed to reproduce bug or clarify the issue. Also, we can communicate with user directly if needed.
At the same time user can always get back and see status of ticket they submitted.
Also, it says a lot when you see Atlassian using its own product and using it really well.
When you use this application as an addition to JIRA, it is a great tandem. I adviced my company to use Service Desk when we were discussing how to receive bugs and ad-hoc requests. We are using this application fro several years and we do not think about changing it.
The only bad point that I can mention about Service Desk is its price. A lot of clients I worked with complained about it. They manage really carefully the number of users that are Agents (users you actually pay for), and get really upset if they were not carefull enough and their bill was higher then they expected.
It has solved some of our immediate business needs out-of-the-box or with moderate configuration effort. But as a full solution it is missing a handful of simple, but crucial, features. It definitely "feels" like a second version. It needs a third.
JSD is relatively intuitive and easy to learn without needing tons of documentation. Initial pricing is attractive. A decent plugin community fills some gaps, but be expected to pay on top of the initial JSD pricing.
Many "obvious" features are either missing or do not work as expected.
For example: in many cases, once an internal user is added to an issue, they no longer receive notification about internal comments. This is completely unintuitive, unexpected, and has caused many people frustration: https://jira.atlassian.com/browse/JSDSERVER-3410
Another example: Email traffic about an issue is *always* public. Do not allow your staff to reply to JSD's emails as customers will also get emailed a copy! https://jira.atlassian.com/browse/JSDCLOUD-3499
The worst part is, despite there being a few years' of discussion, and new comments added monthly by newly-affected JSD customers, Atlassian has no comments on the issues.
In some cases a plugin (more $) can help, but in some cases even the plugin manufacturers can't help as JSD doesn't expose enough info in their plugin API.
Weiter unter folgen häufig gestellte Fragen über Jira Service Desk.
Jira Service Desk bietet folgende Kostenpläne an:
Beginnt ab: 10,00 $/Monat
Kostenlose Testversion: Verfügbar
Jira Service Desk bietet die folgenden Funktionen:
Jira Service Desk hat die folgenden typischen Kunden:
Großunternehmen, Mittlere Unternehmen, Non-Profit, Kleine Unternehmen
Jira Service Desk unterstützt die folgenden Sprachen:
Chinesisch (vereinfacht), Chinesisch (traditionell), Tschechisch, Dänisch, Englisch, Französisch, Deutsch, Ungarisch, Italienisch, Japanisch, Koreanisch, Norwegisch, Polnisch, Portugiesisch, Russisch, Spanisch, Schwedisch
Jira Service Desk hat folgende Preismodelle:
Jira Service Desk unterstützt die folgenden Geräte:
Android, iPhone, iPad
Jira Service Desk kann in folgende Anwendungen integriert werden:
Amity, Anypoint Platform, BigPanda, Calamari, Cayzu, JIRA Software, Monitis, WorkOtter, Workato, xMatters
Jira Service Desk bietet folgende Optionen für Kundensupport:
Häufig gestellte Fragen, Forum, Wissensdatenbank, Online-Support, Telefon-Support, Video-Anleitungen