HubSpot Service Hub vs. Jira Service Management

I'd recommend HubSpot Service Hub for sure. When switching from a different platform to HubSpot Service Hub orgs and admins can count with a vast number of trainings in HubSpot Academy and most of them are free. This means users will find the resources they need without needing to reach for their superiors for training sessions or guidance.

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

• It makes it easier for us to keep track of customer awareness and review in one spot.
• The great thing about how easy it is to use all of its fantastic tools.
• The ability to check customer retention.
• It's easy to track and measure the success of our organization's sales team.
• This is a fantastic all-in-one customer success suite that includes ticketing.

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

• We've had some issues setting up the Client Portal functionality because we merged with another company and are still operating under two domains; Setting up the Client Portal could be easier or they could provide better support to help us work through it
• We've been able to do everything we need to do with HubSpot Service Hub

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

I'd give it a 9 or 10 for the survey functionality because that is what we use regularly. I left it at an eight because we don't yet have experience with some of the other functionalities within the ServiceHub. Based on our demos, the ticketing system and the ChatBot are great, and we look forward to adding them soon.

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.

HubSpot [Service Hub] had many integrations we needed to connect to our CRM, and the cost was just right from them VS the others. We had to look at all the features, and HubSpot CRM just had way more than the others and more bang for your buck. So the Service Hub was just a bonus with their CRM tools.

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

• Easy to keep track of leads and track their journey into becoming a customer. For example, we can tell which leads open what emails and target people differently to help increase sales.
• Even though HubSpot Service Hub is very expensive, I do think it is worth the price because we can keep track of all leads/ customers very easy, track the customer journey, rework emails with AI, etc.
• HubSpot Service Hub also has reporting so you can track everything which helps to improve our sales

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