Jira Service Management vs. Kustomer

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

I would say the greatest strength of Kustomer is its flexibility. In the hands of a skilled admin, it can be adapted to tons and tons of different use cases. I've been able to make custom displays for different groups of agents, produce complex cross sections of users, draw interesting data relationships combining marketing contacts and customer-initiated contacts. For example, there's really no other data source in our company which could tell you which users received a specific promo code and checked out with it, received their delivery within 14 days and then can related that to the number of times they contacted us about using our product. At the intersection of communication, marketing, data, and relationship-management, Kustomer shines at the center. I would say it falls short when you are trying to coordinate multiple "side conversations" with multiple sources to resolve an issue. This is a tough task for any type of platform, but if you're maintaining 3 different email chains with a 3PL partner, the customer, and a separate internal conversation, it would be confusing anyway!

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

• All customer data (past orders, communication with customer service, rewards account data) is in one place. This helps agents avoid confusion and reduces the number of tabs they need to open.
• The Knowledge Base (or K Base) is very helpful. Any time we roll out a new policy or have a limited-time promotion, we can add all the relevant information and worksheets there for the convenience of the agents. That way they can stay in a chat while looking up the answer to a question.
• We can seamlessly move from chat into email if the customer leaves or the queue times are too long. All the interactions will stay on the customer profile page, so they are kept up to date.

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

• For our team, the feature that defaults all notes to begin in "done" status is difficult. Throughout each day we need to have notes open and assigned back and forth to different teams, and we have to remember to manually "open" each note. There is too much room for human error with this setting, and it is easy for important notes to be missed if a user forgets to open the note.
• Similarly, it can be hard to remember to assign emails/notes to a particular team in addition to a user. We almost exclusively work out of team inboxes, and if someone on Care writes an email to a customer, the email will automatically be "done" when it is created, and it will be assigned to the user who wrote it, but not also to the user's team. There are instances where an email needs to be snoozed for several days/hours with further action needed, and unless the user remembers to assign the email to their team it may "awake" from the snooze and not be visible to anyone except the user who created it. Similarly to my first comment, this leaves a lot of room for human error and is not very intuitive.
• Personally, I do not love that all tickets/emails/notes are jumbled together in the same inbox. While this gives visibility to everything on the "to do" list at the same time, it can be visually overwhelming. We have created unique folders for certain types of projects or categories of work, but have experienced tech glitches or just the awkwardness of another step to manually read the note, determine what type of category it is, and then manually assign it to another folder. Would love to have things auto-sort and take out this manual lift.
• I love the idea of the autopilot setting, but we have not been able to use this for our work because it sorts items based on time, and not based on priority. In our line of work, we may have an urgent situation arise that needs attention before an email that was sent in 60 minutes ago. The autopilot feature would push the email to my associates sooner than it would the urgent situation from 5 minutes ago. Due to this, we manually monitor inboxes and assign work to ourselves and others.

Incentivized

Because there's no other tool like Kustomer

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

There is a learning curve, but it is more than worth it, especially to have a dedicated resource pointed at Kustomer and any other software it interacts with. The basic implementation is useful, and powerful - certainly a MASSIVE upgrade over taking care of your customers in an email inbox or shuffling between multiple windows and applications! It is also set up really well to grow and reconfigure with your business. I'm a big fan.

Incentivized

Because Kustomer is available when you need it

Incentivized

Because ages load quickly, reports complete in a reasonable time frame, given their complexity

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.

I did not reach out to Kustomer support when we had an issue. Still, whenever we provide feedback to our manager regarding what can improve based on our experience using Kustomer, our manager always comments that Kustomer support always replies with some positive feedback based on our suggestions.

Incentivized

Because they are very hands-on in training us and very approachable

Incentivized

It was very easy to understand.

Incentivized

Nothing really because it is easy to use. After an hour of using it, we're already getting the hang of it.

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

Apps like Intercom, Zendesk, and Gorgios all treat customer inquiries as tickets, just tracking that one issue or interaction with a customer. Kustomer treats each customer as an individual, which allows us to provide top-notch customer service. Customers love that we're able to be more conversational and informal, while still solving their issues quickly. It also helps us build relationships with customers and increases repeat orders.

Incentivized

Because customer is flexible and scalable

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

• We’re getting so much positive feedback — which is not something you traditionally associate with a customer care team — because we’re making it effortless for customers to deliver both positive and negative feedback, and we can now resolve the bad feedback really really quickly.
• Primarily from our increased efficiency with Kustomer, we’ve seen a significant reduction of $3 to $4 for every cost per contact.

Incentivized