BookStack vs. ServiceNow Customer Service Management

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.

Incentivized

It is well suited for medium to large companies that manage different teams and need to communicate constantly and track progress in a timely manner. It is less suited for small enterprises as it will overwhelm users with the features and functionalities embedded.

• Documentation
• Guides
• Knowledge-base
• Version control

Incentivized

• Allows for clear communication between help desk and end users.
• Provides a clean inventory option for both hardware items and software licenses.
• Navigation is very intuitive and user friendly.
• Many reporting features for all levels of the company.

Incentivized

• Continuity in backward compatibility
• Dark mode
• Absent tree view

Incentivized

• Adding in additional chat features would be nice
• Viewing where you stand in priority
• Having a way to automate more of the processes

Incentivized

Bottom line is that it does what you need it to do. We've been using Service Now as a ticket managing tool for a few years now. There's really not much it can't do when it comes to recording interactions. It has been nice using inventory tracking for software licenses and hardware as well.

Incentivized

Support has been very good. Any time there has been a real issue, the team has responded very quickly and identified the issue without a lot of repetitive questions that I've seen from other services. There is a great external community and internal knowledge base that covers pretty much anything you need.

Incentivized

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.

Incentivized

Connectwise targets small to medium enterprises and kept things simple for cross-organizational communications. On the other hand, ServiceNow with users with more than 500 at least, tends to create lag and tension when all are using the app at the same time, especially getting reports in a timely manner.

• 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.

Incentivized

• The negative impact for my team is the delay in team completing tickets but not a system issue.
• A positive impact for my team is we can easily view the status of tickets and the follow-up emails are beneficial to maintain records of tickets.
• Negative impact is that there is no user job aid or helpful tools for new users.

Incentivized