Jira Service Management vs. TeamSupport

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

TeamSupport is a great ticketing/help desk platform for small companies. It gets the job done and allows for multiple teams to manage workloads. It is not best for bigger organizations as there are lots of lacking features (mobile app, integrations, robust Jira/Confluence like system). The support for TeamSupport is great too. They usually get in touch with customers quickly when the system is down and they resolve issues quickly as well.

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

• There were other customer support software companies that I looked into at first, however TeamSupport provided exceptional customer service themselves. I paid close attention to how they handled me as a customer to see if they were a company that would understand my desire to give exceptional customer service to my clients and if they had the tools to make the experience easy. Every interaction with them was very positive.
• Since we needed TeamSupport's software embedded into our software application to give our users easy access to the support tools, the staff at TeamSupport needed to answer many questions and work with our developers to make this possible. They were always willing to take the extra step to ensure a smooth set up.
• As we continue with TeamSupport, I am especially impressed with the sincerity of the CEO, Robert C. Johnson, and his commitment to us so that together we can deliver exceptional customer support.

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

• We would like to see a structure to the ticket numbering system. In a previous system we had a numbering system like this mmddyy-xxxxxx This was very easy to see when a ticket was created based on just it's number. Currently with TeamSupport they assign a random number to tickets that is not very informative without a created date field.
• Reports are nice but lack some rollup capabilities that are needed. Any given report can only work against two data tables at max. This is a limitation that we had to create custom contact fields to get around. They store phone, address and base contact info in separate tables. This makes it impossible with a standard system to create a report of all tickets along with the ticket and contact information in one report. The previous system we were on, allowed you to tie as many related data tables together that was needed to create one high level report.
• Need Ability to notify external users of ticket activity in regions. So what I mean is we have FAE's in the field that want to know what their customers are asking for their region. They don't want or need a TeamSupport account but want simple e-mails of activity. This has been a lost feature for us going to a new system. I have to create a manual report each week and forward to the people that want this kind of information.
• Ticket Automation rules will only run against a ticket one time. I understand why they did this to prevent uncontrolled loops but it would be nice to be able to set a limit that was greater than one. This limitation often causes us to have to write multiple rules to handle certain ticket cases.

Incentivized

We are very likely to renew. We have been using TeamSupport for years and have tested a few other ticketing software solutions. We utilize several project management solutions to date and are always looking for better more efficient ways. Team Support is great at working with us and allows us to report issues well.

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 think some things could be a little more user-friendly: specifically the dashboard. Although it's fantastic and makes life so much nicer, I'd like to have more control on it's customization. I'd like to be able to default what's collapsed and what's expanded...instead of everything expanding by default each time I load it. But the portal offers great tools and guides on workarounds.

Again while most of the time I CAN access your server, it's offline enough that I can't count on having the software available to me 24/7

It is a feature heavy web application, thus speed can be compromised sometimes dependent on availability of a quality internet connection

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.

TeamSupport's ease of use and the way it benefited our company overall. From cost improvements, ROI, and overall management of team members it gets high marks. We are better able to support our customer base by providing improved support in a more timely fashion. The End User view of IT Support overall has improved just through using this platform in our company.

Incentivized

Able to get hands on training and ask questions.

Not much training was offered, but it was always provided when we requested it

Data import was the most difficult hurdle for us to get over. The mass import was handled through an Excel spreadsheet. TeamSupport doesn't use Microsoft Office products for the most part so they were relying on Google Docs which has limitations over Excel. Special characters and html in import cells can be a issue with importing. When creating a data export from your current system, special care needs to be taken so that the data is able to be processed into TeamSupport without issues.

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

TeamSupport is a much more modern, intuitive and user-friendly version of NetSuite with many additional bells and whistles. NetSuite has a business only facade with a rather clunky interface and system. TeamSupport compares favorably and meets business needs while being a much more advanced and modern solution.

Incentivized

TS keeps adding new features without making sure the program is reliable as-is. The program is frequently offline which makes for significant frustration on my part

• 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

• TeamSupport has improved our team's response times. We are able to address all requests within a short time of receiving them.
• TeamSupport allows us to effectively manage workflow.
• The program provides us with a certain level of accountability, and requires that we be meticulous in our work.

Incentivized