When customer inquiry volume surges, support operations face a classic operational crunch: frontline agents spend hours answering repetitive inquiries—such as password resets, order tracking, returns, and subscription changes—while critical technical issues linger in the backlog. HubSpot Breeze Customer Agent (formerly Service Agent within Service Hub) addresses this bottleneck by autonomously parsing, answering, and resolving tickets using an organization's verified documentation, historical ticket records, and public resources.
Unlike rigid decision-tree bots that break when a user deviates from predetermined branching logic, Breeze Customer Agent leverages generative retrieval-augmented intelligence grounded in your company's actual data. This guide walks support managers, RevOps leads, and Service Hub administrators through configuring Breeze Customer Agent, mounting knowledge sources, mining historical tickets, and establishing foolproof escalation handoffs.
1. Prerequisites, Permissions, and the Billing Model
Before accessing the Customer Agent configuration panel, ensure your HubSpot portal meets the technical and administrative prerequisites:
- User Seats & Permissions: Creating, training, and deploying a Customer Agent requires an assigned paid Sales or Service seat, along with the Customer Agent editor user permission. Configuring ticket assignment rules and workflows during handoffs further requires Account Access or Super Admin permissions.
- Connected Support Channels: Your portal must have at least one active channel connected to the Help Desk or Conversations Inbox (such as Live Chat, Email, WhatsApp, Facebook Messenger, forms, or calling). If embedding chat on external web pages, verify that the HubSpot tracking script is installed.
- AI Settings & Data Access: Navigate to Settings > AI Settings and confirm that toggles are enabled for Generative AI tools, CRM data, Customer conversion data, and Files data.
- The HubSpot Credits Consumption Model: Breeze Customer Agent operates on HubSpot Credits when deployed to live channels.
- Resolution-Only Billing: Credits are deducted only when the agent delivers a confirmed resolution. A resolution occurs when the agent provides a verified content source or completes an action, and no customer-initiated handoff occurs within a 72-hour evaluation window.
- Assisted Mode (Zero Credit Cost): Support teams can also use the agent inside the Help Desk to generate Reply Recommendations for human reps. This assisted mode consumes zero HubSpot Credits.
- Trial Period: New accounts can activate a 14-day free trial where live customer agent resolutions incur no credit usage.
2. Initial Setup: Agent Identity and Brand Persona
A support agent’s tone sets customer expectations from the opening greeting. Configuring identity correctly ensures brand alignment and clarity.
- In your HubSpot account, navigate to Service > Customer Agent (accessible directly or under the More menu).
- Click Continue to agent setup.
- Name Your Agent: Assign a recognizable name (e.g., "Sprocket Support Assistant" or "Acme Virtual Specialist"). Customers will see this name accompanied by a Powered by AI badge in chat interfaces.
- Set the Personality: Select a conversational demeanor from five standard profiles:
- Friendly: Approachable and encouraging.
- Professional: Concise, structured, and formal.
- Casual: Relaxed, concise, and modern.
- Empathetic: Validating, gentle, and understanding—ideal for dispute-heavy or sensitive services.
- Witty: Lighthearted, suitable for direct-to-consumer lifestyle brands.
- Use My Brand Voice: If your marketing or service teams configured an AI Brand Voice profile in HubSpot, select this option to mirror your global corporate messaging guidelines.
- Multi-Brand Portals: If your enterprise utilizes HubSpot Brands, you can create dedicated customer agents for each brand unit, configuring separate knowledge bases, URLs, and handoff queues for each division.
3. Mounting Knowledge Sources: Articles, Public URLs, and Files
The accuracy of Breeze Customer Agent depends strictly on the quality and structure of its knowledge sources. It only generates answers backed by verifiable source materials.
Navigate to Train > Knowledge in the left sidebar and click Add content to attach knowledge inputs:
A. HubSpot Native Knowledge Base & Web Pages
- Click From HubSpot to select native assets.
- Check the boxes for your published Knowledge Base articles, Website pages, Landing pages, and Blog posts.
- Automatic Synchronization: Whenever an author publishes edits to a native HubSpot Knowledge Base article, the Customer Agent automatically re-syncs that article in real time.
B. Public External URLs and Subdomains
If documentation lives on Notion, Zendesk, GitBook, or a custom CMS:
- Click Import from public URLs, input the root URL, and click Add.
- Toggle Import related URLs on to automatically crawl up to 5,000 sub-pages.
- Define the crawl boundary under Which pages to import:
- All pages on this domain: Crawls across the main domain and all subdomains.
- Pages matching this path: Confines the crawler to a specific directory (e.g.,
docs.example.com/support/guides/). - This subdomain only: Restricts crawling strictly to a subdomain (e.g.,
help.example.com).
- Configure Path Filtering to explicitly include priority paths (e.g.,
/knowledge/,/faq/) and exclude extraneous sections (e.g.,/blog/,/careers/). - External URLs re-sync on a scheduled weekly cadence. You can manually force an update by selecting URLs and clicking Refresh, or permanently exclude outdated paths via Exclude from refresh.
C. File Uploads and Internal Documentation
- Select Upload a file to ingest product manuals, standard operating procedures (SOPs), or pricing tables.
- Supported formats include
.pdf,.docx,.csv,.txt,.json,.md,.pptx,.html, and.xml. - Citation Privacy Safeguards: When mounting proprietary files or private internal pages, support teams can toggle Citations off. The agent will synthesize and draw upon the technical facts to solve the user's issue, but will not provide direct links or expose document file names to the public customer.
D. Direct Q&A "Short Answers"
For deterministic questions that demand an exact, approved script (such as holiday shipping cutoffs, return windows, or exact SLA tier definitions), click Create a short answer. Enter the precise question and answer. You can embed hyperlinks and illustrative diagrams directly within the editor.
4. Mining Historical Support Tickets to Generate Knowledge
Rather than building hundreds of FAQ entries manually, support operations can leverage HubSpot's built-in Generate knowledge feature. This tool uses AI to scan closed tickets and extract proven, agent-tested solutions.
- Under Train > Knowledge, click Add content > Generate knowledge.
- Choose the data origin:
- Tickets: Select All tickets (which ingests closed tickets from the preceding 90 days) or select A specific ticket segment (e.g., tickets tagged with "Billing Inquiry" or "Tier 1 Resolved").
- Inbox: Select All inboxes or target a specific support inbox.
- File Upload: Upload batched transcript archives.
- Topic Guardrails: Toggle the Guardrails switch on.
- In the Include topics box, enter high-frequency ticket drivers (e.g., "Account Lockouts", "Invoice Generation", "License Allocation").
- In the Exclude topics box, enter subjects unsuitable for autonomous answers (e.g., "Executive Escalations", "Enterprise SLA Breaches", "Custom Contract Terms").
- Click Generate knowledge.
- Review and Approve Drafts:
- Processing takes several minutes. Once complete, click Review drafts in the notification banner.
- HubSpot clusters findings into structured topic cards displaying proposed Question & Answer pairs.
- Click into any Q&A card to edit the generated response, refine terminology, or insert relevant links.
- Click Accept to immediately convert the pair into an active knowledge source, Skip to defer, or Decline to discard.
5. Setting Communication Guidelines and Behavioral Boundaries
Guardrails prevent hallucinations and keep the AI strictly within support scope:
- Navigate to Train > Guidelines.
- Communication Style: Click + Add Communication style. Name the rule and attach it either globally or to specific contact segments (such as VIP clients versus Free tier users). Define formatting preferences (e.g., "Always structure troubleshooting steps in numbered lists; maintain concise answers under 120 words; do not speculate on unreleased roadmap features").
- Guardrails (Restricted Topics): Under the Guardrails block, explicitly declare topics the agent must never discuss. For example, if a user asks about legal disputes, competitor comparisons, or unannounced discounts, instruct the agent: "Inform the customer politely that this topic requires specialized review, and initiate a human handoff immediately."
- Custom Instructions: Provide contextual guidance for edge cases, such as handling emotionally frustrated customers with de-escalation validation before executing an agent transfer.
- Click Test in the upper-right corner to simulate customer inputs, then click Publish.
6. Configuring Ticket Escalation and Human Handoff Rules
An autonomous agent is only as safe as its handoff mechanics. When a customer reaches the agent's boundaries, the transfer to a human support engineer must be immediate, context-rich, and orderly.
Handoff Triggers
Navigate to Train > Human handoff. The Customer Agent triggers a transfer under three default conditions:
- Low Confidence: The agent cannot locate an answer in synced knowledge sources.
- Explicit Request: The customer types "agent", "human", "representative", or "support team".
- Paused State: The agent has been manually paused or credit allotments are exhausted.
To add custom business triggers, locate the Handoff guidelines field. Use declarative syntax or prebuilt templates:
"When the customer requests to speak with a human or uses any of the following triggers, you must immediately initiate a handoff: 'Cancel subscription', 'Issue refund', 'Security vulnerability', 'System down', 'Talk to billing'."
Configuring the Transfer Pipeline
Click Edit handoff process and choose the handoff execution style:
- Live handoff to a human agent: Routes the session directly to an active agent currently logged in and marked as available.
- Async handoff to a human agent: Informs the user that the inquiry has been queued for email or ticket follow-up by the team.
- Don't handoff to anyone: Keeps the agent in the loop, used strictly in fully automated, no-agent channels.
Routing Destinations: Direct vs. Workflow Rules
- Uniform Assignment: Select I want to hand off all issues to the same users or teams. Pick the destination Help Desk or Inbox, and designate specific users or rotating teams. Only users with assigned Sales or Service Seats can receive routed tickets.
- Conditional Workflow Assignment: Select I want to hand off issues to different users or teams based on a set of conditions.
- For Help Desk channels, assign a Ticket-based workflow.
- For Inbox channels, assign a Conversation-based workflow.
- HubSpot provides a dedicated workflow template: Reassign Tickets for Customer Agent Handoff. This automation reads ticket origin properties, contact tier, and inquiry intent to assign tickets to specialized technical pods, apply SLA timers, and set ticket priority.
Understanding Ticket Status Progression
During handoff, HubSpot automatically updates the CRM property Customer Agent ticket status:
| Status Value | System State | Operational Action Required |
|---|---|---|
| Pending | Agent is actively conversing with the customer; no handoff triggered. | Reps do not need to intervene. |
| Awaiting Human Assignment | Handoff triggered; ticket moved to Help Desk, but awaiting an available rep or workflow assignment. | Monitor queue; reps can manually claim unassigned tickets. |
| Handed off | Ticket successfully transferred and assigned to an active human representative. | Human rep takes ownership; reviews AI conversation history. |
Availability and Messaging
- User Availability Awareness: Breeze Customer Agent routes live chats based on individual user working hours and status in Help Desk, rather than general chat widget schedules.
- Fallback Handling: If no rep is available during a live handoff request, configure the agent's behavior: select whether to keep the chat open in the Unassigned queue or transition to an asynchronous ticket creation prompt.
- Custom Handoff Messages: Customize the exact prompts displayed during normal hours and off-hours (e.g., "I'm transferring you to our technical support team now..."). HubSpot automatically translates these messages into the visitor's native language.
7. Pre-Deployment Testing and Phased Rollout
Never deploy an AI agent to 100% of live traffic on day one. Validate accuracy and operational guardrails through structured testing.
1. Interactive Preview and Testing Insights
- Click Test [Agent Name] in the top right.
- Toggle between Live Chat and Email previews.
- Click the Unknown contact dropdown and choose Test as CRM contact or Test as a segment to simulate how the agent personalizes responses using contact and company CRM tokens.
- Click the Enlarge icon to inspect Testing Insights. This reveals the AI's internal reasoning: which knowledge base article was referenced, which guidelines took effect, and which handoff rules were evaluated.
- Use the Coach your agent drawer to immediately adjust knowledge gaps or tighten guidelines.
2. Batch Testing
Run automated batch evaluations by feeding historical inquiries to the agent at scale. Review automated deflection scores, citation accuracy, and flag hallucinations before launching.
3. Deploying to Support Channels with Traffic Throttling
- Navigate to Deploy > Channels and click Deploy agent.
- Select your target channel (e.g., Website Live Chat or Support Email).
- Set Working Hours: Choose All hours, During specific hours, or Only outside specific hours (ideal if using the agent solely for overnight deflection).
- Conversation Coverage Percentage: Enter a conservative coverage threshold (e.g., start at 15% to 25%). HubSpot randomly routes that proportion of incoming sessions to Breeze, letting the remainder flow to standard human queues.
- For email channels, filter by Contact lists to include / exclude to test on non-critical customer segments first.
- Click Deploy.
8. Post-Launch Monitoring and Knowledge Gap Iteration
After deployment, review operational dashboards under Service > Customer Agent > Analyze:
- Deflection & Resolution Rate: Track the percentage of incoming tickets resolved end-to-end without a customer-initiated handoff within 72 hours.
- Knowledge Gaps: HubSpot highlights unanswered queries where the agent lacked reference documentation. Use this report as a content roadmap to write targeted Help Desk knowledge base articles.
- Top Cited Sources: Identify your most impactful documentation and audit articles for accuracy when product updates ship.
- Credit Utilization: Monitor credit consumption under Account & Billing > Usage & Limits. If revisions are underway, toggle the agent switch off in usage settings to pause consumption without losing your configuration.
By systematically curating knowledge sources, mining historical tickets, enforcing strict guardrails, and linking escalation rules to Service Hub workflows, support teams transform high-volume ticket surges from a frontline crisis into a scalable, high-satisfaction resolution engine.