Knowledge Base

The Knowledge Base is your self-serve documentation layer, a searchable collection of articles, guides, and how-tos that the client can reference anytime from inside GHL. When a client wonders how to do something at 11pm on a Sunday, they do not have to wait for chat support or remember details from a training call three weeks ago. They search the knowledge base, find the article, and get their answer. Always available, always consistent, always patient.

Why This Matters

Support volume scales linearly with your client count unless you build leverage into the system. Every new client adds 8 to 15 support interactions per month. At 10 clients, that is manageable. At 50, your team is underwater. The Knowledge Base is one of your highest-leverage tools because a single well-written article can answer the same question for every client, forever. Write it once, and it saves your team thousands of repetitive interactions over the life of your agency.

The other dimension is client confidence. Clients who can find answers on their own feel more capable and more in control of their system. They build independence faster and rely on live support less. That independence is exactly what you want because it frees your team to focus on strategic work rather than repetitive explanations, and it makes the client feel like they are mastering the tool rather than being dependent on you.

Without a Knowledge Base, your support team becomes the knowledge base. They are the only source of truth, and every answer lives in their heads or scattered across old chat transcripts. When a team member leaves or is unavailable, that knowledge disappears. A documented Knowledge Base is institutional memory that does not take vacations or change jobs.

How to Think About It

The Knowledge Base is your asynchronous training layer. The Live Onboarding Call is synchronous, one-time training. Loom Walkthroughs are personalized, reactive training. The Knowledge Base is standardized, proactive training that is always available. Each layer serves a different purpose, and together they cover every learning scenario.

Start with the 20 questions your clients ask most frequently. You already know what these are because your team answers them every week. Write clear, concise articles for each one. Use screenshots. Use step-by-step formatting. Write at a reading level that assumes the client knows their business but does not know GHL. This initial set of 20 articles will cover 60% to 70% of first-line support questions.

Grow the Knowledge Base based on real support data. Every time your team answers a question through HL Pro Tools chat or Support Tickets, ask whether a Knowledge Base article would prevent that question in the future. If yes, write the article. If you do this consistently for six months, your Knowledge Base will cover the vast majority of recurring questions and your live support volume will drop significantly.

Common Mistakes

Writing articles for yourself instead of the client. Internal documentation uses shorthand, assumes context, and skips “obvious” steps. Client-facing documentation must assume zero prior knowledge of GHL. Write every article as if the reader has never seen the platform before today. What you consider obvious, they consider confusing.

Building a massive Knowledge Base before launch and never updating it. A Knowledge Base that was accurate six months ago but has not been updated since is worse than no Knowledge Base at all. Outdated articles that reference old interfaces or deprecated features create more confusion than they resolve. Assign someone to review and update articles monthly.

Organizing articles around features instead of tasks. Clients do not think “I need to learn about the Conversations module.” They think “How do I reply to a text message from a lead?” Organize your Knowledge Base around tasks and questions, not around GHL’s menu structure. Task-based organization matches how clients actually search for help.

Not promoting the Knowledge Base during onboarding. If the client does not know the Knowledge Base exists, they will never use it. During the Live Onboarding Call, show the client where to find the Knowledge Base, search for one article together, and position it as their first stop when they have a question.

Making the Knowledge Base hard to access. If finding the Knowledge Base requires three clicks and a secret handshake, clients will default to asking in chat. Make it accessible from within GHL, ideally from the same help menu where Page Overlays and HL Pro Tools chat live.

Tools Involved

The Knowledge Base is typically delivered through HL Pro Tools, accessible from within the client’s GHL sub-account. It works alongside Page Overlays for contextual, on-page guidance and the live support channels (HL Pro Tools chat, Loom Walkthroughs, Zoom Escalation) for interactive help. Articles often reference GHL features like Conversations, Calendars, and Workflows.

Where This Fits

The Knowledge Base sits at sequence position 26 in the Support Infrastructure category. It depends on Sub-Account Provisioning because the documentation needs to be accessible within the client’s sub-account. It goes live alongside Page Overlays, HL Pro Tools, and Direct Contact as part of the full support layer. The client is introduced to the Knowledge Base during the Live Onboarding Call.

Common Questions

How many articles do we need before launching the Knowledge Base? Start with 15 to 20 articles covering your most frequently asked questions. You do not need comprehensive coverage on day one. A small, high-quality Knowledge Base that answers the top questions is more valuable than a massive one with shallow, unhelpful articles.

Who writes the Knowledge Base articles? Ideally, the person on your team who handles the most client support, because they know which questions come up repeatedly. If you are a solo operator, set aside two hours per week to document the questions you answered that week.

Should Knowledge Base articles include video? Short embedded videos can be helpful for visual processes, but always include written steps as well. Some clients prefer reading. Some prefer video. Some are in a meeting and cannot play audio. Covering both formats serves the widest range of preferences.