Jira Service Management vs. ProProfs Help Desk

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

As this tool is an affordable option, this help desk software is best suited for startups to deal with their customer base and build customer-centric brand value. This helps in not only helped me increase customer loyalty but also ensured customer retention, increasing my company’s profits substantially. But, this tool does have a few minor drawbacks. The most important feature, for me, that is missing from this tool is skill-based routing. Without this feature, our agents lose a lot of time in replying to just one customer question. Sometimes, the ticket needs to be reassigned to a specialized agent - and until they are available, the ticket remains open.

• Manageable workflow to ensure all users follow the same process.
• Can ban boards for easy visual of ticket status.
• Very flexible tool that can adapt to lots of different uses outside of the traditional service desk model.
• Added communication tools help you get out of e-mail jail.

Incentivized

• Sometimes customers ask questions that require more than one agent to look into the matter. For such situations, ProProfs Help Desk has the “child ticket” feature. This literally made my life so so easy! Whenever I was in this situation, all I had to do was create a child ticket and assign it to another agent and give him a heads up on what has been going on. Answering a customer’s question accurately becomes really easy with this feature.
• Our entire team’s performance was always static. We never knew how anyone was performing or was anyone making any difference in the overall company’s value. With this tool, it became easy to see how every agent is performing and whether there was any positive impact on both - the company and our current customer base.

• Ability to control the number of email notifications received (Note: this is a new feature in the Latest release but I personally haven not extensively looked at it and how well it solves the existing problem).
• No way to reply to multiple tickets at once, say you got 4 tickets in for the same issue, there is no way you can reply to them in one stroke. Other Ticketing systems do have this ability.
• Using a large number of add-ons to customize and add additional features adds up quickly and can become rather expensive.
• Request forms are very basic and there is no native dynamic field ability available.

Incentivized

• This tool does route tickets, but the one drawback is that the tickets are;t assigned to a specialized agent. It is randomly assigned to any available agent, and if he doesn’t have expertise in terms of the customer question, it becomes hard to give an accurate answer.
• Giving automatic responses to customers makes our life easy, but we can’t personalize these messages. This sometimes makes our customers feel that they are talking to a bot, making it difficult to answer their questions without them having a hostile reaction to the automated answers.

I gave JIRA a score of 9 since I am happy with the service it offers. I can easily see the SLA since it gives me visibility. I can pull up the reports I need. I can reach out to our clients using the PR ticket so it is hassle-free for me.

I have not used the technical support from Atlassian. In terms of online help and resources, they are a bit limited thus making it more of a challenge to troubleshoot issues and learn more functionality. There aren't a lot of resources available on the Atlassian site besides developer documents. It would be nice to have a blog or forum where users can get the help they need.

Incentivized

When I evaluated Spiceworks, it was not going to be replacing any ticketing systems. However, I did evaluate it and was not extremely impressed by the short demo I did. JIRA was selected because a branch of our company was already using it, so it made sense to consolidate into one service desk solution, and JIRA was the better option since it was less expensive and geared towards being a ticketing system.

Incentivized

I shifted from Kayako to ProProfs Help Desk for mainly two reasons, UI and features. ProProfs Help Desk definitely has a more user-friendly interface and the features offered by this tool are also more compared to Kayako. A few features that aren’t available in Kayako but are available in ProProfs Help Desk are multiple shared inboxes, private notes, and email ticketing.

• JIRA has been incredibly useful. Our work is more organized and easier to view by the team members as well as upper-level people.
• Our work is correctly assigned and when there are issues, they can be immediately addressed within the tool.
• Users can attach screenshots or files of issues that help clarify the ticket. Developers can attach relevant data as well.

Incentivized

• High customer retention.
• Optimized average response time.