HappyFox is a web based customer support ticketing system hosted in the cloud. It helps track and manage all customer support requests across multiple channels like email, chats, social media and phone in a centralized ticket support system. It provides integration with other web apps like CRM, live-chats, voice and bug tracking apps. Community forums feature help customers help each other and connect. Mobile versions of Happyfox provide support on the move.
$29
per user/per month
ServiceNow IT Service Management
Score 8.5 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.
Happy Fox works well in companies that want a full look at all of their tickets in one place. It may be better suited to smaller companies who can check or double check their tickets and have the time to spare. For bigger companies, I think there are better, more robust solutions.
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.
Smart Rules - Easily create triggers that run based on a variety of criteria. This allows for easily moving tickets through our process. An awesome example is our manager's ability to assign tickets to technicians right from their email simply by responding to the ticket in a certain way. This prevents the opening of a web browser or the mobile app to complete basic functions. Removing one step from the process has already saved us countless hours.
Easy to use and clean interfaces all around. Whether it's the web interface, mobile web interface, or one of the mobile apps, HappyFox is all around intuitive. Plenty of things can be made to be updated in two or fewer clicks (Assigned to, due date, priority).
HappyFox allows our users to easily create tickets on behalf of customers. Any person who has previously contacted the Help Desk is stored as a contact and can be referenced again quickly.
While the portal they provide is basic, it can be quite heavily customized with color schemes and logos. Ours ended up looking better than almost anything else we host both internally and externally. It's clean, simple and provides an easy way for users to input a ticket.
Between the Smart Rules and SLAs it's easy to make sure every ticket gets the attention it deserves. Automatic reminders can be sent to technicians based on criteria. Reports can be run to ensure that service levels are being met. These two things alone have greatly increased the quality of service.
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.
There are a few features that I would hope to be standard that are not yet accessible. For instance, having different time zones isn't a choice, and clients aren't able to create their own reports, only staff can. So, my staff is required to run those reports for our clients.
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!
The way we have our implementation customized has allowed us to tailor the application to exactly how we would like to use it. We didn't have to change our procedures and fear the potential of poor adoption. Instead we customized the application to be used the way we already ran our help desk. From there on out we reaped the benefits of quicker resolutions, increased transparency, and much happier end users. After setting up Smart Rules, HappyFox does a lot of thinking for us. Tickets go where they need to go, close when they are supposed to close and even remind techs of inactivity. This removes the necessity for micromanagement, which is appreciated by our employees and managers alike
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.
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.
HappyFox delivered a more cost effective solution and asset management had no limit. The main problem I saw with the various other services I demoed, was the up charges. The pricing seems manageable until you see that they charge for every 100 or so of this and 100 of that. HappyFox is truly a one-stop shop for us.
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.
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.
