osTicket is an open-source help desk / ticketing platform that can create inquiries online, through email, and through phone calls.
$12
per month
SolarWinds Web Help Desk (WHD)
Score 8.0 out of 10
N/A
SolarWinds
Web Help Desk is ticketing and IT asset management software. It is designed to
simplify help desk management. This solution includes built-in ticketing
management, asset management, change management, and knowledge base
capabilities.
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.
SolarWinds WHD is well suited if you have a limited budget, as it costs less than many help desk software packages that are more full featured and modern in their design. It is not well suited to an environment where you want to manage inventory, users, purchases and tickets all in one package. It has an asset feature that we don't use but that looks quite limited. We track our assets and users separately from this.
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).
Customized reporting allows us to track our service and support better, and find where we need improvements. This allows us to constantly upgrade our service levels and keep the customers happy.
Detailed tracking and response to the end users have led to quicker remediation of tickets. We are able to see where we need a better response or where to add additional resources for support.
Overall metrics allow us to staff properly for our tickets by location and remote users.
Because of AD integration, users sometimes try logging in with their email address and not AD credentials. The user then calls stating they can't put a ticket in, it would be nice if there was a method of matching the AD Email field with a login.
Setting up new techs with the building they are responsible for can be a little messy
We are definitely going to be sticking with Web Help Desk for the foreseeable future since the product is very inexpensive for the features that it provides, the integration that it has with our existing systems, and the ease for managing users, assets, locations, and tickets. Web Help Desk is a great product that is backed by even better support, which is well worth looking into if you are considering moving to a new ticketing system.
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.
The system has time and time again proven to be much easier to use and setup for both technicians and end users. It is simple enough to enter a ticket for end users, and even easier to communicate with logging back and forth because you can reply to the ticket emails to enter comments on the tickets. The technician side is a little clunky at first, but after looking at it for a few minutes it's very clear to see what you need to do to accomplish the goals. The mobile interface is snappy and responsive. It's a great product overall.
SolarWinds is a great customizable and affordable ticketing system. We use SolarWinds Web Help Desk for IT and Software Development trouble ticket tracking and resolution. The reporting that SolarWinds provides is great since it helps us discover problem areas and fix those areas so they don't keep reoccurring
Take the time to roll out a test VM to configure and make changes to before doing a live deployment, this way you don't end up with a VM that has been tweaked and re-tweaked until it's perfect and instead end up with a final, polished product. I would also recommend taking the time to read through the support forums for figuring out minor issues that may pop up, chances are that you aren't going to be the first one to encounter them. When all is said and done, SolarWinds Support is VERY responsive and you shouldn't hesitate to contact them.
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.
Web Help Desk is definitely lacking in the UI/UX department compared to most other ticketing systems I have used int he past. It's very utilitarian; however, what it lacks in UI it makes up for in extensibility and customization. The main issue that the developers need to address is the use of a Web Objects back-end.
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.
