HubSpot Chatbot: Connect an AI Agent with Chatbase

A HubSpot chatbot can qualify website visitors, collect support requests, or answer questions with AI. The setup depends on whether you want HubSpot’s rule-based chatbot builder, its Breeze Customer Agent, or an external agent connected to your support team.

With Chatbase, you can answer questions using your support content and send issues that need a person into HubSpot as tickets. Your team keeps HubSpot for follow-up while you manage the AI agent’s knowledge and behavior in Chatbase.

TL;DR

• Use HubSpot’s chatbot builder for predefined questions, lead qualification and meeting or ticket flows.
• Consider HubSpot Customer Agent when you want native AI support within HubSpot. It requires an eligible subscription and HubSpot Credits.
• Connect Chatbase to HubSpot when you want a separately managed AI agent that sends unresolved requests to your HubSpot team. The connector creates a ticket and associates a contact.
• Plan for ticket follow-up. Chatbase’s HubSpot escalation sends an AI-written summary. It does not provide live takeover inside HubSpot’s chat widget.

Which HubSpot chatbot setup do you need?

Choose the setup based on where you want to manage AI answers and where your team will take over.

If you need a native scripted bot, use HubSpot’s rule-based chatbot instructions. Connect a chat channel, choose a template, build the flow, and set its targeting. External websites also need HubSpot’s tracking code for that widget to appear.

If you want to configure AI and human support within HubSpot, start by evaluating Customer Agent. Choose Chatbase when you want to manage the agent’s knowledge and behavior separately while keeping human ticket follow-up in HubSpot. Both can use public website content.

What the Chatbase HubSpot integration does

The connection lets a Chatbase agent create a HubSpot support ticket when a request needs human attention. The ticket includes customer information and an AI-written conversation summary.

When a ticket is created, Chatbase finds or creates the customer’s HubSpot contact and links it to the ticket. Your support team has the customer record alongside the request.

This setup fits teams that want AI to answer documented questions while keeping human follow-up in HubSpot. For example, an agent could explain your billing policy, then escalate a disputed charge for investigation.

Tell customers what happens after escalation: your team receives a ticket and follows up. If they need someone to join the chat immediately, use the separate live chat workflow in Chatbase’s Helpdesk.

How to connect Chatbase to HubSpot

You need a Chatbase agent, a paid plan with the required integration enabled, and permission to install apps in your HubSpot account. The HubSpot integration guide documents the connection.

1. Add the content your agent should answer from

Prepare current help articles, product documentation, and policies. In Chatbase, you can add website URLs, files, text snippets, Q&A entries, and Notion pages as knowledge sources.

A full website crawl may bring in old announcements alongside current policies. Start with the support URLs you trust, then check their sync status and review the agent’s answers.

For a SaaS support agent, useful starting material might include:

• Account setup and password reset instructions.
• Billing, cancellation, and refund policies.
• Troubleshooting steps for common errors.
• Limits that require a support representative to approve an exception.

For questions about an individual refund or invoice, you’ll need a separate connection to the system holding that record. Keep those requests on the escalation path until that access is configured.

2. Authorize the HubSpot connection

Open your agent’s Integrations tab, find HubSpot, and select Connect. Review the requested permissions in HubSpot and approve the app. Back in Chatbase, confirm the status is Connected.

Use the HubSpot account where your support team should receive requests. If you manage several portals, confirm the destination before continuing.

3. Add the ticket escalation action

Go to Build → Actions → Create action → Escalations, then choose the ticket action and HubSpot as the destination.

In the action’s instructions, specify when to create a ticket. Start with customers asking for a person and questions the agent cannot answer; for unanswered questions, have it confirm that the customer wants support to follow up.

Choose the channels where the action should be available in the Escalations settings. Save and enable it. For HubSpot, the ticket includes customer details and a summary; form fields and tags available for Chatbase Helpdesk have separate settings.

4. Check the customer-to-ticket path

Ask the agent for human help, then inspect the resulting HubSpot ticket. Verify the associated contact, summary, and destination queue. Have a support representative confirm how they will reply to the customer.

Have the representative read the summary without opening the original chat. Can they tell what happened and what the customer already tried? If they need to ask for the same details again, revise the instructions before launch.

5. Add the agent to your website

Use Chatbase’s Channels → Chat bubble setup to obtain the embed script, then install it through your website or CMS. The agent setup documentation covers deployment.

If your site already displays HubSpot chat, decide which pages should show each widget. Two chat launchers on the same page can leave visitors unsure where to ask for help.

Create your Chatbase agent, add your help content, and connect HubSpot to check the escalation flow with your team.

Example: send a billing issue to your HubSpot team

A customer asks, “Why was I charged after cancelling?”

The agent can explain the cancellation policy from approved content. If the customer disputes the charge, the conversation needs account investigation. Have the agent offer to send the request to support so someone can check the charge.

An example summary for the support team might read:

Customer reports a charge after cancelling. They say they cancelled on September 28 and were charged on October 1. They reviewed the cancellation policy but still dispute the charge. Support needs to check the cancellation record and invoice.

After creating the ticket, the agent should tell the customer that support will follow up. Include your team’s response time if you have one.

How much does a HubSpot chatbot cost?

HubSpot’s basic chatbot builder is available with free tools, while advanced features require paid editions. Customer Agent has a separate consumption model.

As of October 2, 2026, HubSpot’s catalog lists 50 credits per resolved text conversation. At its published $0.01 per additional credit, that equals $0.50 per resolution before included credits and subscription costs. For example, 1,000 billable text resolutions use 50,000 credits, equivalent to $500 if all credits are purchased at that rate.

HubSpot evaluates reply-based resolutions over a 72-hour window. Qualifying visitor-initiated handoffs affect whether a conversation counts as resolved. Use the current Customer Agent documentation when estimating usage.

Chatbase’s pricing uses message credits on its published plans. Standard is $150 per month with monthly billing, with 4,000 message credits. The HubSpot marketplace listing identifies Standard as the required subscription; confirm availability in your account before purchase. Enterprise offers custom limits and flexible billing.

To estimate Chatbase costs, use your expected message volume and model usage. For Customer Agent, use billable resolutions and available HubSpot Credits. Include the HubSpot subscription and seats your human team needs in either budget.

Keep the answers accurate after launch

Assign someone to maintain the content the agent uses. When a policy changes, update the source and confirm the revised answer before letting the agent explain it to customers.

Review conversations where customers ask again, challenge an answer, or request a person. These can reveal missing documentation, unclear wording, or issues that should escalate earlier.

Start with a manageable set of documented questions. Track whether customers get an answer they can use and whether escalated tickets give your team enough information to act. Include answer quality and useful escalation details when you evaluate your customer support workflow.

FAQs

Does HubSpot have an AI chatbot?

Yes. HubSpot Customer Agent, powered by Breeze, provides AI support. HubSpot also has a rule-based chatbot builder for predefined flows.

Can Chatbase create HubSpot tickets?

Yes. Connect HubSpot and configure the ticket escalation action. It sends a conversation summary and associates the customer’s contact with the ticket for human follow-up.

Can I use my existing knowledge base?

You can add accessible support URLs or supported documents to Chatbase. Review which pages were successfully processed. Connecting HubSpot for escalation does not itself import your knowledge base or all CRM records.

Can the same connection send sales leads into HubSpot?

Sales lead syncing needs a separate workflow. You can use Chatbase’s Zapier integration to trigger an automation when a lead is collected, then configure the HubSpot destination and field mapping. The ticket connector associates contacts with support requests.

Build a Chatbase agent for your HubSpot support team

If your team wants to keep human support in HubSpot, start with one documented support topic and one escalation path. Give the agent approved answers, then confirm your team can pick up the ticket and contact the customer.

Need help planning the rollout across brands or support channels? Book a demo to discuss your HubSpot escalation workflow, access requirements, and expected volume with the Chatbase team.