How to govern HubSpot AI (Breeze)
How to govern HubSpot Breeze: AI agents drafting outreach, summarising contacts and acting inside your marketing and sales pipeline.
HubSpot · Reviewed when the vendor ships a capability change or a customer declares the tool
How HubSpot AI (Breeze) is used
We see five common ways businesses use HubSpot AI (Breeze), and we govern each one on its own terms. If your team uses it differently, that is fine: you describe the use in your own words and Certrak works out the governance from what it actually does.
Marketing content creation
Consequence to people: LowDrafting marketing copy, social posts, ads, blog content
Customer communications drafting
Consequence to people: MediumDrafting customer emails, support replies, or other outbound communications - reviewed before sending
Sales lead scoring and prioritisation
Consequence to people: MediumRanking leads, suggesting next actions, prioritising sales effort
Customer segmentation and personalisation
Consequence to people: MediumGrouping customers for targeted treatment, personalisation, or recommendations
Customer-facing chatbot or automated support
Consequence to people: HighInteracting with customers directly, without a person reviewing each response
Governing HubSpot AI (Breeze) in practice
- Name one person who owns HubSpot AI (Breeze) in your business. Governance starts with a name.
- Write down what HubSpot AI (Breeze) is used for. Certrak recognises 5 common uses: Marketing content creation, Customer communications drafting, Sales lead scoring and prioritisation, Customer segmentation and personalisation and Customer-facing chatbot or automated support. Yours may differ; write down yours.
- Decide what HubSpot AI (Breeze) may and may not be given. Personal information is in scope for some uses; write the boundary down before it is needed.
- There is no human review of outputs. Decide whether that is acceptable for each use, and what would make you change it.
- HubSpot AI (Breeze) can send messages outside the business without a person approving. Record which of these you allow, and who can change that.
- Look at this again every month, and sooner on any of these: industry incidents, vendor model updates, autonomy level changes and data classification changes.