Jira Service Management (formerly Jira Service Desk, now including features from the former Mindville Insight, acquired by Atlassian in June 2020) is a service desk software that is purpose-built for IT, service, and support teams. The software provides everything IT and support teams need out-of-the-box for service request, incident, problem and change management. Jira Service Management integrates seamlessly with Jira Software so that IT and development teams can work better together. Users…
$0
per month
Kayako
Score 6.8 out of 10
N/A
Kayako is a help desk and customer support platform that helps businesses automate workflows, improve agent productivity, and deliver personalized customer experiences across email, chat, and social media.
$79
per month
Pricing
Jira Service Management
Kayako
Editions & Modules
Free
$0
per month
Standard
$20
per agent/per month
Premium
$40
per agent/per month
Enterprise
Contact sales team
Kayako One
$79
per month
Enterprise
Contact Sales
Offerings
Pricing Offerings
Jira Service Management
Kayako
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Jira Service Management
Kayako
Features
Jira Service Management
Kayako
Incident and problem management
Comparison of Incident and problem management features of Product A and Product B
Jira Service Management
8.2
Ratings
1% above category average
Kayako
2.0
Ratings
120% below category average
Organize and prioritize service tickets
7.50 Ratings
1.00 Ratings
Expert directory
9.00 Ratings
1.00 Ratings
Service restoration
9.50 Ratings
00 Ratings
Self-service tools
7.00 Ratings
00 Ratings
Subscription-based notifications
10.00 Ratings
1.00 Ratings
ITSM collaboration and documentation
7.00 Ratings
1.00 Ratings
ITSM reports and dashboards
7.50 Ratings
00 Ratings
Ticket creation and submission
00 Ratings
7.00 Ratings
Ticket response
00 Ratings
1.00 Ratings
ITSM asset management
Comparison of ITSM asset management features of Product A and Product B
Jira Service Management
10.0
Ratings
20% above category average
Kayako
-
Ratings
Configuration mangement
10.00 Ratings
00 Ratings
Asset management dashboard
10.00 Ratings
00 Ratings
Policy and contract enforcement
10.00 Ratings
00 Ratings
Change management
Comparison of Change management features of Product A and Product B
Jira Service Management
7.2
Ratings
15% below category average
Kayako
-
Ratings
Change requests repository
7.50 Ratings
00 Ratings
Change calendar
6.50 Ratings
00 Ratings
Service-level management
7.50 Ratings
00 Ratings
Self Help Community
Comparison of Self Help Community features of Product A and Product B
Jira Service Management
-
Ratings
Kayako
1.0
Ratings
155% below category average
External knowledge base
00 Ratings
1.00 Ratings
Internal knowledge base
00 Ratings
1.00 Ratings
Multi-Channel Help
Comparison of Multi-Channel Help features of Product A and Product B
Great to manage your issues in a clear and centralised way. If your development teams work with Jira, it will all naturally come together. Great way to manage the issues from end to end. - Very flexible if you have people who understands the set up and is able to configure it for your needs - Maybe not the best if you want something with very easy set up
Kayako is suited for a small company that is just getting started. We are in the web-hosting industry and it was very hard to fully adapt the system the way we would have liked to. Kayako would be very good if you were hosting an ecommerce shop or customer service business where you can look at each customer interaction as separate and not over a long-term period.
Gives a very good report on an individual level of what is being done for a customer or corporate issue.
Easy to understand who has what, what the tickets are about, how long they have been opened and how many times the customer/employee have gone back and forth with each other.
Some of the built-in functions and workflows are surprisingly limited given the fact that you can customize a lot with JQL. These limited areas do not allow you to use JQL. For instance, the built-in notifications are lacking. They have one that is great-- "notify on critical ticket creation"-- EXCEPT that it does not allow you to notify a group or anything, only individual users.
The ticket interface is a little odd for agents. Changing the status is not a simple drop down from unassigned to open to in progress to pending, etc. There are a couple of tabs ("investigate", "pending", "workflow") where you can change the status in different ways. Maybe I am just not used to this way of doing it, but I feel like it could be simplified.
It can get complicated deleting/changing some of the out-of-the-box fields and rules, because you never know what will break workflows or other automated/built-in features.
I have not tried to use the actual Workflow function for awhile so this issue may have been resolved. When we tried to use it, it was cumbersome and did not offer much flexibility as to meeting the needs of different departments.
This may no longer be an issue but if someone was knowledgeable about KQL and knew how another department was set up, they could write a report accessing their data even though they do not have permission to view/edit that departments data.
Perhaps adding the function of "Read Receipts" to end-users when opening a ticket.
When a ticket is closed, automatically include information from the initial creation of the ticket so the end user knows at a glance what issue has been resolved without looking up the Ticket ID.
I am no longer with the company that was using this, and they were recently bought out by a larger organization that uses an internally developed software suite. It is unlikely for that reason that they will renew or keep any service with Kayako.
I have given this rating because, in my opinion, I don't see any downsides of Jira until now. We can customise workflows based on the project needs, including task workflows. Jira is very extensible, which is one of its most important features.
I gave JIRA a 9 rating since for me JIRA works according to its purpose. Since there is a customer portal, our clients can leave a comment or communicate with us using the PR ticket that way it is easier for us to also request any additional information we need for our investigation.
Three years in we are about as happy with Kayako as we could be. We've had several employee's leave and on-boarding new hires was easier than it has ever been as things are uniform and consistent across the entire application.
We chose Jira Service Management due to its easy integrations with the rest of the Atlassian tools, as we have also invested in those. For the price, the ability to add or remove agents, and the cost being reflected in that, it was an excellent medium for us. For the foreseeable future, I do not see us moving off this platform.
Kayako is way more scalable than Spiceworks' helpdesk offering. We had trouble visualizing our current layout within their environment. Zendesk was priced quite a bit higher than Kayako while offering similar functionality. It didn't make sense to want to migrate to a new platform. We have also evaluated various Sharepoint-based help desks, but their speed and reliability did not match our standards for what a help desk should be.
Kayako has helped our business to grow by allowing us to scale our help desk to accommodate more client companies in an efficient manner.
Kayako has allowed our customers to have more direct control over their help desk tickets and has made it easier for them to interface directly with our help desk staff.
The built-in chat features in Kayako that tie to our main website has allowed prospective customers to chat with our sales teams right away, resulting in more business.