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
Oracle Fusion Service
Score 6.9 out of 10
N/A
Oracle Service Cloud is the help desk and customer experience management platform from Oracle. The technology was developed and supported by RightNow Technologies as RightNow CX for cloud-based call center automation, until that company's acquisition by Oracle in 2011 for about $1.5 billion.
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.
Oracle Service [(formerly Oracle Service Cloud)] is well suited for cross-channel contact center service which includes live chats, virtual assistants, email support and case management. It has a social tool that keeps tabs on your customer interactions within your social media platforms and your website. You can provide your customers with a knowledge base for self-service with information that they need by posting content and resources.
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.
Oracle Service cloud handles incident management extremely well. It can accept requests from multiple channels. That includes email, website, phone, chat, SMS & some social.
Oracle Service cloud provides a knowledge base that can be used by customers or by agents. It can move consumers to self service for most issues. It also has good feedback from customers and agents so that the knowledge can continue to be updated to push people to more self service.
Oracle has a good consumer portal that can be used as a website or typically is used in conjunction with a main website as a contact center or help center site. This allows the contact center to manage both the knowledge and the request and the interactions with the customers.
Oracle Service cloud is built to provide a turn key solution for CRM/Contact center with some minor configuration. But it also has the ability to be highly customized to meet any companies needs. Much of that work can be done via the configuration options already in the system. It also have a full set of SOAP and Rest APIs for integrating to other systems.
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.
This is only an occasional, user problem; when searching for specific records, at times we receive an error that the maximum size has been exceeded and therefore does not yield any results. This is particularly frustrating when trying to search for a specific street address across several years.
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
Although RightNow is extremely flexible, the flexibility comes with a price. It is often not intuitive which settings you need to change (and under which menus these setting are buried) to enable the system to do what you want. Also, sometimes the system can do things you need, but you don't initially realize it. When RightNow sells a system to a new customer, I think it should come with X hours of consulting time with a RightNow expert. The customer should be able to consult with this expert over the next year to get advice concerning how to configure the system to achieve desired needs. Often RightNow Support would just answer "no" when I asked if I could do something, but then I would find another way to achieve my goals after talking with other companies using RightNow.
The learning curve is fairly steep; but for something that has this much capability, it's nearly impossible to make it "easy". The layout and organization are at least reasonably intuitive. The hardest part-- the "weakest link"-- is the portal development (where you can build help centers and other end-user pages.) The capabilities there are significant, but the learning curve for that part is especially steep and it takes a fair amount of expertise to be able to update it.
We use a lot of tabs and fields on our incident workspace, which should slow the system down, but it's still quite fast, and we continue to optimize whatever is possible.
The vendor offers customer support to users who maybe stuck in usage of the platform in a number of options and this ensures that one does not get frustrated at all in using the platform. This enhances the trust held by the clients concerning Oracle CX Service [(formerly Oracle Service Cloud)].
Most of our training was given while doing user acceptance testing, and getting the system approved by the market. When ever we were in doubt, our implementer helped us along. Later on we started exploring by our selves.
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.
Work with a RightNow expert during the implementation. Explain features that would you like to have. Often, somebody who really knows the system can show you what you need to do to achieve the desired results. Where a RightNow support engineer or a consultant might say "the system can't do that," a RightNow application engineer will listen to what you need, and often come up with an alternate path to achieve it
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.
TCS' customers who also selected Oracle Service Cloud over Salesforce Service Cloud and GE's ServiceMax in the Mfg. vertical in which I work, did so because of the robust ability of Oracle Service Cloud and its APIs to integrate with other value-add solutions for manufacturers such as IoT applications, Big Data Analytics, and Field Service applications.
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.
We have an internal chargeback for servers and we anticipate that the cloud will save us some money or be cost neutral for us.
We plan to see a reduction in the need for data center staff and server provisioning as we move more environments to the cloud.
We are now responsible for our own destiny with the ability to ramp up and down our servers based on need. We can also monitor our costs more closely with the metered service and turn off the environments when we are not using them.
