osTicket is an open-source help desk / ticketing platform that can create inquiries online, through email, and through phone calls.
$12
per month
Parature (Discontinued)
Score 5.0 out of 10
N/A
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.
N/A
Pricing
osTicket
Parature (Discontinued)
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
osTicket
Parature (Discontinued)
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
osTicket
Parature (Discontinued)
Features
osTicket
Parature (Discontinued)
Incident and problem management
Comparison of Incident and problem management features of Product A and Product B
osTicket
7.6
9 Ratings
8% below category average
Parature (Discontinued)
-
Ratings
Organize and prioritize service tickets
7.99 Ratings
00 Ratings
Expert directory
9.04 Ratings
00 Ratings
Subscription-based notifications
8.47 Ratings
00 Ratings
ITSM collaboration and documentation
7.27 Ratings
00 Ratings
Ticket creation and submission
6.89 Ratings
00 Ratings
Ticket response
6.29 Ratings
00 Ratings
Self Help Community
Comparison of Self Help Community features of Product A and Product B
osTicket
8.3
7 Ratings
3% above category average
Parature (Discontinued)
-
Ratings
External knowledge base
9.05 Ratings
00 Ratings
Internal knowledge base
7.57 Ratings
00 Ratings
Multi-Channel Help
Comparison of Multi-Channel Help features of Product A and Product B
For beginning smaller companies that are in need of partially automating their incoming requests this product is easy to set up and will assist in structuring these request[s]. These requests can come in via email/phone or web portal. For companies that are beginning to streamline their support procedures, this tool can be a first step into automating part of these processes. This is also how user[s] should see it. It is merely a tool that can assist in structuring the incoming request flow the rest still has to be fit into business processes.
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.
osTicket is extremely user friendly for end users and support agents. It's very easy for new end users to put in a service request. This aspect of simplicity is important because we don't have to train new users on how to put in service requests.
Feature wise osTicket has everything you need without being overly complicated or cluttered. This is important for us because it allows for faster support times and happier end users.
Lightweight and very reliable, osTicket uses PHP and MySQL. Setup is easy and it can be hosted internally or externally web hosed. Also, since it relies on PHP it gives you flexibility to use Apache, Nginx , Lighttpd , IIS, etc.
Thriving community: the community behind osTicket is feature-wise. Which is very helpful if you have any questions.
Best of all, osTicket is completely free and open source. While they do offer pair tier cloud-hosting and enterprise support. The free version offers all the features of the paid tiers (minus hosing and support).
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.
I am familiar with osTicket and this allow me to teach all the staff and support them whenever they have any concern regarding the usability and following processes.
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.
osTicket has proven to be a very useful tool for the team to help support the business. Open-source was the right price point and self-hosting as mentioned was quite important (however I believe that osTicket does have a hosting solution available if needed). Jitbit was a close contender but didn't like how it doesn't separate people submitting tickets from users acting as agents. So all in quite happy with the choice.
When we had a hosted version of osTicket, we were saving some time by having them work on our setup, but we were spending a lot. Switching to our own osTicket build from their open sourcing not only saved us money upfront but we actually spent LESS time developing because we knew our ideas and didn't have to explain them to another (unrelated) party.
Creating our own ticketing infrastructure for institutional data requests has been a game changer for us. We have been able to interface with our enterprise email client and create a level of customization that meets our existing informational technology culture.