Agiloft Service Desk (discontinued) vs. Jira Service Management

Agiloft is most suited to meeting the needs of an organization that requires rapid and frequent process changes for critical processes, and values empowering the people who do the job to determine how best to automate it - essentially rapidly growing, democratic organization.It's hard to imagine an inappropriate scenario to use Agiloft, but one that comes to mind is organzations requiring a complete, finished, highly structured solution that they do not want to change over time. Agiloft is designed with the expectation that clients will adapt it to their needs so many functions are left undone, rather than throwing a "kitchen sink" at the customer and letting them choose what they need.The best way to work with Agiloft is to take the training class, then have a small success with a small team, involving the employees and first level management in the deployment. They'll tell everyone else how much they like it. This reduces the possibility of slow development cycles and an undue dependence on outside expertise, while maximizing the return on Agiloft's investment in easy customizability.

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

• Fully GUI based interface that has drastically reduced the time to add new features/workflows.
• The product was very easy to deploy and add features like Single-Sign On and user provisioning from our internal DataWarehouse. Again, vendor support was a big help while implementing those features.
• The workflows include a very comprehensive rule-based system that can trigger various actions like escalations, emails, changes of request state and more. All without any coding. Again, fully GUI based.

• 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

• With flexibility comes complexity, so we have needed to use consulting time to implement some of our needs. The learning curve can be steep, but the product can accommodate nearly any scenario.
• At one point we seemed to have some performance issues, but those seem to be in the past.
• The text messaging integration would be nice.

• 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

We're comfortable and happy with our purchase of Agiloft. Our end users have been happy with the tool, and appreciate the time savings and efficiency it has gave them. Agiloft also appears to actually care about you being a customer, which makes a difference to me.

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

For the most part, it is an easy and intuitive system to use. There are many small things that could be improved to make the system work even easier. However, overall it is very easy to use if you have a good grasp on computer programs and using them to build things. I do not have any computer science or programming background, and I am able to use this system with few problems.

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

We often hear back very quickly with answers to our questions. They also support their answers at times with screenshots and videos to help further explain their advice and suggestions. The only reason it isn't a 10 is because sometimes using only the online support system, sometimes things aren't communicated as well as they would be over the phone. However, we know if there is a major issue going on, we can call Agiloft for support.

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.

Most of the other CRM software packages we evaluated were either too complicated or time
consuming to setup and customize, or they were too expensive, especially since many
of the companies charge additional fees for each additional module or function
you want to use.

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

• Helps us organize tasks and projects and the data associated with each project
• Helps us organize our resources to meet the demand of issues and events
• This has helped us keep moving forward during times we otherwise would have pulled back.
• Completely revolutionized our way of work life. Upwards of approx 300 percent productivity and complexity..

• 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