atSpoke (discontinued) vs. Jira Service Management

Spoke is well suited to ingesting the myriad questions and requests I get throughout my workday. If I receive requests directly, they make it easy to change those requests into tickets, which helps my team track and demonstrate the work that we do. Spoke is also great for auto-answering common issues and questions. It only takes three of the same general question for it to start recognizing and offering the answer from our KB. Spoke has also been a great partner in helping our team be more efficient and more effective, something we never got with our old provider. I can’t emphasize enough that Spoke is NOT for external-facing helpdesks. It’s just not. It works best for teams that are supporting their own colleagues. I would also say that, at the moment, it doesn’t scale well past a few hundred users. They’re implementing features this year that will be more helpful for that sort of thing. But it does work great for remote support!

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

• Routes questions to the right team or person via Slack, email or text
• Obtain status updates on current job requests
• Allows IT to follow up more efficiently on the job requests from employees

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

• Newer company, a lot of features on the road map that aren't yet available.
• A few bugs with the Slack integration.
• Filtering/searching tickets is not intuitive.

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

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

Any questions we've had were fielded in a very timely manner and their staff have been very helpful in our launch and ongoing inquiries. Internally, it has been very well received amongst staff and has increased efficiency, company wide

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.

Spoke is just... easier. Easier to set up and easier to use, for both admins and users. We already have asset management and didn’t necessarily need our ticketing system to be directly connected to it. We wanted a product that was friendly to use, not crazy expensive, and didn’t require us to purchase an implementation package and/or a multi-day training package to roll-out. It’s not rocket science!

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

• Spoke has been very cost efficient, more than paying for itself in gained productivity hours.

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