TeamSupport

Pros

Team support makes it easy for my team to focus on the customers as against just focusing on tickets. With support tools ,we have tried in the past ; we were able to resolve customer tickets , but found it difficult resolving all of them at once.
Team support provides the customer care team with high level visibility , which enable our sales team to manage and resolve customer tickets at a company level as against resolving them at a ticket level.This eliminates duplicate efforts where we have multiple support agents helping out a single customer to resolve multiple tickets at same time.Thus ensuring we are able to resolve all customer issues at once, as against on a ticket by ticket basis.
Overall, Teamsupport has saved us time ,and made our customers happier.

Cons

It is not intuitive even though it is very effective. Also will like to see more information with new tickets opened by customers. For example ,will be helpful if agents can see from what geographical location the ticket was created from, or from what part of the website the ticket was created from.

Pros

I primarily use Team Support for Inventory Management.

I like that I am able to search a terminal based on the serial number alone.

It is helpful to leave a note for each terminal, I use the notes to indicate the current status of a terminal, whether it is ready to be loaned out or if it already been loaned etc. Team Support has a provision to assign an inventory item to a Customer. I find that very helpful.

I like the feature where I am able to schedule the reports to be emailed to more than one email address. These reports need to be sent at particular time and day without fail. Auto scheduling the email report saves me a lot of time and complications.

I also like the fact that Team Support is compatible for API Integration. We are looking to develop a centralised platform in our firm and want to be able to fetch info from Team Support for Data Analysis. This is in our pipeline and we are looking to implement this sometime in the future.

In the past the upper management used to shoot us emails enquiring about the particular issue. It takes up our time to email the management back with the status of that issue. Now the upper management simply logs into team support to view and oversee the status of a ticket/issue

Cons

However, the frustrating part of Team Support is the reporting section. When I open up the inventory report, it displays a list of all the terminals I have added to the inventory and when I want to get more information on a particular terminal, I notice that I cannot click on the terminal to navigate to that terminals page. Not only that, I cannot copy the serial number of the terminal from the inventory report. This applies to pretty much all the reports. All reports are in read only format. I humbly request Team Support to make the items on the report as clickable and actionable in the future.

Pros

I like the flexibility that is combined with a simpler setup. Not everything has a million ways to configure it, and that's okay. The integration of ticketing inputs (email, portal, chat) is really good which allows us to build a simpler experience for our customers.

Cons

There are some features like reporting which could use a major overhaul for an out of box experience. Thankfully, API support is there so that we can design our own dashboards, but the current reporting tools can only get you just enough data and is horribly presented.

Pros

Ability to customize ticket entry questions.
Ability to allow customers to directly enter tickets
Ability to allow for texting our cellphones for tickets that have not yet been assigned.
Ability to enter time on tickets, and retroactively enter/change time.
Ability to search on old issues and for our customers to see the issues.

Cons

Inability to tag a ticket with a "classification". (we charge different rates and minimum hours for different times of day/week/holiday) There isn't a good way to track that in the system and we are having to use the comment entry to work out offline ourselves.

My customers want 1 report entry (at the end of of the day), that shows them what the issue was, and the final resolution (only), and time/$ breakdown per time spent on the project. I do find it hard to externally work a report for that. We have had to generate a VB application to manipulate/merge and calculate everything based on the reports that I can get form the system in order to get what we actually need to share with our clients.

CDI should take into account tickets that are "Waiting on Client". (and remove them from the calculation) Currently, I have 2 tickets that are waiting on clients, but the CDI is "maxed out", because it has taken then more than 2 months to get their "act in order". That shouldn't frustrate them and drive the CDI up.

Why can my clients (outside their contract date enter a ticket, but I cannot enter a ticket for them?). Sometimes we need to "catch them up later".....

I need a way to track our active "on-call" resource and make it so that our ticket automation only alerts us the "on-call" resource (via text message) to those considered currently "on-call". Currently, we have to change that setup manually (pain).

Pros

TeamSupport is easily customized to our likings and their software support team has been beyond helpful and always available for assistance.

Cons

Inability to manage existing datasets in bulk. There is no way to mass update customers, assets, products, etc.