Jira Service Management vs. ProProfs Help Desk

I think using a ticketing system is very easy to use and allows multiple teams to create help desks in the same portal. In terms of internal usage, I think this is a great option. However, suppose you're trying to keep internal items and external helpdesks in the same instance. In that case, this is not ideal, as there is no effective way to separate the two instances to protect internal data better.

Incentivized

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.

• Integration with many of the most common tools companies are using (Slack, MS Teams, Salesforce, ... etc)
• Natural workflow with Jira (as product development / project management tool) which makes the full fix and follow up of the tickets / issues very easy to follow
• Allow multiple different entry points and work flows for as many different needs your teams / company have

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

• Navigating through issues outside of a kan ban board can be confusing and task heavy.
• It's easy to clutter up the tool. It could use some easy clean up capabilities.
• User interface is decent, but could use work to make it more intuitive.

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.

In the current contect the requirments is around having a tool that is focused and can handle large ticket volumes and tracking incident, problem and user requests concerning end users. Jira has built in functionality to address the above practice needs faily easily and has a substantial amount of customizable reports for generating the relevant intelligence.

Incentivized

If you're used to other tools in the Atlassian ecosystem, you'll feel right at home with JSM. It's also a platform that technical folk can easily pick up. However, I wouldn't recommend using JSM as a company's first jumping off point into Atlassian. There are a lot of other 'newer' tools that provide sleeker ITSM systems at a similar cost.

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.

Zendesk is a similar ticketing system that our organization used before JIRA Service Desk. The main drawback of Zendesk was that it can only be used as a cloud service. This means that our company data would be living on the internet at the hands of their security team. Another drawback of this is the price is significantly more expensive rather than hosting it yourself. Zendesk does have some additional features such as commenting on multiple tickets at once that JSD does lack. However, switching to JSD was significantly more cost effective because we have the ability and the infrastructure to host our own ticketing system, something that Zendesk could not provide. Ultimatley switching to JSD saved us money and allows the ability for integration with all of the other Atlassian Suite products that we use on a day to day basis.

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.

• It is definitely cheaper than Salesforce
• It allows the IT service desk to be more organized and respond more quickly to tickets, which can save time for both agent and requester.
• Some things are "not quite there" developmentally, so this means that internal IT will need to spend more time developing and testing the product.

Incentivized

• High customer retention.
• Optimized average response time.