Integrations

HubSpot

How your agents look up contacts and deals in HubSpot during a conversation, and write qualified enquiries, outcomes and next steps back.

On this page

What the connection lets the agent do
How it connects
Permissions
In practice
What your team controls
Related

If your sales or service teams work in HubSpot, your agents work from it too. During a conversation, the agent recognises the contact, reads their deals and the records that matter to your business, and answers from that data. Afterwards, it writes back what happened and what should happen next, so your pipeline reflects every enquiry, including the ones that arrive at midnight.

HubSpot stays your system of record for customer and account data. The Telonic record is the system of record for conversation history.

What the connection lets the agent do

Action	What it means for you	Example
Look up records	The agent recognises the contact and reads their deals and history while the conversation is happening	A returning buyer's earlier enquiry
Write back the outcome	The summary, outcome and next steps are written to the contact	A note: "Budget confirmed. Wants a sea view. Viewing requested."
Create or update contacts and deals	New enquiries become contacts, and qualified interest becomes a deal in the right pipeline stage	A new deal for a two-bedroom apartment
Create tasks	Follow-up work is opened for your team, with the context attached	A callback task for the sales consultant
Update fields you permit	Named properties are kept current, such as lead status or preferred language	Lead status set to qualified

Amounts and dates in the agent's answers are inserted directly from the record, not retyped by the model.

How it connects

The connection uses HubSpot's standard API (application programming interface: the documented way other software exchanges data with it). Your administrators create a dedicated private app in HubSpot and grant it only the scopes (named areas of access, such as contacts or deals) the agent needs. The access token that app issues is what the connection uses.

Each connection is mapped to your configuration during implementation: your objects, pipelines, properties and processes. Credentials are stored encrypted in your deployment, every call travels over TLS 1.2 or higher (Transport Layer Security, which encrypts data in transit), and the connection runs from your deployment in your chosen region.

Permissions

Permission	Needed for	Default
Read contacts, companies and deals	Recognising the customer and their history	Only the objects and properties mapped with you
Create and update contacts and deals	Recording new enquiries and qualified interest	Only the pipelines and properties you list
Create notes and tasks	Writing back and opening follow-up work	On for the record types you choose
Delete records	Not needed	Not granted

The agent can only take actions your team has granted. Anything not granted cannot be invoked. See Permissions.

In practice

A Dubai brokerage runs its sales pipeline in HubSpot.

Priya messages on WhatsApp at 11pm about a two-bedroom apartment she saw on a listing. The agent finds no existing contact and creates one.
It answers her questions about the building and asks the brokerage's qualification questions: budget, timing and whether she is buying to live in or to let.
She is ready to view this weekend. The agent creates a deal in the qualified stage and a callback task for Sunday morning.
When the consultant starts work, the deal, the summary and the task are waiting in HubSpot.

What your team controls

Which objects, pipelines and properties the agent can read and write.
The qualification criteria that decide a deal's stage.
The private app's scopes, which your administrators can change or withdraw at any time.

Product names and logos are trademarks of their owners. Their mention shows systems Telonic connects to and does not imply partnership or endorsement.