Companies that use Hubspot Breeze Customer Agent

What this captures, and what it doesn't

We believe in being transparent about how we collect our data and what its limitations are, unlike most other data providers who operate as black boxes.

This methodology captures companies actively running HubSpot Breeze Customer Agent on their public website. Unlike simply detecting Service Hub usage, this is a direct signal that the AI agent is live and deployed - the configuration fields we check are only present when Breeze Customer Agent has been explicitly enabled on a chatflow, not just when a portal has purchased the plan.

It does not capture a few important scenarios:

• Companies using Service Hub Professional or Enterprise without Breeze Customer Agent enabled. Many Service Hub customers use ticketing, knowledge bases, and help desk workflows without ever activating the AI agent on their chat widget. Those companies do not appear here.
• Companies using other Breeze AI products such as Breeze Prospecting Agent, Breeze Content Agent, or Breeze Social Agent. This dataset is specifically limited to the Customer Agent - the AI that handles inbound customer conversations on a website chat widget.
• Companies whose chat widget is not embedded directly in their website HTML. If the widget is loaded dynamically after user interaction, or only appears on certain pages we did not crawl, we may miss it entirely.
• Companies using Breeze Customer Agent only on internal or gated pages, not on their public-facing website. We only scan publicly accessible pages.

How we figured this out

We start with the same universe of roughly 3 million company domains, ranked by headcount as reported on their LinkedIn profiles. For each domain, we look for HubSpot's chat widget embedded in the page HTML, then query a public configuration endpoint that HubSpot exposes for every active chatflow.

Chat widget detection. HubSpot's chat widget is loaded inside an <iframe> with the ID hubspot-conversations-iframe. When we find this iframe in a page's HTML, we extract the portal ID and session token embedded in its source URL. These give us everything we need to query the chatflow configuration.

Chatflow configuration inspection. HubSpot exposes a public endpoint that returns the full configuration for any active chatflow, requiring no authentication:

https://api-[region].hubspot.com/livechat-public/v1/message/public?portalId=[id]&messagesUtk=[token]

This endpoint returns a JSON configuration object describing how the chat widget is set up for that portal. When Breeze Customer Agent is active, this configuration contains specific fields that are absent on standard chatflows. We look for three signals in the response:

• routingRuleDefinitionAI: true - indicates that conversations are being routed through HubSpot's AI engine rather than directly to a human agent or standard bot.
• recommendedQuestionsForAgent populated - a non-empty array of AI-generated suggested questions, which is a feature exclusive to Breeze Customer Agent.
• isResponderAI: true on any agent in the sendFrom array - indicates that a human agent profile is backed by Breeze AI, meaning the AI is responding on the agent's behalf.

Any one of these three signals firing is sufficient to confirm Breeze Customer Agent is active. The false positive rate is effectively zero - these fields are only populated when Breeze is genuinely deployed, not merely when a portal has purchased Service Hub.