Freshdesk Omni vs. Jira Service Management

For a typical technical support help desk use case Freshdesk Omni is great! It has the advanced features of automating responses and canned answers where appropriate. The AI functionality seems good but not something we are leveraging at this point given the volume of tickets.

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

• When an agent receives a call via Dialpad or Amazon Connect, Freshdesk Omni automatically displays relevant customer details, previous interactions, and ticket history in a single view.
• Every call (answered, missed, or voicemail) is automatically logged into Freshdesk as a ticket, including details like call duration, customer number, and agent notes.
• Agents can initiate outbound calls directly from Freshdesk using click-to-call functionality, reducing manual dialing errors and saving time.

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

• It is a very user-friendly tool. We haven't found any drwback in any of the modules provided. It works excellently at my organization.
• Its powerful workflow automation reduces manual effort for job assigning and makes our process more efficient and saves valuable time.

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

Utilizing a unified platform has successfully reduced the resolution time for customer-facing issues. This streamlined approach enhances efficiency and generates valuable insights that can be leveraged to improve our services and better understand customer needs, ultimately leading to a more satisfying experience for our clients.

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.

1) Price is also a point to decide, other Service Providers were providing similar features but the prices were slightly on a higher side. 2) Coming to feature comparison, JIRA offers whole lot of other features but currently we did not require them and Zoho had few less features comparing to Freshworks

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

• Our customers often give feedback to closed tickets to track satisfaction scores
• Customers appreciate the value of viewing their tickets in the customer portal
• We save time by having a single source system to interact with our customers and track issue history.

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