HubSpot is one of the largest SaaS interfaces a typical office worker uses. As of 2026 it has dozens of products (Sales, Marketing, Service, CMS, Operations), thousands of settings, and a UI that has been re-themed twice in the past 18 months. Most users — sales reps, ops admins, marketers, customer-success managers — operate it the way you would operate any large house you moved into recently: confidently in three rooms, lost in everything else. A push-to-talk AI assistant pinned to the actual DOM elements of the page is a different way to use a tool like this. This post is about why, and what it looks like in practice.
Why HubSpot is hard to navigate
HubSpot is hard not because the people who built it did anything wrong. It is hard because it is genuinely big — every customer-facing function lives in there, every customer-facing function has its own team shipping new features, and the UI has to absorb all of it. The side effects are familiar to anyone who has used the product for more than a year:
- The same control lives in three places. Email settings appear in your profile, in the inbox, and inside Marketing Email. Which one you want depends on what you are trying to do.
- Search is name-based. If you do not know the official label of the setting you want, search will not find it. “Stop sending me notifications when a deal closes” does not match the field that controls it.
- Labels change. “Workflows” used to be one place; it is now three places, with subtly different capabilities depending on which entry point you used.
- Power users learn the URLs. The way most experienced HubSpot admins navigate is by typing partial URLs into the address bar. That is not navigation; it is muscle memory built over years.
The standard answers — knowledge base articles, video courses, in-app tours — are all good investments and all leave a gap. The gap is the moment a user is staring at a screen, knows roughly what they want, and cannot find the control. That moment is too small for a course, too specific for a knowledge base article, and too late for a tour.
The shape of help that actually works
We wrote about this at length in Why Product Tours Fail and In-Product AI Assistant: An Alternative to Pendo, Appcues, WalkMe. The short version: in-app help has to be asked for, not pushed; it has to land on the actual element the user is asking about, not in a sidebar paragraph; and it has to survive UI changes without an editorial team rewriting every tooltip when the design system ships a new release.
That is what a push-to-talk voice assistant pinned to the DOM delivers. The user holds Alt, asks (“where do I turn off the notification when a deal closes?”), and the relevant toggle gets a halo drawn on it while a voice answer plays. The halo survives reflows because it tracks a CSS selector. The voice answer does not require the user to look away from the page.
How a voice + halo loop maps to HubSpot
Clicky is the assistant we make and the only one shipped today with this exact loop. Three concrete things change when you have it installed and pointed at HubSpot:
- Finding fields stops being a search problem. You describe what you want in natural language; the halo lands on the field. “Where do I set the timezone for this user?” works without knowing the menu path.
- Onboarding new hires stops being a half-day shadow. The new rep installs the extension, holds Alt when they get stuck, and gets pointed at the actual control. They learn the interface faster because they see where things are, repeatedly, without interrupting a colleague.
- Every UI change stops being a documentation crisis. When HubSpot moves a setting in a release, your knowledge-base article goes stale; the assistant adapts because it reads the current page, not a frozen tour script.
Five concrete use-cases
These are the five questions we hear most often from HubSpot users running Clicky. None of them are exotic — they are the ordinary friction of operating a big CRM.
- “Where is the deal stage probability setting on this pipeline?” Lives in Pipeline settings > Customise stages, but new admins rarely find it on the first try. A halo on the right column removes the ten-minute hunt.
- “Which property do I edit so the calculation in this dashboard updates?” The dashboard shows the calculated value; the property lives in a different settings page. Asking the question while pointing at the dashboard tile is dramatically faster than tracing the calculation by hand.
- “How do I stop this workflow from re-enrolling contacts every time?” The toggle is buried in the workflow settings tab and labelled in a way that is easy to read past. Halo on the toggle, voice explanation of what it does — done.
- “Where do I turn off the notification email for this event?” The same notification is configurable in three places, depending on whether you want to silence it for yourself, for your team, or globally. The assistant disambiguates and points at the one you actually want.
- “What does this audit-log entry mean?” The log shows changes by ID; the assistant resolves the ID inline and explains what changed in plain language, without opening another tab.
Why this beats the knowledge base
HubSpot’s knowledge base is excellent. The problem is the cost of using it. To answer a single “where is X” question with the knowledge base, you have to: stop what you are doing, switch tabs, run a search, scan three results, open the most promising one, scroll to find the relevant section, read it, hold the instruction in working memory, switch back to HubSpot, and execute. That is two minutes of context switching for what is objectively a five-second question.
A voice + halo loop collapses the seven steps to one: ask, see the halo, act. The knowledge base is not redundant — it is still the right answer for “explain a concept” or “walk me through a multi-step setup.” It is the wrong answer for “where is the toggle.”
Why this beats classic in-app tours
HubSpot itself ships in-app tours and contextual nudges; some organisations layer Pendo, Appcues, or WalkMe on top of HubSpot for additional onboarding. We covered the broader weakness of that approach in Why Product Tours Fail. In a HubSpot context, the specific problem is that tours are push, not pull. They fire when the system thinks you need them, not when you ask. That works for the first day; it fails for everything after.
A push-to-talk assistant inverts the model. It is silent until you ask. It does not own the tutorial sequence; it answers whatever question you have, in the moment you have it, on the page you are on. For users who already know HubSpot well — the experienced admin, the operations lead — that is the only kind of help that does not feel patronising.
Privacy and CRM data
HubSpot contains customer data. That is the right context to be nervous about installing a Chrome extension on the machines that access it. The shape of Clicky’s permission model is relevant here.
Clicky requests only the activeTab Chrome permission, fired strictly when the user holds Alt — never in the background, never on a tab the user is not actively using. Memory is session-only; nothing persists server-side beyond the in-tab conversation. By design, the extension cannot see your HubSpot data unless you explicitly invoke it on a HubSpot tab; and even then, only what is visible at the moment of the press is included in the model call.
For a security review, the relevant comparison is against broad-host AI sidebar extensions that read every page in the background. We laid out the framework in Chrome Extensions That Do Not Track You; the practical takeaway is that activeTab-only is a much easier conversation with a CRM admin than “reads every site you visit.”
Frequently asked questions
Is this an official HubSpot integration?
No. Clicky is a Chrome extension that works on any web page, including HubSpot. It does not use the HubSpot API and does not require admin approval inside HubSpot to install. The extension only sees what the active tab shows on Alt-press.
Does it work on the HubSpot mobile app?
No. Clicky is a Chrome browser extension; it does not exist on mobile. For mobile-first SaaS, voice navigation is a different product category we are not in.
Does it work on Salesforce, Pipedrive, Notion, etc.?
Yes — Clicky works on any web page rendered in Chrome. HubSpot is the example in this post because it is one of the most-asked cases, but the same loop applies to Salesforce, Pipedrive, Zoho, Monday, Notion, Linear, Jira, Stripe, Shopify, and the long tail of admin dashboards your team uses.
How do new hires use it during their first week?
Install during the laptop setup, walk them through the Alt-key gesture in 30 seconds, and tell them to hold Alt and ask whenever they get stuck instead of pinging Slack. Most new HubSpot users ramp meaningfully faster on the second week. We covered the broader pattern in How to Onboard New Hires on Your SaaS Stack.
Part of our product-activation series. See also From Activation to Autonomy and Why Product Tours Fail.