HubSpot
HubSpot holds the marketing and sales record for a large number of mid-market organisations, and its value in an assistant deployment is usually capture rather than lookup.
HubSpot holds the marketing and sales record for a large number of mid-market organisations, and its value in an assistant deployment is usually capture rather than lookup.
What HubSpot holds, and why that matters here
HubSpot combines CRM, marketing automation and service in one place. Organisations running it tend to be growth-oriented and marketing-led, which shapes what an assistant should do with it: the highest-value action is usually capturing an enquiry with its context, not answering a question about an existing record.
That said, the lookup case is real for service teams — contact history, deal stage and previous tickets — and it prevents the specific failure of asking a customer to explain something they already explained.
- Contacts and companies — the record and its history.
- Deals — stage, value and pipeline position.
- Tickets — service history where the service hub is used.
- Marketing activity — what a contact has received and engaged with.
- Forms and submissions — what someone has already told you.
Questions Elbi can answer from HubSpot
Has this person contacted us before?
Contact history, which prevents asking someone to repeat themselves.
What stage is this deal?
Pipeline position and next step.
Capture this enquiry
Writing a new contact and its context onto the record while the interest is live.
What did they download?
Marketing engagement history for context before a sales conversation.
Is there an open ticket?
Service history, so a sales conversation does not walk into an unresolved problem.
What did they tell us on the form?
Previously submitted information, so it is not asked twice.
How Elbi connects to a HubSpot account
- A private app, created by a super adminThe connection uses a private app in your HubSpot account — HubSpot's mechanism for an integration that serves a single account. Only a super admin can create one. HubSpot issues an access token for it, and the scopes chosen at creation decide which objects it can reach.
- Read scopes for the objects on the listFor lookup that usually means read scopes on contacts, companies, deals and tickets, plus owners so the assistant can say who looks after a record. A request for anything outside those scopes is refused by HubSpot itself.
- An account-wide token, person-level answersA private app's token is not tied to one user's view: it sees every record its scopes allow, whatever your HubSpot teams look like. So the scopes set the outer limit, and the asking person's own entitlement — owner and team, as you already assign them — is applied inside it.
- Find the contact, then follow the associations"Has this person contacted us before?" starts with the contact, found by email address or phone number, then follows HubSpot's associations to the company, open deals and tickets. Where the match is uncertain, the assistant asks one confirming question instead of guessing.
- Internal values become labelsHubSpot stores stages and statuses as internal values under property names such as hs_lead_status. The reply uses the labels your team sees — pipeline stage names, lifecycle stages — in Arabic or English to match the question.
- Capture writes to one placeThe write that earns its keep is capture: a new contact, or a note on an existing one, carrying what the person said. HubSpot treats the email address as the unique key for a contact, so capture should look it up first and add to the existing record rather than attempt a duplicate.
HubSpot scopes, tokens and control
| Direction of access | Read by default. Creating contacts, adding notes or opening tickets needs the matching write scope, is enabled per action and can wait for a person to approve. Deal stages are best left to your team. |
|---|---|
| Scopes | Chosen when the private app is created and changeable later by a super admin. Each is named by object — contacts, companies, deals, tickets — so "what can it touch?" is answered with a list. |
| Team and owner visibility | HubSpot's view permissions — everything, team only, or owned only — describe what each user may see. Because the token is account-wide, the same rule is applied to each person's answers, based on record owner and team. |
| Credentials | The access token belongs to your account. A super admin can rotate it from the private app's settings, or delete the app outright, without asking us. |
| Where data goes | Contact and deal details read for a reply are used for that reply and not stored again elsewhere. The conversation itself is destroyed within 24 hours, generally when it ends, and no external AI service processes it. |
| Audit | Each lookup can be recorded with its question. HubSpot also keeps a log of the private app's API calls, so your admin can check its activity from HubSpot's side. |
| If it is unavailable | If HubSpot cannot be reached, or the account's API rate limit is hit, the assistant says it could not check and offers a person, so an enquiry is handed over rather than lost. |
What this replaces
The strongest case for HubSpot in an assistant deployment is closing the gap between an enquiry and a record. Enquiries arrive at all hours; forms capture only what someone is willing to type into fields; conversations capture far more and far more honestly.
Writing that context onto the record while the interest exists is the difference between a lead that is followed up with understanding and one that is followed up with a template. It also removes the gap where out-of-hours enquiries are lost entirely.
For service teams the value is the reverse — reading history so that a customer who has already explained their problem is not asked to explain it again.
Which HubSpot users get the most from it
B2B services
Enquiry capture with context, out of hours.
Agencies
Client history before a call.
SaaS
Ticket and deal history in one place.
Growth-led teams
Attribution context for conversations that started with a campaign.
Getting value from HubSpot data
In a HubSpot account the first thing worth connecting is usually capture, not lookup. Enquiries that arrive by chat outside working hours are the ones most easily lost, and a contact created with the conversation attached is worth more to a salesperson the next morning than a bare form submission.
For service teams on HubSpot's help desk, the first lookup is "is there an open ticket?", answered from the tickets associated with the contact and the pipeline stage each has reached. For sales, it is deal stage and owner. Both use standard objects and a handful of properties.
Marketing history comes last, and deliberately. Which emails someone opened or which guide they downloaded is useful context for a salesperson preparing a call; it is not something to read back to the person in a chat, and the scope should reflect that difference.
Connecting HubSpot, step by step
- Agree the capture and the questionsDecide what a captured enquiry should contain — which properties, which lifecycle stage, which owner or team receives it — and which questions the assistant should answer. The two lists together set the scopes.
- Create the private appA super admin creates the private app, ticks only those scopes and hands over the access token for the connection. The token stays under your control and can be rotated whenever you choose.
- Map properties and pipelinesCustom properties, deal and ticket pipelines with their stage names, and any custom objects your subscription includes are mapped, with Arabic wording agreed for anything customers or staff will hear.
- Send captured contacts through your workflowsA contact created from a conversation should enter the same workflows as one from a form, so assignment, follow-up tasks and lead status behave as your team expects. That is configured in HubSpot, not in the assistant.
- Test with awkward recordsTry an existing contact writing from a new email address, a company recorded once in Arabic and once in English, a ticket closed yesterday, and someone who has opted out of communications.
- Launch on capture and one lookupGo live with capture and the most frequent question, read a month of real conversations, then add scopes. Every scope change is made by your super admin, inside HubSpot.
HubSpot contacts, consent and the PDPL
HubSpot is, by design, a record of individuals: names, emails, phone numbers, and a timeline of what each person opened, submitted and said. Under the Saudi Personal Data Protection Law, adding someone to that record from a conversation is processing that needs a purpose and a basis, and the person should know it is happening.
HubSpot helps if you use it. With its data privacy settings switched on, a contact can carry a lawful basis for processing and communication subscription preferences, and capture from chat should set those honestly rather than subscribe someone to marketing because they asked a question. Elbi's side is simple to state: conversation content is gone within 24 hours, and HubSpot holds the lasting record.
Tell people at the start of the chat, in the language they are writing in, that details they share may be saved to your records.
What organisations typically see
HubSpot's own AI and chat tools, and where Elbi fits
HubSpot has its own conversational tools. The chatflows in its conversations inbox include a bot builder, and Breeze, HubSpot's AI layer, adds an assistant for staff and AI agents for work such as answering customers from your knowledge base. Because they live inside HubSpot, they write to the CRM with nothing to connect.
For Saudi organisations the useful comparison is practical. Test the Arabic on real enquiries, including dialect and messages that mix Arabic and English. Check where AI processing for your account takes place and whether that suits your PDPL assessment; HubSpot stores each account in a data-centre region chosen when the account is set up. And ask whether the assistant needs sources beyond HubSpot — an ERP, policy documents — in the same conversation.
Elbi's answers are the same for every source it connects to: Arabic and English as first languages, conversation processing inside the Kingdom on infrastructure you control, and no external AI service. HubSpot stays the record; Elbi is a bilingual front door that fills it. Running both is possible, provided each channel has one owner, so a customer is never answered twice.
The common mistake on any route is letting capture create a new contact for every conversation. Within a few months sales is working through duplicates, and the CRM is less trustworthy than it was before anything was connected.
Common questions
Where you enable it. Capture is usually the highest-value action here.
Only if configured to write indiscriminately. Scope write-back to specific actions with optional confirmation.
Yes, mapped during deployment.
It sees what its scopes allow, across the whole account — HubSpot does not narrow a private app by team. That is why the scopes are kept to the objects on the question list, and why answers are then bounded by the asking person's owner and team.
Where capture is enabled, it becomes a contact with the conversation attached, and your HubSpot workflows assign it as they would a form submission. Your team starts the morning with the context, not just a name and an email address.
Where you use HubSpot's help desk and enable it, yes: a ticket in the pipeline you choose, associated with the contact and carrying the conversation, so the agent who picks it up does not start from nothing.
Connect Elbi to your HubSpot account
A working assistant that reads and fills your own HubSpot records, in Arabic and English.