Jira Service Management vs. Zendesk Chat

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

Zendesk Chat is suited for all the support teams that provide real-time assistance. Like if someone wants to block the debit/credit card, it is a high-priority case that needs real-time assistance. Whereas issues like close my account, and invoice request doesn't need real-time assistance, where Zendesk tickets support will be perfect.

• 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

• Extremely fluid chat interface allows for easy communication.
• It can be used directly on a website page or as a widget.
• Allows the end user to translate the chat into their own native language.
• Notifies you with pending chats via on-screen notifications and sound effects.

• 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

• Linking with a telephone, so the agent is only working on 1 channel at a time
• More simplified way to create and use templates
• Link users who may have provided us a new/different email from what we have on file for them

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

Due to staffing issues, we have temporarily stopped offering chat as an available channel. We're also interested in the best ways to integrate chat with our FAQs and AI to provide quick responses, either during off-hours or prior to speaking with a live agent. I've also found that reporting is rather limited where some of the interesting and useful data made available and visible during the chat cannot be pulled post-chat; it would be great to pull a high-level report so we can analyze this data.

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

As mentioned previously, it's a clunky product that lacks user-friendliness. It feels old and behind the times compared to other products we have used. The inability to have a wrap-up time before a new chat comes in is also a big issue for our team.

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.

Getting assistance and/or troubleshooting anything with Zendesk can be quite frustrating. In my years of experience with Zednesk, I have almost never found the answer to my question without going through multiple articles, ultimately getting frustrated and reaching out to our contact for more assistance. So for a consumer, the support is not as relieving as Zendesk Chat is to our customers in getting the questions answered by us.

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

Zendesk Chat is far more user friendly than some of the other competitors on the market. It has a very all the features that you require to ensure your customers are contacted in 'real time'. Its main tools include a live chat interface for quick communication, customisable chat widgets to fit your brand, mobile responsiveness for all devices, and canned responses for common questions. The platform can also start chats based on visitor actions, like time on a page or exit intent. A real must for any leading company

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

• Positive impact - Compared to our old system, this newly updated system provides features and functionality that has increased our agent productivity and provided customer insight like we've never had before. This has resulted in fewer hold times and higher customer satisfaction.
• Negative impact - Our reporting team still struggles with obtaining the right information from time to time with the chats. This leads to loss of productivity and more resources dedicated to reporting.
• Positive impact - Due to Zopim's embed, we are able to more successfully place them on the appropriate self-service portals and pages, reaching a larger audience, and being more readily available to answer our client's questions. This has resulted in an increase in our self-service portal usage, driving down the phone and email support channels, which in turn reduces support costs.

Incentivized