I think Front is very useful for every company with multiple teams working together on different emails from clients. Not so useful if a lot of different teams need to work on a request at the same time, because when an email is sitting in multiple shared inboxes things can get messy. Also would not recommend for teams that work is individualized, as team work is the main point of Front.
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.
Even if you are just trying to compose a single email, Front gives a smart system that has options such [as] organized templates, tags, alerts, [and] changing your outbound dpt email.
Tasks- with Front you will not miss any interaction. When you are required to get assistance from a coworker, you only need to mention him/her and that notification will appear automatically in their inboxes.
Smart Notifications- sometimes we are just overwhelmed about the several notifications on our devices that we tend to miss some of them, but Front offers a new way to notify every email, discussion, mentioning, or tag that you really would not want to miss.
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).
Their integration to Salesforce is lacking. As the owner of our productivity tools and how they are used, I have very little control over what things to enforce, or even change what objects are available. For example, we don't use Cases in Salesforce but with the Salesforce integration the Cases object shows up. There's no need to have that there. I've heard there is a roadmap improvement forthcoming.
One of our uses is for our sales development reps to prospect with visitors. Because of the high volume of inquiries it's difficult for our reps to efficiently manage all their follow ups. It would be nice if we could run a "scheduled campaign" where a predesigned cadence of email follow ups can be sent automatically. To be clear, they do have a scheduling capability, but it just can't be used as a prebuilt option.
Integrations to other systems require you have a user account to those systems. We have SSO and therefore we don't always have a user account. For example, out integration to Jira uses SSO so we don't each have individual Jira logins. This is an outage for us.
It's very easy to understand and use by new customer support agents as well. Be it a technology, product, or marketing person, we have trained most of the company folks to read and respond to customer conversations in their free time with the help of the Front app. It is also easy to set up for an admin and manage his/her team with communication rules.
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 support is good, and it's definitely prompt, but still lags when it comes to technical requirements, as I guess they are slow in developing newer features fast. So no complaints in terms of responsiveness, but yeah, at times it's not very helpful when you need certain features or are blocked on things which can't be unblocked.
This is something I am not familiar but it seems like it is [available] in Gmail. Thus I cannot give any feedback about it. What I am sure about is Front works for our team and I see Zoom using the service in the Customer Success Organization in a long run.
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.
