Fin by Intercom vs. Jira Service Management

Fin is great for using for first line support. We use Fin for conversations where customers have a standard question, and Fin is able to pull from our content to answer this accurately and go above and beyond to include some basic problem solving. This really helps us free up our Support Team's time for more complex queries. Fin isn't appropriate for us on technical issues or conversations which require human support. We've had to remove Fin from interacting on these conversations as customers were becoming frustrated with speaking to AI, or having Fin be unable to problem solve. However, this was easy to set up through Intercom, and now customers with complex questions/situations or bugs/technical issues do not engage with Fin and Fin only handles suitable conversations.

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

• Serves as the first point of interaction.
• Answers questions based on the knowledge base.
• Tries to suggest a solution for reported issues (in some cases).
• Gives the option to improve its answer.
• Learns from other conversations and replies by humans.
• Understands other languages.
• Interprets images (somewhat).

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 seems some users really struggle to figure out how to escalate to a human (especially through email).
• Not excited about how "soft" resolutions still count as resolutions and are paid for. Though some abandoned cases appear to be able to be concluded as "the user got the answer they needed", there are others where they clearly didn't, because they just open up another chat (or even more), trying to get more info. This pads the resolution stats and makes it seem more effective than it actually is.
• Cost -- Fin is quite expensive. It helps us with scaling coverage, but we're not really saving money.

• 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 have been and will be continuing our journey with Intercom and nothing too concerning has happened that I have experienced or heard of that has us on the edge yet. If it ever happens it will be something along the lines of "Outgrowing" the use of need of the platform.

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

From an administration standpoint, Fin is very easy to set up, train, and test. Having the ability to impersonate a user in our system to see how Fin responds is huge. It lets you test several situations and throw curveballs at it (as customers will) without the risk of setting Fin live and wondering what will happen. It's also easy to fine-tune. Some chatbots you can never quite get right without spending hours on, but Fin usually takes a few minutes to dial it in. From a customer standpoint, Fin couldn't be easier to engage with. We tell customers up front it's an AI bot and they're wow'd with the experience

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

always there

Incentivized

works perfect

Incentivized

Intercom is the premier customer support/engagement model and it definitely has one of the top tier customer support teams as well. I don't think I have ever waited more than 5 minutes to get the information I need or get help with an issue. They are incredible and I aim to model our customer service department after them.

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.

Easy to know the learning path

Incentivized

The implementation was surprisingly easy but we are having to adapt from our old process to work well with Intercom.

Incentivized

We only used the free live chat version from HubSpot, so Intercom is yards better! If I were just comparing an actual live chat between the two tools, HubSpot was often clunky and delayed, and it was hard to find past conversation information

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

• New role opportunities — Using the “Fin-first” approach has reduced the workload for our Tier 1 team, giving them more time to focus on their own career growth. It’s also opened the door to a dedicated, AI-focused role, where a team member regularly reviews Fin’s answers and makes updates to help it perform even better.
• Enabling Fin has also reduced our response time and allowed us to meet SLA's.

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