TeamSupport was great decision for us
Use Cases and Deployment Scope
Pros
- TeamSupport is great at allowing the user to respond much in the way you can in a rich text e-mail tool. Many solutions we had looked at were strictly text based and are hard to follow. With TeamSupport we can have rich content in our responses including formatted data, tables, graphs, pictures and such.
- TeamSupport is very easy to get going with their sandbox environment in that you can get started with a few simple clicks.
Cons
- 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.
