For a typical technical support help desk use case Freshdesk Omni is great! It has the advanced features of automating responses and canned answers where appropriate. The AI functionality seems good but not something we are leveraging at this point given the volume of tickets.
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.
When an agent receives a call via Dialpad or Amazon Connect, Freshdesk Omni automatically displays relevant customer details, previous interactions, and ticket history in a single view.
Every call (answered, missed, or voicemail) is automatically logged into Freshdesk as a ticket, including details like call duration, customer number, and agent notes.
Agents can initiate outbound calls directly from Freshdesk using click-to-call functionality, reducing manual dialing errors and saving time.
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).
Utilizing a unified platform has successfully reduced the resolution time for customer-facing issues. This streamlined approach enhances efficiency and generates valuable insights that can be leveraged to improve our services and better understand customer needs, ultimately leading to a more satisfying experience for our clients.
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.
1) Price is also a point to decide, other Service Providers were providing similar features but the prices were slightly on a higher side. 2) Coming to feature comparison, JIRA offers whole lot of other features but currently we did not require them and Zoho had few less features comparing to Freshworks
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.
