ChatSpot moved into HubSpot in September 2024. HubSpot then introduced Breeze Copilot, and the current assistant is called Breeze Assistant. If an old bookmark, article, or procedure tells you to sign up at ChatSpot.ai, replace those steps with the current HubSpot process.
The practical change is straightforward: you now work with the assistant inside HubSpot, where its output can reflect the CRM records, permissions, files, and connected tools available to your account. That added context can make the assistant more useful, but it does not remove the need to verify facts, protect sensitive information, and review work before you act on it.
The short answer
ChatSpot was HubSpot's early conversational AI experience. The public alpha launched in 2023. HubSpot announced ChatSpot's move into HubSpot in September 2024 and introduced Breeze Copilot later that month. Its current documentation calls the product Breeze Assistant.
The 2024 announcement said the standalone ChatSpot.ai application would retire. Teams that used ChatSpot should update their documentation and test old prompt workflows in Breeze Assistant instead of assuming every feature, instruction, or interface carried forward unchanged.
ChatSpot to Breeze Assistant timeline
| Stage | What HubSpot documented | What it means for your team |
|---|---|---|
| ChatSpot public alpha in 2023 | HubSpot introduced a conversational AI tool connected to its CRM ecosystem. | Early articles and screenshots may describe an experimental product. |
| ChatSpot moved into HubSpot in September 2024 | HubSpot said ChatSpot would become a HubSpot feature and that the standalone ChatSpot.ai site would retire. | A HubSpot account became the working home for the assistant. |
| Breeze Copilot launched in September 2024 | HubSpot placed the conversational assistant within the broader Breeze product family. | The assistant became part of HubSpot's platform-wide AI positioning. |
| Breeze Assistant today | Current HubSpot documentation describes Breeze Assistant as its conversational AI assistant. | Use current permissions, settings, and product documentation when building workflows. |
This timeline helps you interpret articles that still use the ChatSpot name. The older name can help you find historical context, but it should not be treated as the name of a separate current product.
What changed when ChatSpot moved into HubSpot
The assistant now works where your CRM work happens
Breeze Assistant opens within HubSpot. Its documentation covers content generation, record summaries, meeting preparation, and supported account tasks. Check the requirements for the specific action you want to use.
HubSpot currently labels third-party app connections for Breeze Assistant as beta. Only supported apps can connect, each has its own actions, and you need an account for that app. Do not assume that any integration installed in your CRM automatically works with the assistant.
Start with one task in your existing workflow. A sales representative can ask for context before a meeting. A marketer can draft or refine content. A service team member can summarize a record or review account information. Each use case still needs a clear prompt and a human owner.
CRM context and permissions matter
An assistant that works inside a CRM should not be treated like a public search box. HubSpot's AI settings documentation explains the controls for assistant access and CRM, conversation, and file data. Super Admins manage those settings.
Before a team adopts Breeze Assistant broadly, confirm:
- User access. Confirm who can use the assistant.
- Record scope. Review the records and tools available to each user.
- Connected accounts. Check which supported applications are connected.
- Prompt boundaries. Define what information is appropriate to share.
- Human review. Specify which outputs or actions need approval.
These checks belong in your broader HubSpot operations process, not in an informal prompt list that nobody maintains.
Old ChatSpot instructions can be misleading
An old ChatSpot guide may point to a retired URL, show controls that have changed, or describe a feature that now has different access requirements. Even if the underlying business task is still relevant, the steps may no longer be accurate.
Treat old ChatSpot material as migration input. Keep the useful intent, then rebuild the procedure around current Breeze Assistant documentation and your present HubSpot configuration.
What Breeze Assistant can help with now
Current HubSpot documentation describes several practical categories of work. Availability varies, so the right question is not whether the assistant can do everything. The right question is whether a supported task saves time without weakening control or accuracy.
Prepare for a meeting
When the required calendar and CRM context are connected, Breeze Assistant can help prepare for an upcoming meeting. A useful workflow might ask for the recent record history, open items, and questions that need resolution. The person leading the meeting should still review the underlying record before relying on the summary.
Summarize CRM records and account data
HubSpot documents summaries for contact, company, deal, and ticket records. Data settings affect this feature, and Sensitive Data can limit which activities are summarized. Compare the result with the source record whenever a decision depends on exact details.
Draft and refine content
Breeze Assistant supports content work, and HubSpot also documents generation and refinement in its content editors. You should supply the audience, purpose, evidence, tone, and required call to action. Every factual claim should be checked before publication, especially pricing, product capability, legal, medical, financial, certification, and performance statements.
We recommend connecting this work to a documented AI and automation approach rather than a collection of disconnected prompts.
Answer product and process questions
HubSpot says the assistant can use HubSpot learning resources and account context for supported questions. That can help a user find a starting point, but current official documentation remains the stronger source for a feature, permission, or subscription decision.
A safe migration checklist for old ChatSpot workflows
If your organization used ChatSpot, do not begin by copying every old prompt into Breeze Assistant. Begin with the business process that the prompt was meant to support.
1. Inventory old materials
Collect ChatSpot bookmarks, saved prompts, internal guides, training videos, screenshots, and workflow notes. Record the owner and purpose of each item.
2. Separate the goal from the old interface
Rewrite each item as a business task. For example, "open ChatSpot and create a prospecting email" becomes "draft a prospecting email using approved account context and messaging rules."
This prevents an obsolete interface from defining the new process.
3. Map the task to current Breeze Assistant capabilities
Check current HubSpot documentation, your subscription, account settings, and user permissions. Some tasks may work directly. Others may require a connected calendar, application, project, or product tier.
4. Test with safe records and sample inputs
Use a controlled record or non-sensitive example first. Confirm what information the assistant uses, what it omits, and whether its output follows your instructions.
5. Define a human review point
Name the person responsible for approving the result. Review is especially important before creating or changing CRM records, sending external communication, publishing content, generating quotes, or making decisions from a summary.
6. Document the current process
Replace the old ChatSpot guide with a short procedure that includes the prompt, required context, permissions, expected output, review rule, and fallback when the assistant cannot complete the task.
7. Review the process on a schedule
AI product names, interfaces, access rules, and capabilities change. Add an owner and review date to each procedure so that another product transition does not leave the team working from obsolete instructions.
Where Breeze Assistant fits in a HubSpot program
Breeze Assistant can support work across marketing, sales, service, and CRM administration. It is most useful when the surrounding data and operating process are already clear.
If records are incomplete, permissions are too broad, naming rules are inconsistent, or nobody owns quality review, an assistant can reproduce those problems more quickly. Start with CRM structure and governance, then add AI to specific tasks with measurable inputs and review points.
That sequence is part of a sound HubSpot onboarding and training plan. It also gives revenue teams a clearer connection between AI assistance and RevOps responsibilities.
Questions to ask before adopting Breeze Assistant
Use these questions to decide whether a workflow is ready:
- Purpose. What business task are you trying to complete?
- Context. Which records or connected tools provide the required information?
- Permissions. Does the user have the right access for the task?
- Data boundaries. What information should never be included in the prompt?
- Evidence. Which statements or actions need source verification?
- Ownership. Who reviews the result before it affects a customer, prospect, or record?
- Fallback. What happens when the assistant cannot complete the request accurately?
- Measurement. How will you compare the time taken and consistency with your existing process?
If the team cannot answer those questions, the workflow needs more definition before broader use.
Frequently asked questions
Does ChatSpot still exist?
Not as the former standalone application. HubSpot announced in September 2024 that ChatSpot was moving into HubSpot and that the standalone site would retire. The current conversational AI product is Breeze Assistant.
Is Breeze Assistant the same as ChatSpot?
Breeze Assistant is the current product in the transition that began with ChatSpot, but teams should not assume the interface, access rules, or capabilities are identical to the 2023 product. Use current HubSpot documentation for present behavior.
Do I need a HubSpot account to use Breeze Assistant?
Yes. Breeze Assistant works inside HubSpot. Access must be enabled, and the actions available to a user depend on account settings, permissions, subscriptions, and connected tools.
Can Breeze Assistant update CRM records?
HubSpot documents supported record and task actions, but availability depends on permissions and product configuration. Test the exact action in your account and keep human review in place before changing important data.
Is Breeze Assistant included with every HubSpot subscription?
HubSpot lists the assistant itself across its product plans, while noting that some features require additional subscriptions. Check the current requirement for the specific action you want to use rather than treating general assistant access as entitlement to every AI feature.
Should we delete our old ChatSpot prompts?
Do not delete them before reviewing their business purpose. Archive the original material, map useful tasks to current Breeze Assistant capabilities, and replace obsolete instructions with a controlled process.
Build a current HubSpot AI workflow
The name change is the easy part. The important work is connecting a useful task to reliable CRM data, current permissions, a clear prompt, and human review.
If your team needs help replacing outdated ChatSpot procedures or building a governed Breeze Assistant workflow, talk with Selworthy. We can review the process within the context of your HubSpot setup without assuming that every AI feature belongs in every workflow.
Source notes
Checked September 7, 2026. The linked HubSpot announcements establish the historical timeline; current Knowledge Base articles establish present requirements. Our migration checklist and review questions are process recommendations, not a claim that HubSpot enforces your internal approval policy.
