HelpSpot vs. Jira Service Management

HelpSpot is well suited for streamlining support ticketing within the organization. By providing a single point of contact to email for support, we were able to increase response time and case resolution by approximately 30% through the increased efficiency of ticket routing via workflows and the ability for IT support staff to grab tickets from the queue instead of having them pile up in a mailbox that contains other emails as well.

Incentivized

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

• HelpSpot was great for organization. Having different queues allowed each of my team members to organize their conversations with the customer and quickly retrieve the history of the ticket.
• HelpSpot is a fairly simple tool that has a friendly user interface. With it's more modern look, it made it easier for me personally to navigate and train team members on how to use it successfully.
• HelpSpot allowed our team to view the responses section, which allowed our team to cut down on the time we spent responding to a ticket.

Incentivized

• 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

• The UI is a little dated but to be fair, shows most of the pertinent information at a glance on a well designed dashboard.
• The UI can also be buggy at times with controls appearing in strange places. These glitches are usually corrected within a reasonable amount of time.

• 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

My current job does not use this platform as it is not necessary for my job function.

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.

HelpSpot appears to be more of an old-school product but much of the recent technology is running under the surface. It has much of the compexity and customization available with Jira in tandem with the easy communications interface, not unlike Zendesk ,and some of the potential archival intelligence (in the works) of Fogbugz

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

• Improved ticket response time
• Workload reporting to upper management
• Ticket category reporting to identify training opportunities

Incentivized

• 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