TeamSupport

Avantages

Switch facile et bien géré très bon logiciel

Inconvénients

Un peu lent mais en prenant le temps on y arrive

Avantages

Easy workflow and team management - TeamSupport has improved our customer support vastly over the years, we use groups for our different support teams and brands to keep things well organized. Over the years we have taken advantage of more features and functions including asset management, automation and data management via API.

Inconvénients

There isn't much that we don't like about TS, but our team would benefit from a better mobile version that allows you to easily update customer tickets, at the moment the mobile functionality is designed to be more of internal operations and collaboration rather than customer-facing.

Avantages

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.

Inconvénients

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.

Avantages

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.

Inconvénients

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

Avantages

It doesn't take much mental effort to understand how the product works and how to apply the many facets of your support function to it. My innate teamwork skills allowed me to effectively coordinate with my colleagues, the client, and TeamSupport to improve our service to the customer.

Inconvénients

Outdated user interface. The business is ignoring its primary offering. Very little. Its features are so similar to those of other CRMs that you'll be hard-pressed to find one that meets your specific needs if you don't already use another CRM.