Customer Conversations That Automatically Update Your CRM

Every refund, support issue, and customer interaction handled by Hay flows directly into HubSpot. No manual logging required.

Your CRM should reflect what's actually happening with customers

You're using Hay to handle customer interactions: refund requests from your e-commerce site, support questions about your SaaS product, order tracking inquiries. Each of these interactions contains valuable information that should live in your CRM, but manually logging every conversation into HubSpot after it happens is tedious and inconsistent.

70%

Of customer interactions never get logged to CRM

3-5 min

To manually log each conversation after it ends

Incomplete

Picture when sales/support check HubSpot

Hay automatically syncs every customer interaction into HubSpot as it happens. Refund processed? Logged to the contact timeline with order details. Support issue escalated? Ticket created with full conversation context. Contact changed companies? HubSpot record updated immediately. Your CRM stays current without anyone manually entering data.

How HubSpot + Hay Works

AI that executes actions, not just answers questions

Automatic Activity Logging

Every customer conversation Hay handles gets logged in HubSpot. Support requests, refund inquiries, order issues appear on contact timelines automatically.

Contact Record Updates

Customer changed email? Updated shipping address? New company? Hay updates the HubSpot contact record in real-time during the conversation.

Deal Context Access

Hay pulls deal information from HubSpot to personalize responses. Know if customer is in trial, negotiation, or has active deals.

Support Issue Tracking

When Hay handles a support request, it creates or updates tickets in HubSpot. Full conversation history attached for your team.

Revenue Event Logging

Refunds processed, subscriptions cancelled, upgrades requested. Financial events flow into HubSpot with complete context.

Custom Property Updates

Update custom HubSpot properties based on conversation content. Tag customers mentioning competitors, feature requests, or churn signals.

Real Scenarios

1

Refund Request Logged to CRM

Customer:

"I'd like a refund for my last order"

Hay:

I can help with that. Let me check your order... Your order from January 3rd qualifies for a refund. I've processed €89.99 back to your card.

→ Processes refund via Stripe → Logs refund activity to HubSpot contact → Creates note with reason and order details → Tags contact with 'refund_requested'

Result: Sales team sees refund in HubSpot timeline. Revenue reports stay accurate. Customer tagged for follow-up analysis.

2

Support Issue Automatically Documented

Customer:

"The export feature isn't working for me"

Hay:

I see the issue. Let me escalate this to our product team. I've created ticket #4521 and they'll reach out within 4 hours.

→ Creates support ticket in HubSpot → Logs full conversation → Tags contact with 'product_issue' → Assigns to product team

Result: Product team has full context in HubSpot. Customer interaction documented. No manual ticket creation needed.

3

Contact Update During Conversation

Customer:

"I moved companies. My new email is [email protected]"

Hay:

Thanks for letting me know, Alex. I've updated your contact information with your new email and company.

→ Updates email field in HubSpot → Updates company association → Logs activity note about job change

Result: CRM stays current. Sales team sees job change. Marketing can adjust lead score based on new company.

"But what if the AI makes a mistake?"

Confidence System

CRM data is critical. Hay treats updates carefully with verification checks and configurable permissions:

  • 90%
    High confidence: Update automatically. Contact info changes, activity logging, ticket creation.
  • 70%
    Medium confidence: Enable supervision mode. You approve CRM updates before they're applied.
  • <70%
    Low confidence: Escalate immediately to human with CRM context gathered.

You control which fields Hay can update. Lock down revenue fields, allow contact info changes. Your CRM, your rules.

Why Teams Choose HubSpot + Hay

CRM That Stays Current

Every customer interaction Hay handles updates HubSpot automatically. No more manual logging after support calls or chat sessions.

Complete Customer Context

Sales sees all support issues. Support sees deal stages. Everyone works from the same current HubSpot data.

Revenue Tracking Accuracy

Refunds, cancellations, upgrades all logged in HubSpot. Your revenue reports reflect reality, not outdated assumptions.

Workflow Triggers

Use HubSpot workflows on Hay interactions. Customer requests refund? Trigger retention workflow. Mentions competitor? Alert sales.

Frequently Asked Questions

Which HubSpot objects does Hay update?

Hay can update Contacts, Companies, Deals, and Tickets. It logs activities to contact timelines and can create or update records based on customer interactions. You control exactly which objects and properties Hay can modify.

Can Hay create HubSpot tickets from support conversations?

Yes. When Hay escalates an issue to your human team, it can automatically create a HubSpot ticket with full context—the conversation history, customer details, and any actions already taken.

Does Hay work with custom HubSpot properties?

Yes. Hay reads and writes to custom properties. During setup, you map which customer data points should update which HubSpot fields. Custom properties are fully supported.

What HubSpot plan do I need?

Hay works with HubSpot Free CRM and all paid tiers. Some features (like custom objects or advanced workflows) depend on your HubSpot plan, but basic contact and activity syncing works on any tier.

Ready to automate HubSpot support?

Join our pilot program and start reducing repetitive tickets with AI that actually executes actions.