A visitor asks your chat widget "do you have anything available this weekend" or "what's the cost for a first consultation," gets a good answer, and closes the tab. Most teams never see that conversation again — it's not a form fill, so it's not a lead, so nobody follows up. But look at what was actually asked. That's not idle browsing. That's someone closer to a decision than most of the contacts a marketing team pays to generate through ads.
The conversations you're already having, uncaptured
Without a CRM connection, an FAQ conversation is a transcript nobody reads, not a lead anyone works. The intent is real. It's just invisible to everyone except the person who had the conversation.
What AIVA sends to HubSpot
Connected to HubSpot, AIVA creates a contact the first time it identifies one — from a phone number, an email shared mid-conversation, or a detail the chat widget collects — and updates the record on every conversation after that. The contact carries what was actually discussed: which questions came up, whether pricing was one of them, whether an appointment got booked, whether the conversation ended in a clear next step or trailed off.
This isn't limited to the chat widget. A phone call that asks the same pricing question, or a text conversation that starts with someone confirming your hours, feeds the same contact record the same way. If a customer reaches out on two different channels in the same week, HubSpot shows one contact with both conversations attached, not two half-pictures sitting in different places.
That last part matters. A contact who asked about pricing twice and never booked is a different kind of lead than one who booked immediately, and HubSpot's lists and workflows can treat them differently, because the detail is actually there to filter on.
AIVA stops being a dead end and starts being a source — the same as a form fill or a demo request.
What triggers your existing workflows, and what doesn't
Because so much of HubSpot's value sits in workflows — sequences, lifecycle automation, lead scoring — it's worth being precise about where AIVA sits relative to all of that. Creating or updating a contact is a normal property write, visible to your workflows the same way any other update would be. If you've built a workflow that enrols a contact when lifecycle stage changes to a certain value, and AIVA's conversation causes that change, the workflow fires — AIVA doesn't need special integration with your automation to participate in it, because from HubSpot's side, it isn't a different kind of update.
What AIVA doesn't do is enrol a contact into anything on its own initiative. It writes the properties you've configured it to write — lifecycle stage, lead source, a conversation summary — and stops there. Whether that write should also trigger a specific sequence or notify a specific rep is a decision you make when connecting the properties, not a default AIVA assumes on your behalf. That matters because an automatic enrolment into the wrong sequence is a worse outcome than no enrolment at all — a contact who asked a routine hours question landing in a sales nurture sequence meant for people who requested a demo does more harm to that sequence's effectiveness than it helps.
Read access works the same way it does everywhere else in this integration: enough to match a conversation to an existing contact, using whatever field your instance already relies on, and nothing beyond that. Timing follows the same real-time pattern as everything else here — a property updates the moment a conversation resolves, not on a nightly import, so a workflow that's meant to fire within minutes of a lifecycle change actually can.
Matching a contact across channels
The matching itself relies on whatever identifying detail a conversation actually offers — the phone number a call comes from, an email a customer types into chat, a number a text arrives from. Where AIVA already has enough to recognise someone as a returning contact, it attaches the new conversation to the existing record instead of starting a new one. Where it doesn't — an anonymous chat visitor who never shares a way to reach them — no contact gets force-created; the transcript simply isn't attributable to anyone yet, the same way an anonymous website visit wouldn't be.
A concrete example
A home services business gets a chat message at 9 PM: "do you do same-day AC repair, and what's the callout fee." AIVA answers both, the visitor doesn't book on the spot, and closes the tab. Without HubSpot connected, that's the end of it. With it connected, a contact exists the next morning with that exact question attached — pricing-sensitive, same-day urgency, no booking yet. That's specific enough for a follow-up call to open with "I saw you were asking about same-day AC repair last night — still need that sorted?" instead of a generic outreach message.
When an anonymous visitor becomes identifiable
Earlier, on matching: an anonymous chat visitor who never shares a way to reach them doesn't get force-matched to a contact, because there's nothing to match against yet. The natural follow-up question is what happens when that same visitor later does identify themselves — say, they chat anonymously on a Monday asking about pricing, then call on Wednesday and give their name and number to book an appointment.
Those become two separate, disconnected events unless something links them — and that's the honest limit worth understanding rather than glossing over. AIVA can't retroactively attach Monday's anonymous chat to Wednesday's contact unless the two conversations share an identifying detail, like the same email typed into both, or the chat widget capturing a phone number partway through. Where that detail exists, the match happens the same way any other cross-channel match does, and the contact created on Wednesday carries both conversations. Where it doesn't — a genuinely anonymous browse-and-leave, followed by a booking from a different device entirely — the two simply stay separate, the same way they would if two different people happened to ask a similar question.
In practice this matters less than it might sound, because the conversations most worth capturing are the ones where a visitor engages enough to eventually identify themselves — and once they do, that's the record that carries forward. An anonymous conversation that never resolves into an identified contact wasn't going to be actionable either way; nobody could have followed up on it regardless of whether HubSpot logged it. If cross-device matching matters enough to your business to invest in — asking for an email early in every chat conversation, say — that's a setup decision worth making deliberately rather than assuming AIVA will reconcile identities it was never given a way to connect.
From transcript to pipeline
Once conversations land in HubSpot as contacts with real context, they flow into whatever your marketing and sales teams already do with a contact — lifecycle stage changes, segmentation, a nurture sequence for the ones who asked but didn't book. None of it requires rebuilding your HubSpot setup around AIVA.
Considerations before you connect
Worth deciding before going live: which properties AIVA should actually be allowed to write to, especially if your HubSpot instance already has other tools populating the same fields — you don't want AIVA's lead source overwriting one a paid campaign already set. It's also worth being deliberate about which new-contact events should trigger existing workflows; a contact created from a routine hours question probably shouldn't enter the same nurture sequence as one created from a pricing conversation that didn't convert.
Setting it up
Connect your HubSpot account, decide which properties AIVA should populate — lifecycle stage, lead source, conversation summary — and choose whether new contacts should trigger existing workflows. Most teams have it live within one setup session.
If your marketing team measures lead sources in HubSpot, this closes a common gap. See it next to other CRM integrations — Salesforce, Zoho, Pipedrive — in AIVA's other integrations, check pricing, or start free and connect HubSpot yourself.