Dixa vs. Jira Service Management

Dixa may be a more cost-effective cash flow program than other programs used in our organization. Dixa does not require us to change our phone number when using the application because it is adaptable to our current number; the Dixa team handles the interface by quickly adding our phone number to their system. Despite the significant additions and updates to Dixa, our company is very pleased with the results obtained so far.

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

• The text recording of calls has made our life in the office easier since we often miss some requests, which with this feature we can attend to.
• The pre-recorded greeting is a good way to keep the customer waiting to be answered.
• The chatbot feature is perfect for customers with simpler problems to be solved.

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

• I wish it had the option of call transcription so that you don't just have access to the recording.
• We have had some problems when receiving calls, as they are forwarded instantly without allowing us to answer them.
• We have also had problems integrating with social networks, we have not yet been able to integrate them.

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

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.

Value proposition was by far and away the best. Any other system that had the features was much more expensive. The ease of programming made start up cost almost non existent. You have the ability to modify programming easily and do any special projects that invariable need to be accomplished by customer care.

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

• We must pay close attention to the regular updates that are released so that their implementation does not become difficult.
• You can be confident that you will achieve the desired results for your users thanks to the platform.

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