Your support team changes an onboarding step on Monday. On Tuesday, the customer agent confidently explains the old process. The answer is clear, polite, and wrong.
Before rewriting the agent's instructions, check the information it can use. An outdated guide can turn a perfectly ordinary question into an avoidable support conversation.
Keeping a HubSpot customer agent useful requires a small content maintenance process: decide which sources it should trust, update them when the business changes, and check the answers afterward.
Choose sources that answer today's questions
Start with the questions customers actually ask. For each one, identify the page or document your support team would use to answer it now.
A current setup guide is a better candidate than a launch announcement describing what the product was expected to do. A support article should explain the present process. A historical blog post may still be worth publishing without being appropriate support knowledge.
Build a short source register. This can be a shared worksheet; it does not need to become another application.
- Topic: The customer question or process the source covers.
- Location: The exact page or file the agent should use.
- Owner: The person who can confirm the information is correct.
- Review trigger: The business change that should prompt another check.
- Last verified: When someone checked the substance, not just whether the link opened.
Keep the initial scope small enough to maintain. Importing more material gives you more material to inspect. It does not settle disagreements between documents.
Resolve conflicting answers at the source
Suppose your knowledge base says onboarding starts after an intake form is complete, while a sales PDF says it starts immediately after purchase. Both documents may be readable. Neither a successful sync nor a friendlier tone resolves the contradiction.
Have the process owner determine the correct answer. Then update or retire the conflicting content and review whether it still belongs among the agent's sources.
Write exceptions explicitly. If enterprise customers follow a different process, name the conditions and the next step. Avoid expecting the agent to infer an unpublished rule from a vague sentence about personalized service.
A useful source answers one question directly, states when the answer applies, and points the customer to a clear action. “Contact us for more information” is sometimes appropriate. It should not be the entire operating manual.
Understand what a refresh does
HubSpot's knowledge source documentation, checked on November 10, 2026, says changes to synced knowledge base articles trigger automatic re-syncing. Other knowledge sources re-sync weekly. The source controls also include Refresh and Remove as source.
Plan urgent content changes around that distinction. If a support process changes today, do not treat the next routine refresh as your verification plan. Update the authoritative content, refresh the relevant source where appropriate, and confirm the resulting answer.
Also distinguish citation visibility from source selection. Turning off citations prevents the agent from citing that content. It is not the control for removing outdated information from the source set.
Use the native source management tools first. A custom synchronization service adds maintenance of its own. Build one only after identifying a requirement the available controls cannot meet.
Check sync failures before adjusting the answer
If an answer seems unaware of a recent update, check whether the source was successfully retrieved. HubSpot's source sync troubleshooting guide directs users to Service, Customer Agent, then Train and Knowledge, where the Failed tab lists affected sources and errors.
The documented causes include unavailable pages, rendering problems, and unexpected responses such as redirect issues. Check the specific error before changing content or agent instructions.
A page opening in your browser is useful evidence, but it does not establish that the agent ingested the current version. Your browser may have access or rendering capabilities that differ from the crawler's.
Give each failure a next action. The content owner can correct an outdated URL. A site administrator may need to investigate a loading problem. The person maintaining the agent should confirm the source works after the correction.
Keep confidential material under its intended access controls. A sync error is a reason to investigate the approved delivery method, not a reason to make an internal document public.
Retest the questions affected by the change
Keep a small set of questions with expected answers. These are your review examples, not a claim that a particular response is guaranteed.
For the onboarding example, test the basic question, an incomplete intake form, and the exception for a different service package. Include a question the content does not answer so you can check whether the response appropriately acknowledges the gap or follows your team's escalation process.
- Correctness: Does the answer match the current approved process?
- Applicability: Does it distinguish the relevant customer or product situation?
- Completeness: Does it include the condition that matters before the customer acts?
- Source: When a citation appears, does it lead to the intended supporting content?
- Next step: Can the customer tell what to do or who can help?
Save the question, observed answer, review date, and correction needed. Reuse those examples after related changes. A pleasant answer deserves a quick read; a consequential answer deserves a comparison with the source.
Make content review part of the business change
Assign source review to the work that changes the answer. A new service package should prompt a check of its support content. A revised intake process should prompt a check of onboarding guidance. A renamed feature should prompt a search for the old name.
Set a recurring review for sources that do not change predictably, and choose the interval according to how quickly the information becomes stale. Give the review an owner and a completion condition. “Everyone should keep an eye on it” is usually nobody's calendar event.
After launch, sample conversations that required correction or human follow-up. Decide whether each problem came from missing knowledge, conflicting content, failed synchronization, or an unclear question. Fix the cause you found rather than adding another paragraph to the agent's instructions by default.
Maintain the knowledge behind the agent
A customer agent needs a dependable source set and a way to notice when that set is no longer dependable. Start with a few valuable topics, clear ownership, and repeatable checks before expanding.
Our HubSpot Breeze agent configuration services cover planning and configuring agents around the work your team needs. If your customer agent keeps repeating yesterday's answer, talk with No Bounds Digital about the sources and maintenance process behind it.
