Short answer: HubSpot has no dictation setting, so failures come from macOS Dictation, your browser, or the field itself. Test in TextEdit first. If that works, check for a call tool still holding the microphone, a cursor not really in the field, or a note that never registered the text.
You hang up from a discovery call, open the contact record in HubSpot, click Note, and start dictating the three things the prospect said that matter. Then one of several things happens. Nothing appears at all. The words appear and then disappear. The note looks perfect until you realise it never saved. Or the text lands somewhere you did not intend, like the search bar at the top of the page.
HubSpot is a large web application with many different kinds of editable field: rich text note and email editors, inline property fields in the record sidebar, chat and ticket reply boxes in the inbox, task descriptions, and call notes that sit next to an active call. Each one behaves slightly differently when text arrives from outside the keyboard, and that is why dictation can work in one corner of HubSpot and fail in another on the same afternoon.
The failures sort into a small number of categories. A thirty-second test tells you which category you are in, and the nine fixes below are ordered so the most common causes come first.
Start here: the thirty-second split test
HubSpot does not have a dictation feature of its own, and nothing in your HubSpot settings turns dictation on or off. That means a dictation failure inside HubSpot always belongs to one of two separate systems:
- macOS Dictation (or whichever dictation tool you use). It listens to your microphone, transcribes your speech, and inserts the result into whatever text field currently has focus anywhere on your Mac.
- The browser and the HubSpot page. Which field has focus, whether the editor notices text that was inserted rather than typed, whether the page reloads underneath you, and whether your organisation manages the browser.
Run this test to find out which side is broken:
- Open TextEdit, click into a blank document, and dictate one sentence.
- Switch to your browser, open a new tab, click into the address bar, and dictate the same sentence.
- Open HubSpot, click into the global search box at the top, and dictate a contact name.
- Open a contact record, click Note, click inside the note body so you see a blinking cursor, and dictate a sentence.
Read the result like this:
- Fails in TextEdit: the problem is macOS, not HubSpot. Go to Fixes 1 to 3.
- Works in TextEdit, fails in the address bar: the browser is the problem. Go to Fix 4.
- Works in search, fails in the note: it is a field or focus problem. Go to Fixes 5 to 8.
- Works everywhere during the test but fails right after calls: something is holding the microphone. Go to Fix 3.
Fix 1: Confirm Dictation is actually on and the shortcut fires
Open System Settings, then Keyboard, and scroll to Dictation. Make sure it is turned on and note which shortcut is set. If you have recently updated macOS, check this first, because updates occasionally reset preferences or change what a key does.
Then look at the Globe key setting on the same page, labelled something like "Press Globe key to". If it is set to change input source or show the emoji picker, a double press of the Globe key will not start dictation. Either set the shortcut to something you will reliably press, or change the Globe key behaviour. If you use a keyboard remapping utility, temporarily quit it and test again, because remappers frequently intercept the Fn or Globe key before macOS sees it. Our guide to the Mac dictation shortcut not working goes deeper on shortcut conflicts.
The quick check: when you press the shortcut, you should see the small microphone indicator appear near the cursor. No indicator means the shortcut never fired, which is not a HubSpot problem at all.
Fix 2: Check the input device and the language
Open System Settings, then Sound, then Input. Speak and watch the level meter. If it does not move, macOS is listening to the wrong microphone, often a disconnected headset, a monitor with a built-in mic, or a virtual audio device left behind by a recording or calling tool.
Back in the Dictation settings, check the language. If the microphone indicator appears and you get fluent text that is simply wrong, as if you were being heard in another language or dialect, a language mismatch is the likely cause. This is easy to trigger if you have added a second keyboard language, because dictation can follow it.
Fix 3: Release the microphone from HubSpot calling and other call tools
This is the cause most people never suspect. If you make calls from inside HubSpot, use a separate dialer, or were just on a video meeting, that tool may still be holding your microphone. Muting does not release the device. Dictation then starts normally, the indicator shows, and it hears silence, so nothing is inserted.
The distinctive symptom is "no text" rather than "wrong text", and it tends to appear right after a call. Try this:
- End the call fully and close any calling window or popped-out call panel.
- If you used a desktop meeting or dialer app, quit it with Command-Q rather than closing the window.
- If you use a headset, note that some Bluetooth headsets switch into a lower-quality two-way mode during calls and take a moment to switch back. Dictating in the first second after a call can lose the start of your sentence.
A practical habit for sales reps: let the call end, count to three, then dictate the note. If the microphone is regularly contested, using the Mac's built-in microphone for dictation and the headset for calls avoids the fight entirely. Our post on dictation not working during video calls covers the contention problem in more detail.
Fix 4: Rule out the browser
System dictation does not need the website's microphone permission, because macOS does the listening, not the page. So the site permission prompt in your browser is not what blocks dictation. It does matter for HubSpot calling, which uses the browser's microphone access directly, and that is a separate question.
What can block dictation at the browser level:
- A managed browser. If your company manages Chrome, open
chrome://policyand look for audio capture policies. A managed policy can override what the visible settings page shows. If you see one, that is a conversation for IT. - The wrong browser profile. If you run separate work and personal Chrome profiles, settings and extensions differ per profile. Test in the profile you actually use for HubSpot.
- Extensions. Grammar checkers, sales engagement extensions, and email trackers inject their own layers into text fields. Open HubSpot in a private window with extensions disabled and dictate into a note. If it works there, re-enable extensions one at a time.
- A different browser entirely. Try the same note in Safari. If it works in Safari but not Chrome, you have narrowed it to the browser. Our guide to Mac dictation not working in Chrome walks through the Chrome-specific causes.
Fix 5: Make sure the cursor is actually in the field
HubSpot pages have a lot of clickable surface that looks editable but is not. Clicking a note's title area, a card header, or an empty region of the sidebar can highlight something without placing a text cursor. Dictation needs a blinking cursor in a real text field.
Common traps in HubSpot specifically:
- Sidebar property fields. Many properties on the left of a record display as text until you click them. The first click opens the field for editing. Dictate only once you can see the cursor inside the input.
- Dropdown and picker properties. Lifecycle stage, deal stage, owner and similar fields are selection controls. Dictating at them does nothing useful. Pick the value by hand.
- The note panel. Clicking Note opens the editor, but depending on the view, focus may not move into the body automatically. Click inside the body before you speak.
- Association and mention pickers. Typing the @ symbol in a note opens a picker for tagging a teammate. Those pickers expect real keystrokes, so type the @mention by hand and dictate the surrounding sentence.
If text appeared in the global search box instead of your note, focus was on search when you started speaking. Click back into the note body and dictate again.
Fix 6: When the note looks right but does not save
This is the most frustrating failure because nothing looks wrong. Rich text editors in web apps track changes through keyboard and input events. Dictation normally triggers those events, but in some editors and some browser combinations, text inserted from outside the keyboard can appear on screen without the editor registering that the content changed. The Save or Create button may stay disabled, or the saved note may come back shorter than what you saw.
Two workarounds are reliable:
- Type one character and delete it after dictating. That real keystroke tells the editor the content has changed.
- Dictate somewhere else and paste. Dictate the note into a plain text field or a notes app, then copy and paste it into HubSpot. Paste is a normal input event every editor recognises.
Before closing the note panel, glance at the saved note on the timeline. If the timeline entry matches what you dictated, you have your answer for that editor. If it is consistently truncated or empty, make the paste workflow your default for that field.
Fix 7: Stop the page from stealing focus mid-sentence
If text starts appearing and then stops, or vanishes partway through, the page probably changed underneath you. HubSpot records load activity, associations and cards in stages, and a panel that finishes loading can move focus away from where you were typing. Switching between tabs in a record, or having a workflow or integration update the record while it is open, can do the same.
- Wait until the record has finished loading before you click into a field.
- Avoid dictating in the first few seconds after saving another change on the same record.
- Dictate in shorter chunks. Two or three sentences at a time survive a focus change better than a two-minute monologue.
- If you work with many records open in tabs, dictate into the tab in the foreground only. Background tabs are sometimes throttled and refreshed by the browser.
Fix 8: Check field length and field type
If your dictated text is always cut off at a similar point, or the save fails with an error, the problem may be the property itself. A single-line text property is designed for short values, and some fields are validated against a specific format such as a phone number, date, or URL. Dictating a paragraph into a field built for a short value will not end well.
Longer context belongs in a note, a multi-line text property, or the description of a task or deal. If your team has created custom properties for things like call summaries, ask your HubSpot admin whether they are set up as multi-line text. Dates, phone numbers, deal amounts and email addresses are worth typing by hand anyway, because a dictation tool can produce something that looks right but is formatted in a way the field will reject or, worse, accept incorrectly.
Fix 9: Restart in the right order
If none of the above has solved it, do a clean restart in this order, testing after each step:
- Quit any calling, meeting or recording app with Command-Q.
- Quit the browser completely with Command-Q and reopen it.
- Turn Dictation off in System Settings, wait a few seconds, and turn it back on.
- Restart the Mac.
Quitting the call tool is the step most likely to help, because a lingering background process can keep the microphone busy long after the call window is gone. If dictation still fails in TextEdit after a restart, your issue is system-wide and our full Mac dictation fix list is the next stop.
HubSpot quirks that are not actually bugs
- Chat and inbox replies can send on Return. If you say "new line" while dictating into a conversation reply box, check how your inbox handles Return before you dictate. A dictated line break may send a half-finished message.
- Dictation stops after silence. macOS Dictation ends a session after a pause. That is not HubSpot cutting you off.
- Sequences and templates use personalisation tokens. Insert tokens such as first name or company from the menu. Speaking the token syntax will produce literal text, not a working token.
- Emails send from what you see. Unlike a note, an email to a prospect is external. Read a dictated email once before you press send, especially names and numbers.
Why the right words still come out wrong: CRM vocabulary
Once dictation works mechanically, the next frustration is accuracy on the words that matter most in a CRM: company names, product names, plan tiers, competitor names, acronyms like MQL, SQL, ARR and ACV, and the unusual spellings of people's names. General-purpose dictation guesses at those, and correcting them by hand eats the time you were trying to save.
This is where Voice Keyboard Pro is built differently. On Mac, you hold a hotkey, speak, and release, and the text appears at your cursor in whatever app has focus, including a HubSpot note in any browser. Its Smart Vocabulary is a personal dictionary with replacement rules, so you can teach it your product names, your key accounts and the acronyms your team actually uses, and have them come out spelled the way your CRM expects.
Because it inserts text at the cursor rather than through a browser feature, the split test above still applies: click into the field, see the cursor, then speak. The same field-type advice applies too. Paste into editors that ignore inserted text, and type identifiers like deal amounts and phone numbers.
For reps who take a lot of calls, Meeting Mode adds speaker detection and AI notes for meetings, and calendar meeting detection can prompt you when a scheduled meeting starts. Always follow your company's policy and the other party's consent on recording. On iPhone, the Voice Keyboard Pro keyboard has a built-in mic button, so you can dictate into the HubSpot mobile app between meetings, and Voice Edit lets you speak a change to fix a sentence without retyping it.
On privacy, which matters when you are describing customer conversations: our server stores only operational pings. No audio and no transcript content is kept. There is a free tier with daily limits, and Pro is $4.99 per month or $34.99 per year.
Why dictating CRM notes is worth fixing
The average adult types around 40 words per minute, and even experienced typists usually sit in the 80 to 100 range. Most people speak at 130 to 150 words per minute. A 200-word call summary is about five minutes of typing at an average pace and well under two minutes spoken. That gap is the difference between logging the note straight after the call and promising yourself you will do it at the end of the day. If you want to build the habit rather than just fix the tool, our guide to dictation for CRM updates covers the workflow, and how to dictate in HubSpot covers day-to-day use.
Frequently asked questions
Does HubSpot have its own voice-to-text feature?
HubSpot does not provide a general dictation setting for typing into fields, so dictation into notes and properties comes from macOS or a third-party dictation app. HubSpot features change over time, so check HubSpot's own documentation for any recording or transcription features on your plan.
Why does dictation work in Gmail but not in HubSpot?
Different editors react differently to inserted text, and HubSpot pages load in stages that can move focus. Work through Fixes 5 to 7: confirm the cursor, try the type-and-delete trick, and wait for the record to finish loading.
Do I need to give HubSpot microphone permission for dictation?
No. System dictation and third-party dictation apps listen through macOS, not through the web page. Browser microphone permission matters for in-browser calling, not for dictating into a text field.
My note saved empty. Is the text lost?
If the editor never registered the change, the text was not saved to HubSpot. Before closing a note you have dictated, check the timeline entry. For important notes, dictate into a notes app first and paste.
Can I dictate in the HubSpot mobile app on iPhone?
Yes. The built-in iPhone keyboard mic works in most text fields, and a third-party keyboard such as Voice Keyboard Pro works in any app that allows custom keyboards. If iPhone dictation is misbehaving generally, start with our iPhone dictation fixes.
Is the same fix list useful for Salesforce?
The categories overlap, but the specific traps differ. See our guide to Mac dictation not working in Salesforce for the Lightning and console-specific causes.
Quick reference
- Fails in TextEdit too: system-level. Check Dictation is on, the shortcut, input device and language.
- No microphone indicator: the shortcut is not firing. Check the Globe key setting and remappers.
- Indicator shows, nothing appears, right after a call: a call tool still holds the microphone. Quit it.
- Works in search, fails in a note: focus or field type. Click inside the body and look for the cursor.
- Note looks right, saves empty: the editor missed the change. Type and delete a character, or paste.
- Text vanishes mid-sentence: the record reloaded. Wait for it to settle and dictate in shorter chunks.
- Always cut off or rejected: single-line or formatted property. Use a note or multi-line field.
- Works in Safari, not Chrome: extensions, profile or managed policy. Check
chrome://policy. - Right sentence, wrong company and product names: you need a vocabulary layer.
Most HubSpot dictation problems come down to three things: a microphone still held by a call tool, a cursor that was never really in the field, or an editor that did not notice the text arrive. Check those three before you change anything else.
The words land at your cursor in whatever app you are already in — Mail, Slack, Word, a browser form. No dictation window, nothing to copy across.
Free forever for casual use · Apple Silicon & Intel