SaaS Product Guides: Document Every Tool You Support
Organize customer-facing how-to content by SaaS product so users find the right answers fast and AI agents scope responses accurately.
The SaaS Product Guides section of your External Knowledge Base gives every tool your customers use its own dedicated space. Instead of a flat list of articles, you group content by product — so a customer troubleshooting Salesforce never has to wade through Zendesk setup guides, and your AI agents always know which product's documentation to draw from when answering a question.
What a SaaS Product Guide Collection Is
A SaaS Product Guide collection is a structured container within your External KB that holds all how-to content related to a single SaaS product. Think of it as a mini knowledge base scoped to one tool. Each collection is self-contained: it has its own landing page, its own topic categories, and its own set of articles. Customers browsing your help center see a clean product directory, and when they click into a product they immediately see content relevant to that tool — nothing more, nothing less.
How Products Are Structured
Every product in your External KB has four core elements:
- Name — The exact, customer-facing name of the product (e.g., "Slack", "Notion", "HubSpot CRM").
- Icon — A logo or icon that visually identifies the product in navigation and search results.
- Short description — One sentence that tells customers what the product does and who it's for.
- Topic categories — A set of groupings (e.g., "Getting Started", "Integrations", "Troubleshooting") that organize articles within the product collection.
Articles within a product collection inherit the product's context, which means search results, AI responses, and breadcrumb navigation all reflect the product the customer is working with.
What to Document for Each SaaS Product
A complete product guide collection typically covers:
- Login and initial setup — Account creation, SSO configuration, first-time onboarding steps.
- Key features — How to use the product's core functionality, broken into focused task-by-task articles.
- Common workflows — Step-by-step guides for the scenarios customers encounter most often.
- Troubleshooting — Answers to frequent errors, edge cases, and "why isn't this working?" moments.
- Integrations — How to connect the product to other tools in your customers' stack.
You don't need to document every feature on day one. Start with the highest-traffic support topics and expand from there as you identify gaps.
Why Organizing by Product Matters
When content is organized by product, customers spend less time searching and more time solving. They arrive at your help center knowing which tool they need help with — your structure should reflect that mental model, not your internal team's org chart.
For AI agents, product-scoped collections are especially powerful. When an agent is configured to answer questions about a specific product, it draws exclusively from that product's article collection. This keeps responses accurate and prevents the agent from mixing up instructions from one tool with those of another. A question about resetting a Salesforce password gets a Salesforce answer, not a generic one.
Get Started
Frequently Asked Questions
There is no hard limit on the number of SaaS products you can add to your External KB. You can create as many product collections as you need to cover every tool your customers use. If you are on a plan with content limits, each product collection counts as a single collection regardless of how many articles it contains. Check your plan's collection quota in Settings → Billing if you are unsure.
Articles belong to one product collection at a time. If you need the same content to appear under two products — for example, a shared integration guide — the recommended approach is to write a canonical article in the most relevant product and then add cross-links from the other product's articles. Duplicating articles word-for-word creates maintenance overhead and can confuse AI agents that encounter contradictory or near-identical content. Use cross-links instead to keep a single source of truth.
Removing a product from your External KB unpublishes all of its articles immediately and removes the product from your customer-facing directory. The articles are not permanently deleted right away — they move to an archived state and remain accessible to admins for 30 days in case you need to recover content. After 30 days, archived content is permanently deleted. Before removing a product, export any articles you want to keep and update any internal links that pointed to the product's collection.