What This Update Actually Is
HubSpot shipped a knowledge generation engine inside Customer Agent setup. It reads your resolved, human-responded support tickets, groups them into topic clusters, and writes a short Q&A answer for each cluster.
The output lands in a review queue. You accept, edit, or decline each Q&A pair individually. Approved items become Markdown knowledge sources and go live immediately inside Customer Agent. Nothing is published without your sign-off.
Two guardrails are built in from the start. First, only tickets where a human responded are used, so AI-only or bot-deflected conversations don't pollute the source data. Second, personally identifiable information is scrubbed automatically before any content reaches the review screen.
Why HubSpot Shipped This
Here's the problem we see constantly across portals: a company decides to deploy an AI support agent, opens the knowledge base setup screen, and freezes. The blank page is brutal. Writing quality articles from scratch takes weeks of effort that most teams simply don't have.
The internal frustration runs deeper than just time. Humans who've been answering support tickets for years know the answers cold. But translating that institutional knowledge into structured articles feels like a different job entirely. It often never gets done.
HubSpot's answer: your ticket history already contains the knowledge. This feature surfaces it instead of asking you to recreate it. New portals especially benefit because they can have a working, populated Customer Agent without authoring a single article manually.
How to Use It Step by Step
- Open Customer Agent setup and navigate to the Knowledge section.
- Click "Add content" and select "Generate Knowledge" from the options.
- Choose your ticket scope: all resolved tickets or a specific filtered subset. Only human-responded tickets are eligible.
- Optionally add topic guardrails to include or exclude specific subjects. If you've already got an active Customer Agent, you can connect it so the engine skips topics it already covers.
- Kick off the generation job. You'll get a notification when it's done, typically within 5 to 10 minutes depending on ticket volume. You can leave the page and come back.
- Review results organized by theme. Accept, edit, or decline each Q&A pair one at a time.
- Approved pairs import as Markdown knowledge sources and go live in Customer Agent immediately.
One important limit: you can only run one generation job at a time. Plan your scope accordingly, especially if you're segmenting by product line or department.
What It Touches in Your HubSpot Strategy
This update sits at the intersection of Service Hub, Breeze AI, and your CRM data. Understanding the ripple effects helps you use it without creating technical debt.
On the knowledge base side, generated articles become Markdown files inside your knowledge sources. If you're already managing articles programmatically, these files will coexist with your existing content pipeline without conflict.
Key Takeaway
Generated knowledge sources are Markdown files. If your team uses the Knowledge Base API to manage articles programmatically, audit your pipeline before you start bulk-approving generated content so nothing overwrites existing articles.
On the workflow and routing side, this feature doesn't change how conversations get to Customer Agent, but it does change how capable the agent is when it handles them. A well-populated knowledge base directly reduces escalation rates. That means fewer tickets hitting your inbox routing and assignment workflows downstream.
On the data and reporting side, watch your ticket deflection metrics after you import the first batch of generated knowledge. Customer Agent's resolution rate is the clearest signal that the new content is working. Set a 30-day benchmark before the import, then compare.
On the CRM side, the source data is your ticket records. That means ticket property hygiene matters here more than it ever did for basic reporting. If your resolved tickets have inconsistent pipeline stages, missing subject lines, or mixed bot and human responses not properly tagged, your generation results will reflect that messiness.
Key Takeaway
Clean ticket data produces clean generated knowledge. Before you run your first generation job, confirm that your resolved tickets are properly tagged as human-responded and that your ticket subjects are descriptive. Garbage in, garbage out applies here just like anywhere else in the CRM.
On the AI strategy side, this feature pairs naturally with the broader Breeze ecosystem. Humans interacting with Customer Agent get faster, more accurate deflection when the knowledge base reflects real conversation patterns instead of marketing-approved boilerplate. That's a meaningful difference in experience quality.
Who Should Care Most
This update matters most to these specific situations:
- Service Hub admins deploying Customer Agent for the first time who need a knowledge base without starting from a blank page.
- Customer success and support managers who know their team answers the same 20 questions repeatedly but have never had time to document them.
- RevOps leaders who want to reduce first-response time and escalation rates without adding headcount.
- Growing companies on Professional or Enterprise tiers across any covered Hub who have 6 months or more of resolved ticket history sitting unused.
- Portal administrators migrating from a legacy help desk who want to carry institutional support knowledge into HubSpot without a manual rewrite project.
If you're on Starter or Free, Customer Agent isn't available yet for your tier. This one requires Professional or Enterprise on any of the covered Hubs.
George's Take
I've sat in enough portal audits to know that the knowledge base is almost always the most neglected tool in Service Hub. Not because teams don't care, but because writing from scratch feels like a separate content job stacked on top of an already full support workload. This feature flips that equation. Your resolved tickets are a living record of what your customers actually need to know. HubSpot is finally treating that data like the asset it is. My caution: don't approve everything the engine generates without reading it. The review step isn't a formality. It's where your subject matter expertise keeps the AI honest.
“Your resolved tickets are a living record of what your customers actually need to know. HubSpot is finally treating that data like the asset it is.”
If you want help auditing your ticket data before you run your first generation job, or if you're setting up Customer Agent for the first time and want to do it right, that's exactly the kind of work we do at Sidekick. Book a strategy call and let's look at your portal together before September 30.
Frequently Asked Questions
What is HubSpot Customer Agent knowledge generation?
It's a feature inside Customer Agent setup that reads your resolved, human-responded support tickets, clusters them by topic, and generates draft FAQ-style Q&A pairs for your review. You approve, edit, or decline each item before anything goes live. PII is scrubbed automatically before you see any results.
Does HubSpot Customer Agent publish generated knowledge automatically?
No. Every generated Q&A pair goes through a human review queue first. You accept, edit, or decline each item individually. Only approved items are imported as knowledge sources and made live in Customer Agent. Nothing is published without your explicit sign-off.
Which HubSpot plans include Customer Agent knowledge generation?
Customer Agent is available on Professional and Enterprise tiers across Marketing Hub, Sales Hub, Service Hub, Content Hub, Data Hub, and HubSpot Smart CRM. It is not available on Free or Starter tiers. The knowledge generation feature is included as part of Customer Agent setup on all supported tiers.
How long does HubSpot Customer Agent take to generate knowledge from tickets?
Typically 5 to 10 minutes, depending on how many tickets you include in the job. You don't need to stay on the page. HubSpot will notify you when the results are ready. Note: only one generation job can run at a time, so plan your ticket scope in advance.
What ticket data does HubSpot use to generate knowledge?
Only resolved tickets where a human agent responded are used. Bot-only or AI-deflected conversations are excluded. You can choose all resolved tickets or a filtered subset, and you can add topic guardrails to include or exclude specific subjects. PII is scrubbed automatically from all source data before generation.
Can I use topic guardrails to control what knowledge HubSpot generates?
Yes. During setup you can specify topics to include or exclude from the generation job. You can also connect an existing Customer Agent so the engine skips topics it already has knowledge for, preventing duplicate or redundant content from cluttering your review queue.
