Lares advice on setting up your knowledge base

This is not available to the public, think of  it as a project management area where you store important links, images, project timescale etc

Then, using internal or external Ai, within an article, ask for suggestions for the categories required for your business and a brief explanation.

Again - store but dont publish to a category

Before a client sets up a TAWK knowledge base, they should have a clear plan and the necessary assets in place. While the TAWK platform makes the technical setup relatively simple, the content and strategy require some preparation. Here is a bullet-point list of what is exactly required:

• Content:

  • Article Topics: A list of frequently asked questions (FAQs), troubleshooting guides, and step-by-step instructions. This content is the core of the knowledge base.

  • Article Content: Drafted articles for each topic, including clear headings, explanations, and any necessary images or videos.

  • Categories: A logical structure for organizing articles into categories (e.g., "Legals" "Getting Started," "Billing," "Troubleshooting").

  • Internal vs. Public: A decision on which articles will be public (visible to customers) and which will be private (visible only to the team).

• Branding and Design:

  • Knowledge Base Name: A name for the knowledge base (e.g., "Acme Inc. Help Center").

  • Subdomain: A chosen subdomain for the knowledge base URL (e.g., support.yourcompany.com).

  • Logo and Favicon: A company logo and a favicon (the small icon that appears in the browser tab) to maintain brand consistency.

  • Branding Colors and Fonts: A primary color and font style that match the client's brand.

• Technical Information (Optional but Recommended):

  • Domain Configuration: If the client wants to use a custom domain (e.g., support.yourcompany.com instead of yourcompany.tawk.help), they will need to have access to their DNS settings. This is a paid add-on.

  • Google Analytics: A Google Analytics tracking ID to monitor visitor behavior and search patterns within the knowledge base.

  • Social Media Banners: Images that will appear when knowledge base links are shared on social media.

• Team and Workflow:

  • Team Members: A designated team member or group responsible for writing, editing, and publishing new articles.

  • Content Maintenance Plan: A process for regularly reviewing and updating articles to ensure the information remains accurate and relevant.

  • Feedback Mechanism: A plan for how to gather and act on customer feedback about articles (e.g., a simple rating system).