TeamDynamix is a rock solid platform for ITSM, asset, and project management. It offers a lot of features in a relatively simple to maintain platform, putting time back into the hands of staff who may spend a lot of time with configuration on other platforms. The support is second to none. There are so many ways to get help, from TeamDynamix itself, but the user community is robust and extremely supportive.

TeamDynamix as a platform is easy to use, easy to understand and well featured. It offers a lot of functionality in the core platform, giving customers the flexibility to grow into it and for it to grow for an organization. The ability to quickly create a variety of ticketing apps, support portals for knowledge and service management will help to quickly allow for adoption across an organization.

There are some quirks with he product that could use improvement, especially around email notifications, There is some customization available, but there could be more to allow for more dynamic use of email messaging. There is also currently no real mobile view from an overall ticket management perspective.

It is mostly positive. It has been relatively quick and the ability to upload documentation and images is very nice. One thing that bugs me is that attachments open in new windows/tabs and I don't see an option to set how you'd like that to happen. It would be nice to have a document always open in a new window. It would also be great if I could set tickets to open in a new tab instead of new windows but I don't see that as an option either. The workflow overall is pretty good and writing reports is pretty powerful yet simple. The day-to-day ease of use could be improved though. Also, support for high-efficiency HEIC images would be great. JPEG and PNG are good but a lot of newer phones shoot in HEIC by default. It would also save some space with attachments.

The ease of entering most information is very nice. The fact that we can route things pretty efficiently is also quite nice because we can route things to another user or group/responsibility easily. Integration options are pretty good and the fact that it supports our Single sign-on method for increased security is a plus.

It isn't always as flexible as IT needs it to be. It is not possible to have a requestor and recipient which would be a great help. Many of our users have office managers or assistants that submit work orders/tickets on behalf of the user experiencing an issue or requesting a service. Having the ability to have a requestor and recipient specified in TDX would be awesome. We also don't have an easy way to split tickets as the system is currently implemented. For example, we often have users submit requests to have say five PCs set up but our workflow requires we have one ticket per device for proper tracking. This becomes a greater issue when users need equipment repaired. It may be a bit of a limitation of how we are implementing things but simply copying the work order requires we adjust multiple pieces of content or triggers a workflow for which users need re-approve tickets since there are charges for some services and not others. The ability to clone tickets with the approval status still in place would be a great option for situations where the requestor has already approved the charges for the work on the main ticket. I would also really like to see an option to require data fields at specific steps in the ticket workflow. Currently, this seems very limited. For instance we can require someone to enter their phone number and location but we can't require the technician fill out the solution or resolution method for the ticket when they are resolving/closing tickets.

TDX is great when we were a bit looser with our fields and reporting, but I've grown to really dislike it as the information required from me is slow to resolve. Now that our organization is focusing on reports above all else I often feel like I'm fighting against the system.

TDX is by far the most intuitive ticketing system I've used. Its reporting features are powerful and as a user it's very easy to understand.

Input resolution is slow and often inaccurate. The "autocomplete" often lists something I typed in exactly near the bottom of the list, or sometimes not at all. It creates a very slow, clunky experience.

We rely heavily on the incident management. It has been a very stable platform and functions well for ticketing.

The user interface is relatively simple and easy to navigate. It has become more useful with the recent features that have been implemented.

Our implementation was back on version 9. The newer versions added more features, but in turn caused a lot of our initial methods of ticketing to become obsolete. Now we have a tremendous amount of "bloat" that needs to be cleaned up.

Adopting TD has allowed us to mature as an organization.

Keeping all communications in a single place on a request is a must. Having a self service portal and knowledge base has helped campus tremendously. I appreciate that it was designed to be flexable and understand the unique needs of higher education.

It does not function very well on mobile. If you do not set up custom reports, it is easy to "loose" requests as they change states. It would be nice if there were a way to force ticket tasks. i.e. ticket could not be sent to another person or closed until a task was completed first.