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
SAP Service Cloud
Score 8.7 out of 10
N/A
SAP Service Cloud helps deliver customer value and protect the brand with intelligent customer service. It enables the user to engage with customers at their convenience, connect service with the value chain and deliver greater profitability.
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.
It is well suited for Analytics, Customer Relationship Efficiency Engagement, and best suited to help decrease Infrastructure maintenance costs for Organizations. Learning for new bees is a little difficult to grasp with the features/functionalities. The Software is a little complex from the setup and configuration point of view. Reporting capability can be improved as it is a highly effective CRM.
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.
SAP Service Cloud pulls together messages from different channels - emails, calls, social sites - into one dashboard. This means we can quickly see and respond to any customer question or concern without jumping between different tools.
It streamlines our workload by automatically categorizing and prioritizing customer issues. This ensures that urgent banking matters are addressed immediately and no query is left unanswered.
The built-in knowledge base is a lifesaver. When a customer has a common question or issue, we can quickly reference or direct them to pre-existing solutions, speeding up the resolution process.
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.
Integrating SAP Service Cloud with non-SAP systems can be challenging, i faced some hurdles when my IT team took 3 months to integrate the billing data from some other vendor and the system would run slow if you try to pull billing data
Slow loading of the pages as compared to other consumer tech softwares we use
Implementation costs and complexity of implementation makes it an option only for large enterprises with huge IT teams (and it can take a few months to implement)
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
I have found that sometimes issues reported to the SAP takes more time also they lack system support with respect to the priority . Also we don't see RCA for the issues raised. Also turn around time for the issues is not fixed as the support is global sometimes the issues float here and there.
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 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 went with SAP Service Cloud instead of Oracle Cloud Platform because it is like a custom-made tool for big companies, seamlessly working with our other systems. It helps us manage complex tasks and customer interactions better, making everything smoother and more efficient. It just fits well with how we do things.
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.
positive impact: Enhanced Productivity: The platform's automation and knowledge management capabilities can boost agent productivity. Agents can handle more cases in less time, leading to cost savings and potentially higher revenue through increased sales opportunities.
negative impact: Complexity: If not properly configured or if it doesn't align with an organization's specific needs, SAP Service Cloud's complexity can hinder user adoption, leading to inefficiencies and potentially negative ROI.
