TeamSupport

Team support makes us a more efficient with customer support.

Puntos a favor:

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.

Puntos en contra:

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.

Intuitive, Useful Software Company-wide

Comentarios: Overall, our company has toyed with the idea of using competitors but TeamSupport has held strong as a useful solution for us whose advantages outweigh its detractors.

Puntos a favor:

I like the largely intuitive interface and functionality. Creating actions (public/private) are extremely easy as is pasting in-line images, adding attachments and customizing ticket types. Once saved, the formatting of actions are ideal and translate to what the user entered. Not all other ticketing software handles it this well.

Puntos en contra:

Performance/stability has certainly improved over the years and has become more reliable. Despite that, there are the odd instances of slowness or degraded performance. The reporting could be more robust and easier. The ability to create more than one new (unsaved) ticket simultaneously would be very helpful.

Amazing tools with worth for small organizations.

Puntos a favor:

Ticket collision and even calendar, Customer Self-Service, Ticket Deflection

Puntos en contra:

Ticket Automation & Routing Rules,Collaboration Features Within Tickets

More capable than most, but still some additions I'd like to see

Comentarios: Getting the system configured for our particular use has been "tricky". It is working for us, but there are some limitations that make it difficult in some areas. For instance, notification via text message should be based on "who is on-call". As it is, I can notify, but I have no-way to denote who is "on-call". So, there may be some way to do this and change the external calls/texting based on it, but it isn't intuitive. Another issue has been with refreshing the screens. (we need to manually do that) However, this system is working for us an our clients, overall, and has met 90% of our needs. Working with customer service, we have had to resolve our own issues on occasion, which is a frustration. (no ideas presented to us, and we just "found" a way)

Puntos a favor:

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.

Puntos en contra:

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).

Customer support can be more efficient with TeamSupport.

Comentarios: I really like TeamSupport a lot. It has helped us get in touch with our customers through live chats, IT ticketing system, and reply to inquiries on time, thus improving our relationship with our customers.

Puntos a favor:

It is easy to understand and has many useful tools, as well as being able to modify it for what is most valuable to us. We can save customers, and when they create new tickets, their info is populated automatically.

Puntos en contra:

I have nothing to dislike TeamSupport. But they may improve their website. Site functionality or page load times have occasionally slowed down.