Jira Service Management vs. Microsoft Dynamics 365 Customer Service

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

With the constant changes included in the product, we can now use it for all the customer service scenarios / channels, for e.g. earlier for voice, we had to buy 3rd party CTI based tools, but now Voice Channel being available as the part of the product, that solves that thing. Also we see constantly new AI-driven features added to the product that could save lot of time of the agents while working on the cases like case summary, automate email generation, sentiment analysis etc.

• 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

• Dynamic CS allows you to access a wider customer base and gain artificial intelligence-powered insights into numerous client interaction activities.
• It assists in gaining deep insights into numerous data analyses performed on various customer interaction activities, as well as data visualization and customer satisfaction enhancement.
• This product has been extremely beneficial to my firm since it allows us to communicate with customers via a variety of channels, including e-mail and social media.
• Extensible, and Microsoft responds rapidly to market demand with new features. In terms of service, both Microsoft customer success and technical teams collaborate closely to ensure appropriate delivery.
• A better way to track client interactions is SaaS-based cloud services. This software may also be linked to outlook.

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

• It occasionally crashes or slow down, but it usually works great.
• Costly.

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

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

Microsoft Dynamics 365 Customer Service is generally very user-friendly, especially for those familiar with Microsoft products. The strength of Microsoft Dynamics 365 Customer Service is its integration with Outlook and Microsoft Office products like Word, Excel etc. and it user interface being similar to those products. This makes it easy for user to adopt to any new app.

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

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

• It has help us serve our customers better and get Support Contracts from them after we have designed / developed and deployed Microsoft Dynamics 365 Customer Service based solutions for them
• Ease of Routing it to appropriate customer support agent
• Because of multiple channel support we now give our customers option to raise a ticket or connect with their preferred communication medium, be it email, SMS, Chat etc.