Creating an Internal Knowledge Base in FuseDesk

Internal Knowledge Base Early Access is now open! Contact Us to get started!

If you’re looking to organize your internal documentation, Standard Operating Procedures (SOPs), training documentation, systems, and more, you can now do so right in FuseDesk!

Help your teams stay organized, train up your new team members, and keep the documentation they need most right at their finger tips.

Creating a new Internal Knowledge Base

To get started, head to Knowledge Bases in FuseDesk and create your first Internal Knowledge Base.

By default, this will create a welcome page that you can then customize.

From here, you can continue to add new content to your internal knowledge base.

Editing Knowledge Base Content

You can organize the content you create for your internal knowledge bases by setting a Parent Page. This will organize your content hierarchically for your team in the sidebar navigation.

Cross Referencing Content

In addition to the usual formatting, you can also easily link to other content you’ve already published.

Simply click the dropdown of other published content – or type + in the editor – and select what you’d like to link to.

This is a great way to cross reference content for your team.

Tagging Team Members

You can also tag a team member in your documentation by typing @ and then selecting the team member you want to tag.

This allows your team to know who to contact, see if that person is online, and more, right from their documentation!

Checklists in Content

In addition to the usual bullet lists and numbered lists in your content, you can also add checklists for your team to see what steps might be required in a system or process.

From the toolbar, click the checkbox icon to create a checkbox list right in your document!

Knowledge Base Content Ideas

What might you put in your internal knowledge base?

Some ideas to get you started:

  • New team member training and onboarding
  • Your systems, standard operating procedures (SOPs) and documentation on how to do what you expect your team to do
  • Frequently asked questions (FAQs) that your team might encounter when assisting customers
  • Sales documentation for your sales team supporting your prospects, for example products, pricing, and scripts
  • Technical support documentation for your team to better assist your customers