Short answer: ServiceNow has no built-in dictation, but you can speak into any field with a system-wide voice tool. On Mac, install Voice Keyboard Pro, click into a work-notes or description box, hold your hotkey, and talk. On iPhone, switch to the Voice Keyboard Pro keyboard and tap its mic.
ServiceNow runs on typing. Every incident, every change request, every problem record, every knowledge article is a wall of text that somebody has to compose while the pressure is on. Agents live in the work-notes field. Fulfillers live in the resolution box. Change managers live in the description and the implementation plan. And all of it gets typed, one keystroke at a time, usually badly, usually in a hurry, usually right after a call where the details were still fresh and are now already fading.
Speaking is faster than typing for almost everyone. The average adult types around 40 words per minute and speaks at 130 to 150. That gap is exactly the kind of documentation debt that ServiceNow quietly generates all day: the resolution note that says "fixed" instead of what actually happened, the work note that trails off because typing the whole story is too much friction. This guide covers how to dictate directly into ServiceNow, which fields are worth talking into, which ones you should still touch by hand, and how the workflow differs on Mac versus iPhone.
Does ServiceNow have built-in dictation?
No. ServiceNow is a browser-based platform, and it does not ship a native voice-to-text feature for the fields you type into every day. There are conversational and virtual-agent features aimed at end users filing requests, but those are not the same thing as an agent being able to speak a two-paragraph work note into an incident. For the person actually working the ticket, ServiceNow expects a keyboard.
That is fine, because dictation does not have to come from inside ServiceNow. The better approach is a voice tool that works at the operating-system level and types into whatever field your cursor is in. Because ServiceNow runs in Chrome, Safari, Edge, or a Mac browser tab either way, a system-wide dictation app treats it like any other text box. There is no plugin to install into the ServiceNow instance, no admin approval to request, and nothing that touches your company's ServiceNow configuration. The voice tool lives on your machine, not in the platform.
This is the same reason system-wide dictation works across the rest of your stack. If you also live in a ticketing tool, the approach in our guide to dictating in Freshdesk and dictating in Zendesk is identical: one voice tool, every field, every app.
How to dictate in ServiceNow on a Mac
On macOS you have two realistic options: the built-in dictation that ships with the operating system, and a dedicated tool like Voice Keyboard Pro. Both put text at your cursor inside a ServiceNow form. The setup is the same either way.
Step by step
- Open your ServiceNow instance in your browser and pull up the record you are working: an incident, a change, a problem, or a knowledge article.
- Click into the field you want to fill. This matters more than it sounds. Dictation types wherever the cursor is, so click directly into the Work notes box, the Additional comments box, the Description, or the Resolution notes before you start talking.
- Trigger dictation. With Voice Keyboard Pro you hold your chosen hotkey; with the macOS built-in feature you press the Fn key or your configured shortcut.
- Speak in complete thoughts. Say the punctuation out loud where you want it: "the disk filled up on the primary node comma we cleared the temp directory and restarted the service period".
- Release the hotkey. The text appears in the field. Read it, fix anything, and save or update the record as normal.
The reason a dedicated tool tends to win for ServiceNow work is consistency across the odd corners of the platform. ServiceNow forms are full of embedded fields, journal inputs, activity streams, and the rich-text editor inside knowledge articles. A hold-to-talk tool that inserts text at the cursor behaves the same in all of them, whereas the built-in Mac feature can behave inconsistently inside heavily scripted web forms. If macOS dictation is dropping words or refusing to type into a ServiceNow field at all, our guide to Mac dictation not working in third-party apps walks through the usual causes.
The fields worth dictating
Not every part of a ServiceNow record deserves your voice. The rule is simple: speak the prose, type the structured data. Here is where dictation earns its keep.
- Work notes. This is the single biggest win. Work notes are the running log of what you actually did, and they are almost always under-written because typing them mid-incident is a chore. Talk them out instead: "took over from tier one at fourteen hundred comma reproduced the timeout on the staging URL comma escalating to the network team period".
- Resolution notes and close notes. The field that matters most for the next person and the field most likely to say "resolved" and nothing else. Speak the real root cause and the fix. Future you, reading this ticket during a similar outage, will be grateful.
- Additional comments (customer-visible). The update the requester actually reads. Dictate a full, human sentence instead of a curt fragment.
- Description. When you open an incident or problem on someone's behalf, narrate the symptom and impact in plain language.
- Change request details. Implementation plan, backout plan, test plan, and risk assessment are all long-form prose that people rush. Dictation makes a thorough plan cost the same effort as a lazy one.
- Knowledge articles. KB drafts are just documents. Talk the first pass, then edit. This is the same workflow as dictating in Confluence or any other wiki.
The fields to leave alone
Dictation is wrong for structured, exact, or list-driven data. Do not talk these:
- Configuration item names, host names, and reference fields that use type-ahead lookups. Let ServiceNow's autocomplete match the exact CI record.
- Assignment groups, categories, subcategories, priority, and state. These are dropdowns, not text.
- Ticket numbers, KB numbers, IP addresses, and error codes. Type these, or better, paste them. A spoken "INC zero zero one two three four five six" is slower and more error-prone than typing it.
A useful habit: click into a prose field, dictate the paragraph, then reach for the mouse to set the dropdowns and reference fields by hand. You get the speed of voice for the writing and the precision of the interface for the metadata.
Teaching your voice tool ServiceNow's vocabulary
Every IT shop speaks its own dialect. Application names, internal acronyms, server naming conventions, product SKUs, and the surnames of the people you escalate to are exactly the words a general transcription engine has never seen. Left alone, they come out as the nearest common word, and you spend your saved time correcting them.
This is what Voice Keyboard Pro's Smart Vocabulary is for. It is a personal dictionary with replacement rules: you tell it that when you say a term it should always be written a specific way. Add your CMDB application names, your ticket-prefix conventions, your data-center codes, and the names of your assignment groups. Say the phrase the way you naturally would, and it lands correctly in the work note every time. Because the dictionary lives on your machine and applies everywhere, the same entries help you in email, in chat, and in your Jira tickets too.
Spend ten minutes seeding it with the fifty terms you type most, and the accuracy on ServiceNow's specialized language stops being a problem. This is far more effective than hoping raw transcription guesses your internal jargon.
How to dictate in ServiceNow on an iPhone
Plenty of ServiceNow work happens on a phone, whether in the Now Mobile app or in a mobile browser: an on-call engineer updating an incident from bed, a field tech closing a task between sites, an approver leaving a comment on a change. Typing a proper update on a phone keyboard is miserable, which is why so many mobile updates are one word long.
The iPhone version of Voice Keyboard Pro is a full custom keyboard with a mic button built in. Because it is a keyboard, it works in any app that accepts text, including the Now Mobile app and any ServiceNow form loaded in Safari or Chrome. Set it up once:
- Install Voice Keyboard Pro from the App Store and open it once to finish setup.
- Go to Settings → General → Keyboard → Keyboards → Add New Keyboard and add Voice Keyboard Pro. Enable Allow Full Access so it can transcribe.
- In ServiceNow, tap into a work-notes or comment field, tap the globe icon to switch to the Voice Keyboard Pro keyboard, then tap the mic and talk.
If you have never enabled a third-party keyboard before, our walkthrough on enabling Full Access on iPhone explains exactly what that permission does and why it is needed. Once it is on, updating a ServiceNow ticket from your phone stops being a reason to wait until you are back at a desk.
Two mobile features that matter for ticket work
The iPhone keyboard has two extras that fit ServiceNow work particularly well. The first is Voice Edit: after you dictate an update, you can speak a correction instead of pecking at the text. Say something like "change the second sentence to say the workaround is temporary" and the text is revised. That is genuinely useful when you have dictated a hot update and want to soften the tone before a requester reads it.
The second is two-way translation while you dictate, across 24 languages. If you support a global user base, you can speak in your language and have the customer-visible comment written in theirs, or read an incoming note in a language you do not speak. For a service desk that spans regions, that turns a translation detour into a single step.
A realistic incident workflow, start to finish
Here is how the pieces fit together on a normal ticket. You pick up an incident that has been sitting in your queue. You click into Work notes, hold your hotkey, and narrate what you see: "requester reports the reporting dashboard returns a five hundred error comma confirmed on my end comma checking the app node logs now period." You release, the note lands, you save. You set the state and assignment group with the mouse.
Twenty minutes later you have the fix. You click into Resolution notes and speak the whole story, not a fragment: the query timing out, the missing index, the index you added, and how you verified. You click into Additional comments and dictate a plain-language update to the requester. You set the close code by hand. The whole record is now more useful than the ones around it, and it took less time than typing a worse version would have.
Multiply that by every ticket in a shift and the difference is not a minor convenience. It is the difference between a knowledge base full of "resolved, no notes" and one that actually helps the next person on call. The same logic applies to any high-volume writing surface, which is why teams that adopt voice for ServiceNow tend to keep using it in their customer messaging and email too.
Is dictating into ServiceNow secure?
This is the right question to ask about any tool that touches ticket data, because incidents routinely contain names, internal system details, and occasionally sensitive information. Voice Keyboard Pro is built around a clear boundary: your audio is transcribed and the text is placed at your cursor, and the company's servers store only operational pings needed to run the service. As of the May 2026 privacy update, no audio and no transcript content are retained on the backend. The words you speak into a work note become text in the field and stay in your ServiceNow instance, governed by your organization's own controls.
That said, the same rule applies here as with any per-app dictation in a regulated environment: follow your employer's policy. Some organizations restrict what can be processed by third-party tools, and a service desk handling regulated data may have specific requirements. We cannot rule on your company's compliance obligations, so if you work under strict data-handling rules, clear the tool with your security team before you point it at production tickets. If it is approved, you dictate freely; if it is not, you have asked the right question first.
The bottom line
ServiceNow will not add dictation to the fields you actually type into, and you do not need it to. A system-wide voice tool treats every ServiceNow box like the plain text field it is. Speak your work notes, resolution notes, comments, change plans, and knowledge drafts; type the CIs, dropdowns, and numbers. Seed a personal vocabulary with your internal jargon so the specialized terms land right. Do it on the Mac with a hotkey and on the iPhone with the keyboard mic, and your tickets get more complete while costing you less effort.
Voice Keyboard Pro has a free tier, so you can point it at your next incident and see the difference before deciding. Dictate one full work note out loud and compare it to the fragment you would have typed. The gap is the whole point. Pro is $4.99 a month or $34.99 a year when you want to remove the daily limits.