Tracing any maintenance requests, so you don't forget any requests, it also sends an email to the requestor once the project is completed. Keeping status of projects in progress and the current state they are in. Allowing anyone with access to know the current state of any project. Generating a useful report is a bit more difficult then I would like.
From a technician's point of view, it is extremely easy to create new work orders or tickets. It's also very simple to enter in data and keep track of the state of the ticket without taking too much time to keep it updated. I would love to see a cloud instance available to be able to make it a global installation as our company grows.
Documentation. We try to reduce the amount of paperwork needed for staff to do their job, so by automating certain tasks, we are able to speed up the resolution process for trouble tickets.
Reporting. We'll use the reporting tool to get the number of tickets opened, response times and can go into granular reports.
Surveys. When tickets are closed, we automatically send out surveys to end users to get valuable feedback on how we did and what we can improve.
Purpose based configuration- It would be beneficial to see a more purposed based, out of the box, configuration option. For example, if you need PCI compliance, more intuitive reporting would make managing compliance much easier.
Initial design and implementation- Don't think that your experience as an IT professional will allow you to stand this system up on your own. To properly configure Footprints and set yourself up for success down the road, get Professional Services with this one.
Somewhat behind the times- Service Core is making a huge leap forward with the latest version, 12, but Asset Core is far behind. There are quite a few quirks to how the application works and how it is used.
Care must be taken when configuring automatic replies otherwise you can end up in an endless loop of emails if response goes to another auto-responder. This will cause tickets to automatically be generated with every reply and then it takes a while to clean up the unwanted tickets.
The support model is prohibitively expensive if you let support lapse and then need support once again. This is because they expect you to pay for all of the previous versions/years between when you last paid for support and their current version. This means that if there have been 3 versions of the software since you last had support, they expect you to pay for the 3 versions even if you did not use them. This is a primary reason why we are looking at alternative ticketing systems currently.
It would be nice to have the ability to selectively kick a user our of a ticket without having to kick them entirely out of the application.
It has been the business decision to go with them and that is what we will do. Going back, this would have not been the choice, but nothing can be done about it now. We are stuck with this application for years to come. Wish there were other possibilities that could be done.
It's so simple to use and customize however you want. You can create new workspaces and workflows with ease, set up new users, incoming email rules, customize the layout of the forms, and even change the colors and logos. It's just very easily customizable overall. It's also really straightforward to figure out how to use, you really almost don't have to show somebody how to use it. If you just sit them down in front of it and let them look it over, they could figure it out themselves easily.
I've had no issues with the support for FootPrints. We haven't really had to use them all that much over the years, but when needed they have always been prompt and knowledgeable at dealing with any issue. I've worked with a lot of different support teams over the years, and they have been one of my favorites to work with.
I only gave it this rating for the fact that we did not really use their support for much of the time we used the product. The support documentation in the actual program seemed to be lacking, so finding the information via the web or the vendor's site provided more helpful, from a support standpoint. I did notice that the vendor does have a portal where you can manage support cases and also has live phone support and an email option. All of these options are good for any customer that needs good support while using the product
Both are developed from the same vendor but Footprints is so complete for all the configurations that we need (we are a medium business company). BMC Remedy has a little more friendly interface but it doesn't meet our needs. We prefer a product that fits better our needs to a product that could have other features that we are not going to use.
ConnectWise was far more robust with a lot more customization, project management features, templates, and documentation. It tied into other software that we needed to do our jobs. The interface was cleaner, the software was faster, and users had an easier time. Oversight was also much better. That said, it was also far more expensive, and it was developed more for managed service providers and large companies than smaller enterprises like ours.
