Updating chatbot knowledge is complete when the correct new information powers answers and the old statement no longer competes in active sources. Saving a file or changing a webpage does not establish that outcome. Begin with the fact owner, define an effective date and plan publication. This guide covers carrying out the change; a detailed test set for checking behavior after an update belongs to a separate workflow.
Trigger chatbot knowledge updates with a business change
A change to an offer or process should trigger a review of related knowledge. Do not wait for a customer to quote an outdated answer. Triggers include different service availability, a new contact route, a retired product or a revised delivery period. The person making the business change passes approved information to the knowledge owner rather than sending only a request to “update the AI”.
Record when the change takes effect. “From next month” becomes unclear within weeks, so use a specific date in the company record. If older conditions apply to earlier orders, explain that distinction instead of deleting useful process history entirely. The guide to a knowledge base and website FAQ covers collecting and editing content; here the focus is the transition between versions.
For a seasonal offer, prepare two events: its start and its end. Updating only at launch can leave the assistant proposing promotion conditions afterwards. Name the withdrawal owner and materials to review. Do not rely on the customer reading the expiry date in an old advertisement; active knowledge should represent the conditions currently available.
Name the fact owner and publication operator
The fact owner confirms what is true, while the publisher carries out the knowledge change. One employee may do both in a small business, but each responsibility should remain explicit. An administrator should not independently decide whether a new policy applies to orders already placed. They need the process owner’s decision before changing answers delivered to customers.
Write “The offer owner approves the information; the administrator completes publication and reports the result” in the change record. Include cover for absence when the change has a deadline. Do not send the entire process to an ownerless general queue. The guide to turning a support case into a task covers implementation work; creating a task does not itself make a fact current.
Find every source of the old statement
The old statement can remain in several active materials even when the main page is correct. Review FAQs, offer pages, files and instructions used to answer customers. Search for the exact period, name or condition being changed. Do not restrict the search to document names: “Customer information” may contain the same old deadline as the visible offer card.
Scroll the table sideways to see all columns.
| Item | Decision | Check |
|---|---|---|
| Fact change | New service scope effective on a defined date, approved by the offer owner. | Do not publish conflicting conditions without an explicit distinction. |
| Sources | Offer page, FAQ and an older document shared with customers. | Find all active locations containing the previous information. |
| Knowledge work | Edit or refresh material, followed by separate publication. | Saving a source does not prove a new generation is active. |
| Acceptance | Ask about the changed condition and inspect the source used. | After failure, establish which version remains active and who finishes the update. |
For every copy, choose update, replacement or withdrawal. If retaining different variants, make clear who and when they apply to.
For example, a previous promotion should not look like an offer for all new customers. The guide to selecting chatbot knowledge data covers source eligibility. Here, the priority is removing conflict between active versions of the same information.
Record a simple dependency map: “Consultation duration change: service page, FAQ, preparation document”. The next person can then locate the fact during another update. Avoid cataloging every page in the business; maintain the locations that actually contain the changing statement. This makes the record useful for the next action rather than creating documentation nobody can keep current.
Separate source edits from active knowledge
Editing a source prepares new material, while publication determines what answers use. Meet AI website and file sources do not refresh automatically; refreshing is a deliberate action. Do not assume new website copy has already reached the assistant. Inspect the source origin and correct update method before working on a document copy that may not control the active source. Changing a fact here means refreshing or replacing a source, not retraining the model; the guide to RAG or fine-tuning explains why. Before refreshing a website source, compare the sitemap with your exclusion list, because new site sections may need new rules, as described in the guide to exclusions when importing a website into the knowledge base.
Help Center articles follow a different path: publication synchronizes them into sources, and you edit their content in the Help Center. Source synchronization does not mean any website change has also been retrieved, or that knowledge publication can be skipped. Record the source type and the stage actually completed so “saved” cannot be mistaken for “active in answers”.
Publish and inspect the operation result
Publication needs acceptance after completion rather than after clicking start. Meet AI retains the previous generation until the new one succeeds fully, so failure or partial completion does not prove a switch. Inspect the result and record whether the change became active. If the operation failed, do not tell the team that AI answers already reflect the new condition.
In Meet AI, you can organize sources and inspect a private answer with citations. An account, active application and plan access are required; management actions need an authorized person. If unsafe information must be withdrawn, deliberately delete or unpublish its source instead of waiting for a routine update. Withdrawing the final source can leave the assistant without ready knowledge.
If the previous version must temporarily remain active, tell operators about the limitation and approved interim response. Do not invent a completion date. After publication succeeds, send a second short notice confirming the limitation has ended; the initial announcement alone is not enough to close the change record.
Close the change with confirmation for the team
Complete the update with a short notice: what changed, when it applies and which source is now authoritative. Operators should know the old file must no longer support replies. Ask about the revised fact and compare the citation with current material. If the assistant still cannot find the information, use the missing-match diagnosis rather than restarting imports without establishing the cause.
Microsoft documentation on editing knowledge sources shows that changes depend on source type. This record is our proposal; Meet AI publication rules come from the current product description, not Microsoft documentation.
The broader check of previously working questions belongs to chatbot regression testing after an update. Keep the acceptance outcome, owner and retired-version list in this change record. Schedule another review according to content risk: a seasonal offer needs a check when its promotion ends, while stable instructions need one after a product change. Avoid assigning every document the same review date without a reason.
Questions about knowledge updates
Does changing a webpage update Meet AI immediately? Do not assume that behavior.
Website and file sources need a deliberate refresh and knowledge requires separate publication. Help Center articles synchronize their source after publication, but that workflow does not promise automatic retrieval from every company page. Inspect the source type and the actual operation outcome.
What happens after publication fails? The previous generation stays active until the new one succeeds fully. Inspect the cause and finish the change rather than treating a saved file as publication. If the old information must no longer be used, make a deliberate withdrawal decision for the relevant source and explain the consequences to the team.
Is editing an operator answer enough? A message edit handles one conversation but does not change material used for future suggestions. Notify the knowledge owner about the wrong fact and carry out the appropriate source update. A confirmed knowledge change addresses the cause rather than only correcting its effect in a single draft sent to one customer.
