Otto vs Now Assist: What Actually Changed

[laurenmcman]

Let's address the elephant in the comments section first, because it's the same question no matter which Knowledge 26 recap or LinkedIn post you're reading it under:

Is ServiceNow Otto just Now Assist wearing a trench coat?

Fair question. ServiceNow has shipped a lot of AI-shaped names over the last few years, and "another one just dropped" fatigue is real. But no, this isn't a rebrand or  a marketing team getting bored of "Now Assist" and reaching for a thesaurus. Something structural actually changed here, and if you're the one building on this platform, there are a couple of details buried in the announcement that are worth more than a passing skim. So let's break it down properly before Brazil comes out.

1 Assistant Instead of 3

Before ServiceNow Otto, if you were an admin (or a developer fielding admin questions), you were juggling Now Assist, Moveworks, and AI Experience as three separate AI surfaces, each with its own configuration, its own mental model, and its own corner of the platform to babysit. Three assistants, three places for users to get confused about which one to talk to, three places for you to get paged when something breaks.

ServiceNow Otto collapses that into one front door. It's the AI assistant that now shows up everywhere — Virtual Agent, EmployeeWorks, fulfiller workspaces — and it doesn't stay politely inside the ServiceNow tab, either. It shows up natively in Microsoft Teams, Slack, and Google Chat, and it handles voice, text, and multimodal input (images, forms, screenshots, the works) depending on the channel. One assistant, wherever your users already are, instead of three assistants competing for the same real estate.

 

What's Actually Running Underneath

Here's where it stops being a coat of paint. Under the hood, ServiceNow Otto is genuinely three products merged onto new plumbing:

• Now Assist: the AI skills and generative capabilities you already know
• Moveworks: enterprise search, reasoning, and a deep connector bench
• AI Experience (AIx): the multimodal layer (e.g. AI Voice Agents, Data Explorer, AI Lens, AI Web Agents)

All three now run on a new AI-native architecture. You won't see either name in the product UI; they're the internals that let ServiceNow Otto respond faster, hold multimodal conversations, and orchestrate agentic work at scale without falling over.

That architecture is fed by a few things worth knowing the names of, because you'll see them again:

• Context Engine: keeps responses grounded in what's actually true in your instance, not just what sounds plausible
• Workflow Data Fabric: pulls in live data instead of stale syncs, across 350+ connectors (Okta, Workday, SAP, and a long tail of everything else)
• AI Control Tower: logs every action ServiceNow Otto takes, so nothing happens outside of policy and nothing goes unexplained when someone asks "wait, why did it do that?"

Zoom out far enough and this is really the Sense → Decide → Act → Secure stack ServiceNow's been building toward: Sense (data — Workflow Data Fabric, RaptorDB, process mining, CMDB), Decide (AI skills, Context Engine, Knowledge Studio), Act (workflows, AI specialists, AI Agent Studio, Build Agent), and Secure (AI Control Tower, Vault, Guardian). ServiceNow Otto is the conversational layer sitting on top of all four. Now Assist was never architected to be that; it was one tile on this board, not the board itself.

 

The Part That Actually Matters to You

Okay, here's the developer-relevant headline, and it's a good one: everything you've already built is completely untouched.

Your AI agents, AI specialists, and agentic workflows still live in AI Agent Studio. You build, deploy, version, and manage them exactly the way you did last week. No forced migration, no "log in to a new admin console and re-learn where everything lives," no deprecation notice with your name on it.

What changes is upstream of you. ServiceNow Otto is the new intake layer; it takes a request in whatever form it arrives (typed, spoken, dropped in as a screenshot), figures out the intent, and routes it to the right skill, agent, or specialist. Then it hands the result back to the user, cleanly, regardless of which channel they came in on. That means the agent you shipped last quarter doesn't just keep working, it potentially starts getting hit a lot more often, because there's now a much smarter, much more available front door funneling traffic to it. And every one of those handoffs is passing through AI Control Tower's logging, so the governance story around "what did the AI just do and why" gets stronger, not weaker.

A few other things worth knowing if you're going to be the one fielding questions about this:

• AI agents ≠ ServiceNow Otto. ServiceNow Otto is the thing users talk to. Your agents and specialists are what it talks to behind the scenes. They're not being folded into ServiceNow Otto or made redundant by it — they're the actual muscle it's routing work toward.
• Two harnesses, one assistant. In EmployeeWorks specifically, ServiceNow Otto can run on either the Now Assist harness or the Moveworks harness. Customers already invested in Now Assist's admin experience can stay there; Moveworks is the recommended path going forward, though it's not yet available in every cloud/region combination. Either way, users see one ServiceNow Otto: the harness choice is an admin-side decision, not something end users need to think about.
• ServiceNow Build Agent (the autonomous agent that builds and updates ServiceNow apps for you) has ServiceNow Otto as its conversational front end too, so even the tool that helps you build things now talks to you through the same assistant.

 

When You'll Actually See This

If your org already leverages EmployeeWorks or AI Control Tower, ServiceNow Otto may already be live in your instance, quietly, without a big-bang cutover. For everyone else, it rolls out through the monthly AI release beginning in August 2026, with full availability targeted for later this year in the Brazil release.

 

Bottom Line

Now Assist didn't get a new hat. ServiceNow Otto is a genuinely new front-end brain, built by merging three previously separate AI products onto new architecture that sits in front of everything you've built and makes it more discoverable, more multimodal, and more accountable, without asking you to touch a single line of what's already in AI Agent Studio. Your agents were already the point. ServiceNow Otto just built them a much better front door.