Jira Service Management vs. Groove by OptimizeCX

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

Groove is great for people who are wanting to provide accountability and organization for teams across your business. It is suited well for an organization that has many email requests coming in every day, because you can assign tickets to specific team members. It would not be suited for an organization that utilizes more phone support, than email support

• 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

• Creates Tickets when someone emails in or you can create a ticket within the groove system.
• They have great reports on response times and the average amount of time it took for a ticket to close. You can even see individuals average response times as well as specific teams.
• We use their Knowledge Base which is a great tool for creating FAQ and sending people to that.

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

• Better Follow-up by customer success team
• More customization within their major features to fit both, large and small sales teams, alike
• Their site goes down fairly often

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

It's well organized, but slow.

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.

I'm giving them a 3 for the really great support they gave for general questions. They also have a good knowledge base. I'm giving them only a 3 though because of my last customer service when I need a billing resolution. I was very disappointed in how they handled that. I also find it very bad practice to send out ONE email notice that they were raising my rate three times as much at the end of the month. When I was with Desk.com, I had numerous emails over months letting me know their billing plans were changing. Even worse than refusing to refund me the difference was that they just stopped responding to me.

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 also use Trello for project management. I have used both systems and we like Groove because it allows for our clients to contact us via email. They do not have to go to a ticket submission page, they can just email us directly and it will create a ticket. Groove also provides analytics on how long it takes to respond to tickets

• 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

• We wasted a lot of time setting up the product before we discovered a lot of features listed on the website aren't ready for public use