This is Chapter 2 in a series walking through ServiceNow's AI stack from the ground up. Chapter 1 covered the platform fundamentals — CMDB, Flow Designer, ACLs, and enough scripting to read what's happening under the hood. With that base in place, this chapter looks at Now Assist the way most people will first encounter it: as a consumer, not a builder.
Before building anything with AI on this platform, it's worth spending real time just using it — watching what it gets right, what it gets wrong, and where a human still needs to step in.
1. Skill Kits and Per-Module Licensing
Now Assist isn't one switch you flip once. It's packaged into Skill Kits — bundles of specific AI capabilities scoped to a module — and each one is licensed and enabled separately. Now Assist for ITSM and Now Assist for CSM are different entitlements, even though some of the underlying capability (like summarization) looks similar on the surface.
Example — enabling Now Assist for ITSM on a PDI:
- Confirm the Now Assist for ITSM plugin is installed under System Applications > All Available Applications — on most current PDIs it ships pre-installed, but it's worth verifying rather than assuming.
- Navigate to Now Assist Admin Console and confirm the ITSM Skill Kit shows as active. If it doesn't, this is where licensing gaps show up first — a missing entitlement will block activation even if the plugin itself installed cleanly.
- Enable the specific skills you want inside that kit individually — incident summarization and resolution notes generation are typically separate toggles, not one bundled "on" switch.
- Assign the
sn_generative_ai.rai_adminor equivalent role to the users who need to configure it — this is separate from the roles that will actually consume the feature day to day.
What to actually learn: that "Now Assist is enabled" is not a single fact about an instance — it's a per-module, per-skill state, and the first debugging step for "why can't I see the summarize button" is almost always checking whether that specific skill inside that specific kit is actually turned on for that specific table.
2. Case & Incident Summarization
This is usually the first feature people see, and the easiest to evaluate honestly, because you can compare the AI output directly against the raw thread it summarized.
Example — before and after:
Before (raw work notes thread, condensed):
[Mon 9:14am] User reports VPN disconnects every ~10 min since this morning. [Mon 9:40am] Checked client version, up to date. Asked user to restart adapter. [Mon 10:02am] User confirms restart didn't help. Escalated to network team. [Mon 1:15pm] Network team found packet loss on user's ISP-side link, not VPN config. [Mon 1:20pm] User advised to contact ISP. Ticket on hold pending user confirmation. [Tue 8:30am] User confirms ISP replaced modem, issue resolved.
After (Now Assist summary, typical output shape):
User experienced repeated VPN disconnections traced to ISP-side packet loss rather than a VPN configuration issue. Resolved after the user's ISP replaced their modem.
That's a genuinely useful compression — six work notes and roughly a day of elapsed time reduced to two sentences that get a new reader oriented fast. But notice what it silently drops: the specific troubleshooting steps already tried (adapter restart, client version check). If a similar ticket comes in later, an agent relying only on the summary might repeat a step that's already been ruled out. That's the actual skill to build here — knowing when the summary is sufficient and when you need to open the full thread.
What to actually learn: read several real summaries against their source threads before trusting the feature in production. Look specifically for what gets dropped, not just whether the summary sounds fluent — fluency and completeness are different things, and generated summaries are reliably better at the former.
3. Virtual Agent
Virtual Agent is the conversational front door, and the part worth studying closely as a beginner is exactly where it recognizes its own limits and hands off to a human.
Example — a sample conversation showing the handoff point:
User: my laptop won't connect to wifi
Bot: I can help with that. Are you seeing an error message, or does
it just not find any networks?
User: it finds the network but says wrong password even though
im sure its right
Bot: That sounds like it could be a saved credential issue rather
than the actual password. Want me to walk you through
forgetting and re-adding the network?
User: i tried that already, still doesnt work
Bot: Since the basic steps haven't resolved it, I'll connect you
with a support agent who can look at this further. Creating
an incident now — you'll be routed to the Network team.
The useful thing to notice: the bot didn't try a third, more exotic troubleshooting step once the user said the standard fix failed. It recognized that as the signal to stop guessing and escalate. A poorly configured Virtual Agent topic keeps offering variations of the same fix past the point of diminishing returns, which frustrates users more than an early handoff would have.
What to actually learn: when reviewing or building a Virtual Agent topic, explicitly design the escalation condition rather than letting it be an afterthought. A topic with no clear "give up gracefully" branch is a common beginner mistake, and it's usually invisible until a real user gets stuck in a loop.
4. Where It Augments vs. Replaces
It's worth being precise about this, because it's the single most common misconception beginners bring in: Now Assist does not replace the case lifecycle. It inserts itself at specific points inside it.
Example — where Now Assist sits inside a standard incident lifecycle:
New → [AI: suggested category/priority] → In Progress → [AI: summarize thread on assignment handoff] → Resolved → [AI: draft resolution notes] → Closed
Every bracketed step is still a human decision point — the agent reviews the suggested category, the receiving team reads the summary rather than blindly trusting it, and the closing agent edits the drafted notes before submitting. None of the state transitions themselves are automated by Now Assist; the underlying ITSM process is untouched. What changes is the effort required at each of those points, not who's accountable for them.
What to actually learn: map out your own team's actual lifecycle and mark where an AI suggestion could reasonably sit, versus where it's being asked to make a decision it shouldn't own. That distinction is the difference between augmentation and quietly eroding accountability.
Checkpoint Before Moving to Chapter 3
You should be able to: enable a Skill Kit for a module and explain the licensing layer underneath it; read a Now Assist summary against its source thread and articulate what got dropped; identify whether a Virtual Agent topic has a real escalation path or just loops; and point to the exact steps in your team's lifecycle where an AI suggestion sits versus where a human decision is still required. That fluency is what makes Chapter 3 — where you start building with Now Assist for Creator — something you can review critically instead of accepting on faith.
Next in this series: Chapter 3 — Now Assist for Creator, with a real Text-to-Flow prompt, the flow it generated, and what needed fixing before it was safe to deploy.