HappyFox Help Desk vs. Jira Service Management

The biggest factor in my selection of this product was how our techs wanted to use a Help Desk. Everyone was already accustomed to email because that's how everything was done in the past. More than that, people often responded to inquiries on their phones via email. I needed a help desk software that could be used almost entirely by email. After demoing HappyFox, I knew I had found what I was looking for. Tickets, based on what department they are for, arrive in the appropriate tech's inbox. Techs can respond and HappyFox will forward their reply to the customer. All conversations are logged on the site so that they can be reviewed later, by us or the customer. With Smart Rules we could begin to get creative and open up even more options to allowing our techs to work solely through email. For example our managers have the ability to assign tickets to employees purely through email based on the text they enter. We also have the ability to respond to an email and close it. This speeds up resolution times by allowing everything to be handled through email. For everything else the web interface is a breeze to use

Great to manage your issues in a clear and centralised way. If your development teams work with Jira, it will all naturally come together. Great way to manage the issues from end to end. - Very flexible if you have people who understands the set up and is able to configure it for your needs - Maybe not the best if you want something with very easy set up

• HappyFox is restricted in what it can offer (particularly the free version,) yet it functions exceptionally well as a support ticketing framework.
• Clients have an portal to submit tickets, mind progress, and react to support assistant's updates or plans.
• Administrators can track tickets, see what's left open, and set up plans that ensure tickets are not overlooked and are given the best possible priority to get dealt with.

Incentivized

• Highly configurable Notification Scheme, allowing free customization on who receives notifications and when
• Ability to add extra features through the highly diverse Atlassian Marketplace.
• Simple and highly customizable ticket interface. The Software can be almost completely branded in every aspect to represent your organization.
• Integration with Jira Software allows support tickets to be moved into other Log Term projects as necessary.

Incentivized

• Their interface is a bit busy and overwhelming sometimes.
• Still getting notified on too many tickets I haven't even looked at, despite our in-house specialist assuring me I don't have any incorrect alerts set up. Seems HappyFox Help Desk is working on this.

Incentivized

• Some of the built-in functions and workflows are surprisingly limited given the fact that you can customize a lot with JQL. These limited areas do not allow you to use JQL. For instance, the built-in notifications are lacking. They have one that is great-- "notify on critical ticket creation"-- EXCEPT that it does not allow you to notify a group or anything, only individual users.
• The ticket interface is a little odd for agents. Changing the status is not a simple drop down from unassigned to open to in progress to pending, etc. There are a couple of tabs ("investigate", "pending", "workflow") where you can change the status in different ways. Maybe I am just not used to this way of doing it, but I feel like it could be simplified.
• It can get complicated deleting/changing some of the out-of-the-box fields and rules, because you never know what will break workflows or other automated/built-in features.

Incentivized

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

I have given this rating because, in my opinion, I don't see any downsides of Jira until now. We can customise workflows based on the project needs, including task workflows. Jira is very extensible, which is one of its most important features.

Incentivized

I gave JIRA a 9 rating since for me JIRA works according to its purpose. Since there is a customer portal, our clients can leave a comment or communicate with us using the PR ticket that way it is easier for us to also request any additional information we need for our investigation.

Mojo was an okay ticket system but it was difficult to track. You also couldn’t consolidate between messages very well, which would leave you with long threads to deal with and waste time. With Mojo, it suited our needs for a time but as the company grew, it became clear we needed a more robust ticket system to work efficiently.

Incentivized

We chose Jira Service Management due to its easy integrations with the rest of the Atlassian tools, as we have also invested in those. For the price, the ability to add or remove agents, and the cost being reflected in that, it was an excellent medium for us. For the foreseeable future, I do not see us moving off this platform.

Incentivized

• Through Email support, the company conducts a marketing plan, through sharing of catalogs.
• Survey and feedback are conducted and attained from HappyFox.
• HappyFox supports live chat, an easy way to perfect the satisfaction of clients.

Incentivized

• It has allowed us to take on a larger volume of work at a faster pace.
• We have established best practices with the tool that we have taught and sold to clients.
• It has allowed for further collaboration with a larger team.

Incentivized