Kayako is a help desk / ticketing product and is available is both SaaS and on-premise configurations. Is is built in PHP and uses my SQL. The product competes with HelpSpot, ZohoSupport, Freshdesk and Zendesk.
The Kayako Engage edition may be deployed as a live chat system without ticketing at a reduced cost, featuring click-to-call and site visitor monitoring for customer targeting and engagement.
$29
per month
ServiceNow IT Service Management
Score 8.4 out of 10
N/A
ServiceNow is a fast-growing service management provider that went public in 2012. Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management, and (on the higher tier ITSM Professional plan) ITAM and software asset management.
Kayako is a great tool for the service industry. I think it is better suited for businesses that do 1-off interactions rather than using it to manage and maintain a larger repeat customer base. This was just our opinion based on the industry we are in. We are in the hosting …
When it works, It's without a doubt a great help desk solution. It is perfect for our usage, and have rolled it out company-wide. It's great if you have multiple departments. We have it set up so most items come through a single desk that then hands out tickets to their proper department. There may be cheaper options for smaller organizations but for one that is as service-driven as ours, we really think Kayako is a great fit.
In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
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.
When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.
Departments need a bit of work. Even though you can have multiple departments, the only changes that can be made are globally. If you want independent queues within the departments, you have to do a lot of work that can be very confusing.
Survey system is not up to speed. Kayako really needs to add Net Promoter Score into their system. Also, if a staff user removes their name from an incident ticket, it removes them from the survey so you really can't even get a good estimate of how well your staff is in the eyes of the customer.
Very difficult to implement when you already have a customer base. Setting them up in organizations is difficult. Also, the sign-up for new customers is quirky. If you send an email to Kayako, it will say you are not an authorized user, however, it will store your email address. If you try to send an email a second time, it will go through. This is one of many reasons why we decided to move from Kayako to Oracle Service Cloud.
It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!
We are grandfathered in on their old Software-assurance pricing and our continued use costs us only a few hundred dollars a year (excluding hosting expenses)
Our team's processes are now heavily ingrained in the system
We have not been shown a more compelling option that is more cost-effective while still offering all the features we've come to expect
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
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.
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
We were using Spiceworks for a few years before switching to Kayako but found that it wasn't as customizable or as user friendly for our customers. The SNMP scanning and inventory features with Spiceworks was nice but we needed more of a Help Desk that would allow us to scale our services to more companies.
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
Tickets were definitely responded to faster once we implemented the audible alarm that would go off when new tickets came into the queue. This was possible because of the API.
Since the system was email based we could set our monitoring software up to generate tickets automatically via email for customers when it found something out of the ordinary.
Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.
