Kayako vs Spiceworks Help Desk

• 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.
• Nice dashboard view.

Read full review

• It helps to multitask, even on the go with the mobile App.
• We can customize to meet your needs with automated responses, notifications, and templates.
• Detailed reports allow managers to keep track [of] and analyze data.
• Allows for a database to store notes helpful for future tickets.

Read full review

• 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.

Read full review

• I have always wanted a way to redirect a support request into another IS bin, such as a development task.
• It's possible to extract the data from the Spiceworks database, but it would be helpful if the process to do so were easier.
• Improved ability to customize the system generated emails to improve the formatting and company branding.

Read full review

• 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.

Read full review

• Positive - Allow organizations to implement structured Help Desk procedures.
• Positive - IT can begin to quantify their tickets and uncover needs within the organization.
• Positive - IT can develop a solid roadmap with [the] management of future needs, equipment refresh schedules, etc.
• Positive - IT can pinpoint employees who may need extra training or updated equipment based on historical ticketing data.

Read full review