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.
ServiceDesk Plus is very easy to configure at the start, and then adjust the categories and rules as the implementation is refined. Its greatest strength is the ability to program without requiring a full time administrator. There is very little jargon involved. Reporting not so much. The canned reports are useful but do not always cover some of the basics. Fortunately, the user groups freely share report definitions so one could springboard from something close to your desired result.
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).
Ticket logging for end users, so they can see the progress on their help requests
Asset management; it has an agent that can be installed on machines which can then feed back information on installed software, active times, logged on user etc
Project management; larger projects can be managed within ManageEngine ServiceDesk as well as end user help tickets, where progress/milestones etc can be recorded
Active Directory import of users, so that it automatically updates when users are created/deleted and links their accounts in ManageEngine ServiceDesk with their email address as well to enable email alerts
When trying to select the top row ticket, you have to be careful not to select all tickets. Happened to us twice and we assigned all open tickets to one technician. Took a few minutes to correct.
Site is sometimes a bit sluggish to respond. Don't know if that is an issue with our network infrastructure or the program itself, though.
When users send emails to the help desk, we sometimes experience delays until the tickets appear on the site for the technicians.
we are looking at other tools like Zendesk which may replace ServiceDesk. We are currently evaluating both tools to see which one would serve our needs better
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 is still very cumbersome, lots of data entry on the back end to build how we want it but it is still not completely user friendly. Many functions still dont work and contacting someone for help isnt always easy or we get told solutions for issues we have just arent built yet.
Our network administrator usually gets a good response when contacting ManageEngine ServiceDesk Plus customer service. They are quick to respond and so far have been able to eliminate most of our issues. We have been through several upgrades of the software over the years and have no issues to report in regards to customer service.
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.
Compared to Cherwell, SDP is much much faster, and easier to deploy, set up, and use. But it does not have automation, and has limited customization. Since it is smaller and easier, it does not require any development effort. On the other hand, it is far more expensive, considering its lower capabilities, and its licensing model is not concurrently based (each technician uses up a license, even if the technician is not actively logged in and using the tool).
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.
ServiceDesk Plus has helped our organization see what issues we face on a more global picture and we are able to take the time and resources to correct them in a timely manner.
The only negative part about ServiceDesk Plus is it can become costly when you see and use all the features it has to offer.
