When it acts
- User starts chat in customer portal
- Contact update in CRM
Connect HubSpot and answer with the plan they actually bought
Connect HubSpot so Intake knows the user’s plan, company, or sales stage before answering. Log finished activity back to the CRM to keep track.
What it solves
Answering while knowing who you are talking to
The same question has different answers depending on the plan the person asking is on, and that lives in HubSpot, not the help center. The agent looks it up before replying, so it does not say "it depends on your plan": it says what that company plan includes.
What it solves
Sales hears what happens in support
An account asking three times about their plan limits is saying something, and that signal usually never leaves the support inbox. With HubSpot connected, what happens in the conversation lands on the customer record, where their owner sees it without anyone telling them.
What it solves
Commercial questions go to the right person
Not everything arriving through support is support: pricing, renewal and upgrade questions lose value when the wrong team answers them. The agent recognises them and routes them to that account owner in HubSpot, with what has already been discussed.
What it does
What the connection triggers and what the agent does with it
An integration is not useful for being on the list: it is useful for what it lets the agent do. This is what HubSpot puts on the table, and what the agent does with it without anyone watching.
What it can do
- Query company/lead properties
- Log activity or note in HubSpot
- Escalate to Account Executive
How HubSpot helps the agent resolve with context
Three concrete things that change the team day, not a feature list.
Data-driven decisions
Intake adjusts its answer or action depending on whether the user is a lead, an Enterprise customer, or at risk.
Commercial handoff
If a support question turns into a sales opportunity, it is escalated to your team with the HubSpot state.
Synced history
The actions Intake executes are automatically reflected in the HubSpot profile.
How it works
Three steps, and only the first needs a HubSpot admin. The rest you change later without reconnecting anything.
Authorise the connection
You open the integrations panel, pick HubSpot and authorise access with the account your team already uses. You need to be an admin in HubSpot, so if you are not, this is the only step you will have to ask someone for.
You choose what the agent sees
You tick the channels, events and account fields it can reach. What you do not tick does not exist for it, and you can change that whenever you want without reconnecting anything.
It answers with that context
From the first conversation the agent looks that data up before replying, resolves what it can close on its own and passes to a person what it cannot, with the case already assembled.
Frequently asked questions
How long does connecting HubSpot take?
Minutes, not an afternoon. You authorise access and choose what it can see; nothing needs rewriting and no development work is needed to start.
Can I revoke access later?
Yes, and from either side: revoking the connection in Intake or withdrawing the permission from HubSpot. The agent stops reading that data immediately and keeps answering with the rest.
Does using HubSpot cost extra?
No. Every integration sits inside the per-resolved-conversation price: 0.41 EUR on annual billing. There is no add-on to buy and no call meter.
What happens if HubSpot stops responding?
The agent answers with what it does have and, if the question depended on that data, hands off to a person explaining why. It never invents the value it could not look up.
What HubSpot data does Intake read?
Company properties, contact status, account owners, and custom fields you authorize.
Does Intake write data to HubSpot?
Yes, it can sync resolutions as notes or log attribute changes if you grant write permissions.
