BookStack is fantastic for having business users and not-so-technically-savvy IT users. It enables them to create a documentation they like in a visual way while still forcing them to adhere to logical structure of a document. It works fine even for more technical matters such as integration guidelines, especially when these concern some of the more obscure technologies. The exported docs are presentable but lack any interactivity. Where it lacks is generating heavily technical documentations. Heavier REST or GraphQL integrations should for example be documented through other means. As for developer documentations, there are definitely more suitable alternatives, also.
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.
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.
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.
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.
Confluence, having only a slight advantage in terms of features compared to BookStack, really only makes sense to procure as a part of the Jira bundle. It requires much more maintenance from my experience and does not really deliver any extra value aside from the very strict certifications like HIPAA. DokuWiki and MediaWiki both provided way too much in terms of customizability, not really focusing on the business need. Of course, MediaWiki was conceived for a whole different purpose but is very often seen being used for both internal and public documentation delivery. DokuWiki did not provide the authors with the user-friendly environment that BookStack has and integrated most poorly with LDAP. As for OneNote, which was used for support docs prior to BookStack, it provided the authors with too much of a user-friendly environment, rendering the product of their work very inconsistent. Also, the sharing model was either peer-to-peer or within Teams, neither of which made it easy to audit and supervise.
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.
Spillover within Business IT staff up, nearly double substitutability. This is through the ability of a support technician servicing a different product to find a guide describing how to solve the more frequent issues the way a product lead would do it.
Time to draft and publish a documentation down some 20% compared to previous solution.
OpenSource that integrates fine with enterprise-grade software and somehow even passes security audit. 20 times cheaper to implement compared to Confluence, almost free to maintain.
