Parature was a self-service customer support platform providing a self-service knowledge base to connect with customers across multiple channels. The company was acquired by Microsoft in January 2014 and reached EOL in 2017.
I'm currently using Solarwinds Web Help Desk and I think the 2 are very comparable. I didn't select either product but I'd rate Parature at the same level as WHD or better.
Before choosing Parature we reviewed many of the currently available solutions before building our short list of Parature, SugarCRM, Zendesk, Salesforce, and NetSuite. In the end, the licensing models for Salesforce and Netsuite eliminated them from consideration. The SugarCRM …
Parature comes in at just the right blend between ticketing solutions like Ceridian and Remedy. Ceridian is a little too cut-down/simple while Remedy can be mired by its complexity. Parature shares the same features as quite a few other ticketing solutions, but hits strongly in …
Salesforce is so much more intuitive and the layout is so much better. I never had any training nor did I need it with SF and with Parature it was a constant battle to understand its issues. I don't like to feel I have to resort to a manual every time I use the product.
Between SolarWinds and Altiris, I like the advantage that Parature gives. The auto reply is a huge assistance when dealing with people outside of my organization.
The single element of Parature I've not seen in any other system of this kind is the Download Module. You can post files in the open, or protect them by any number of entitlement methods. The solution is also appealing to those who don't want to manage the back-end/IT needs as it is a hosted solution and has proven to be very reliable.
Clean/Friendly UI. It was extremely easy to navigate around Parature's menus at a high level, and you could take advantage of the more robust features as you became more comfortable and familiar with how Parature operates!
Strong Knowledge Base. Writing KB articles or ticket summaries and making use of the search function within Parature allows for expedient recovery of past ticket information. Being able to search for a fix action, or at least a troubleshooting article that can guide you towards a resolution is extremely valuable.
Enhanced Notation Capability. Being able to send/post internal or external updates to a ticket is great! You can leave the wordy technical details for other employees while making sure to communicate the high-points and fix action to the end-user.
Reporting is barebones at best. If you need special reports, we had to go through Parature to have them built.
The use of frames on a website is very 1990s. It actually impacts usability of the product, especially when combined with how Parature handled sessions. An engineer could only work one ticket at a time which, honestly, isn't very realistic for a busy support team that is working on several issues at a time.
Support was often unresponsive when contacted for unplanned problems.
The knowledge base was not very friendly for clients and it provided no real encouragement for it to be used.
It took several clicks to do something as simple as edit and assign a ticket or to close a ticket.
It was bulky, cumbersome, and didn't allow us to handle the volume of cases we received on a daily basis. Many of our issues were highly technical in nature and we would often need to work on 2 or 3 at once. The poor design choices prevented this, which was unfortunate.
They recently had one very extended outage. It was a data center issue - but they were not diversified enough so in the end the system was down for almost 8 hours. There are also periods of time where for no reason the system simply doesn't respond. This small outages are usually short (just a few minutes), and have in fact been occurring less often, so it appears some corrective actions have been taken.