Helpjuice vs. Jira Service Management

Helpjuice is an excellent platform when you’re looking to modernize the way you create documentation. Many companies, especially larger corporations, are stuck in the past, utilizing PDFs and share drives to house and access procedures. With Helpjuice, we now have a centralized web-based platform that provides everything from analytic functions to standard templates, user-specific features, and more. My team specifically chose Helpjuice during the pandemic, when all the tech writers from my company (including myself) were moved into a single team. We needed to find a platform that would allow us to align our publishing standards while also moving us forward in the way we publish procedures. That platform was ultimately Helpjuice. Helpjuice certainly offers a variety of features, but one of the few drawbacks is that it does not incorporate or seem to integrate with any specific ticketing tool. While this isn’t an issue for me or my team, as we are required to use a specific tool internally, I can imagine that someone looking for a complete package with multi-step workflows and an intake process would not find Helpjuice adequate.

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

• We were looking for a publishing feature where there would be some required oversight.
• We have really enjoyed the AI Tool of Wizardshot as it has helped reduce the time spent writing articles.
• The analytic dashboard to see who has contributed what and which articles are the most clicked on is wonderful

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

• Article feedback disappears when resolved, would like to see a integration with Jira which we now use to track feedback changes.
• Analytics for the AI search would be appreciated. Currently we have no idea how many people are actually using this feature.
• A way to train the AI search bot. Currently there is no way to up/down vote answers or indicate how accurate or helpful an answer is.

Incentivized

• 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

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

HelpJuice is really amazing as a starter knowledge base vendor. They have great customer service and the ability to customize your website is endless. However, it is difficult to scale up.

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.

Prior to using Helpjuice, I was using Microsoft Publisher to create all the training materials and manuals for multiple divisions within my company. It was awful. It would lag whenever I opened larger manuals, it operated like software from the late 90s, it was not intuitive, from a design perspective, and after migrating to a MacBook Pro as my work computer, I discovered that the program was NEVER created for Mac OS, requiring me to run Windows on my MacBook whenever I had to update any procedures that hadn’t yet migrated to Helpjuice. What a nightmare.

Incentivized

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

• As I mentioned, my productivity in terms of working around issues, asking for help, etc. is greatly reduced on a DAILY basis.
• I spend as much time finding bugs and filing tickets as I do writing content, and this was especially true at the beginning.
• The Doc Center looks nice, so you'd never know the pain behind it.

• 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