ChatBot vs. Jira Service Management

Most suited: Frequent duties can be automated. services can be improved by analyzing customer feedback. Load and Heavy tasks can be reduced. Less workforce is required. Less Suited: Specific product queries and their proper answers. When the user uses those words that are misspelled or have a long sentence it finds difficulty in giving them proper information.

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

• Routing rules
• no code workflows
• UI/UX is excellent for a newbie to start on
• Their Chat support is very helpful

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

• Having enough conversational data to train the chatbot.
• Really understanding intent.
• Understanding emotion.

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

As long as budget is not an issue - we renewing this solution.

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

Since I deployed this solution end to end for my organisation, I would speak from my experience that since I was a newbie to this platform I took ample support from their team, their training resources. However, the product's UI/UX was simply very intuitive that it helped me to get a lot of hand-on practice on the product well. This helped me with the timely deployment of this solution.

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

Full end-to-end support is critical to maintain the ongoing service, robustness, training and customer service Chatbot offers.

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.

ChatBot is more stable and enhanced as compared to other rivals which are new in this segment and also provides a lot of details which is missing in other products like report etc. Also, chatBot is more commonly used so support wise it is also great and you can find multiple examples on the internet and from your peers as well.

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

• Connecting to DB.
• Customizable dashboards.
• Automated reporting.

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