Gorgias vs. Jira Service Management

Gorgias is one of the easiest platforms I've used, as it was easy to navigate. You can customize your views so you can easily track them. The shared views are also specific and convenient. The search button is also one thing I like, as it easily shows what you're looking for with just keywords, email addresses, or any information.

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

• Tagging- the tagging system was a great way to stay organized.
• Rules- when you have 49 inboxes implementing rules on when to fire a macro or auto tag is necessary and Gorgias’ UI was easy to understand and execute.
• Integrations- I had to integrate with dozens of inboxes many times using aliases and most of the time Gorgias was able to help.

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

• Rules are powerful, but clunky, showing them to others can put them off as it looks "easy to break" because of their messy nature.
• Pricing seems to be increasing due to the inclusion of more advanced AI that currently does not provide value.
• Macros could really use contextual support, or a hotkey system to make it easier to pick highly used ones that aren't in the top 3.

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

Gorgias is still by far most the most complete customer service tool to handle multiple responses and channels at a single umbrella without the needs of opening multiple tabs and sometimes will even make us missed some messages what supposed to be taken care of at a timely manner

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.

We selected Gorgias from Zendesk based on its Shopify integration. Given how many stores we were managing the team needed to quickly find all of a customer's information in an email. We preferred it to Zendesk. However, now that I use intercom I have many more features such as surveys, topics, extensive reporting, auto tags, and series I prefer intercom for my work now

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

• Drastically reduced our response time from 2 business days, to 2 hours on average.
• Made it easier to sync data for damaged item, allowing us to better understand damages.
• Allowed us to easily see that statistics of what kind of issues we are seeing from our customers.

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