Uploading every available file does not automatically create a useful chatbot knowledge base. An old price list, a current product page and an internal exceptions document may contradict one another. Preparation means deciding which source answers each customer question and what the assistant should do when the available information is insufficient.
Group real questions before organising files
Collect recurring questions from sales and support, removing personal information from the examples. Group them by customer task: understanding a product, checking suitability, arranging delivery, using a service or resolving a problem. Keep different phrasings of the same question together. Customers should not need to know your internal terminology.
Define what a successful answer does for each group. Stating dimensions, comparing options and showing an individual's order status require different kinds of information. The last task should not be answered from a general help document; it belongs in a separate workflow with authorised access to the relevant operational system.
Assign an authoritative source to each subject
Use a source register to show which information is approved. Its owner should be able to verify the content, rather than simply being the person who uploaded it. Resolve contradictions before activating both an outdated document and its replacement.
| Information area | Authoritative source | Update check |
|---|---|---|
| Product specifications | Approved product record | Owner review when the product changes |
| Service scope | Current service definition | Agreement with proposals and website copy |
| Delivery guidance | Operations-approved conditions | Regional and exception changes |
| Account-specific status | Authorised live system | User permissions and data freshness |
| Unresolved questions | Support routing policy | Team, channel and opening hours |
Write content with clear conditions and context
Make the subject, applicable product or service, conditions and exceptions explicit. Prepare explanations that stand on their own instead of relying on the visual headings in a long presentation. Preserve units, package names and version information in tables. Provide a readable text equivalent for essential information that exists only inside an image.
Consider a hypothetical remote installation service. Its guidance should identify the supported products and distinguish remote assistance from an on-site visit. Do not expect the assistant to infer missing service boundaries. A short glossary of product terms and the everyday names customers use also makes the information easier to maintain.
Separate public help from internal information
Do not include private pricing discussions, other customers' notes or employee access details in public-facing knowledge. Decide who can see each source. Microsoft's Copilot Studio documentation describes different authentication requirements for different source types; connecting a source is not the whole access-control design.
Design an explicit response for missing or conflicting information, with an appropriate support route. Providing a source link can help the customer examine an answer, but the presence of a link does not prove that every statement is supported. Review the actual claims against the source, including exceptions the response might omit.
Verify that changes reach the assistant
Editing a document and making its contents available to an assistant can involve separate preparation or refresh steps. Identify the process in your chosen system, who owns it and how completion is checked. Keep approval, activation and rollback decisions traceable so the team can understand which information was available.
Maintain sample questions and the required answer points for important subjects. After a change, test both questions about the new information and related existing questions. When a source is removed, check whether the assistant continues to produce its outdated content. This makes knowledge maintenance a repeatable operating process instead of an occasional document upload.