Missed ServiceNow Knowledge 2026? Here’s the Inside Scoop on CRM

As 25,000 people landed in Las Vegas, they were greeted in the airport by ServiceNow signs reading: Go from AI chaos to AI control. Your AI Control Tower is here. That message set the tone for the week that AI adoption isn’t about rolling out natural language chatbots and automating a workflow or two. It’s about truly understanding what AI capabilities you have, how to fully leverage them, and most importantly, how to manage them across your entire enterprise as you scale.  

During the week, there were major product AI announcements and launches with a common underlying theme that AI is moving quickly past just generating insights and towards being a critical execution layer.

If you weren't able to attend Knowledge this year, we're rounding up all of the CRM product launches and announcements you may have missed, spanning Customer Service Management (CSM), Field Service Management (FSM), Sales and Order Management (SOM), and Configure Price Quote (CPQ).

‍

Every ServiceNow Customer Already Has AI, Most Just Haven’t Operationalized It Yet

One major announcement before the event even started is that AI is no longer something ServiceNow customers need to purchase separately because it’s now included with your licenses

A month before Knowledge, ServiceNow made AI capabilities included across its entire product portfolio. That means every ServiceNow customer already has access to AI-powered workflows, automation, governance, and data connectivity whether they have actively enabled them or not.

The question is no longer, “Which AI products should we adopt?”, but whether your operations, workflows, and data are connected well enough for AI to actually deliver value.

‍

The Real Problem in CRM Is Operational Coordination

One thing that was clear at Knowledge this year is that most organizations don’t actually have a technology problem, but instead a coordination issue.

It’s easy to assume CRM challenges are about dashboards, reporting, or visibility. However, when you start listening to the real operational stories companies shared at the event, the issue is almost always the same: too much work still depends on people manually stitching together disconnected systems, teams, and decisions in real time.

In reality, the stitched together process typically looks like this: when a customer issue comes in a customer service representative checks the entitlement. Another person reviews asset history. Then a scheduler and dispatcher figures out technician availability. Parts get validated somewhere else, billing adjustments happen in another system, and customer communications are managed separately on top of all of it.

To overcome a piecemealed process, one of the more interesting customer stories came from a large telco company using ServiceNow. Their team talked openly about how difficult field service coordination becomes when you’re operating across huge territories with changing weather conditions, technician skill variations, shifting customer priorities, and constantly moving dispatch schedules. Standard FSM logic simply was not designed for that level of complexity. By building custom bulk and drip dispatching logic and agentic workflows inside ServiceNow FSM, they were able to replace that manual stitching with automation that continuously adapts in real time, which is exactly what drove the outcomes they shared.

‍

From Copilots to Autonomous Execution

A lot of the AI conversation over the last year has focused on copilots helping people work faster, but Knowledge 2026 felt different.

The messaging this year was much more focused on execution.

ServiceNow demonstrated how role-based AI specialists can actually participate inside workflows, not just recommend next steps. The goal is moving toward AI agents that can coordinate work, trigger actions, manage tasks, and operate within governed systems alongside employees.

One thing I appreciated was that the conversation was not centered around ripping out legacy systems and starting over. Multiple sessions reinforced the opposite approach: many organizations need to layer intelligent automation onto the environments they already have.

Autonomous CRM: The Whole Customer Lifecycle on One Platform

You could see this operational execution theme showing up across every CRM-related announcement at the event.

Customer Service Management (CSM) 

The CSM vision focused heavily on reducing repetitive coordination work for service teams. AI agents are being positioned to triage cases, capture intent and sentiment, resolve common issues, and escalate to humans when needed while preserving customer context throughout the process. The bigger idea is not just faster case handling. It’s reducing operational friction between teams and systems.

Field Service Management (FSM)  

Field service was probably the clearest example of where ServiceNow sees AI creating immediate operational value. The FSM sessions were especially interesting because they went beyond theoretical AI discussions and showed how this actually works in practice. A global telco provider  discussed building custom “bulk and drip” dispatching logic and agentic workflows designed to continuously adapt to operational conditions in real time.

The outcomes they shared were significant:

• 90% of dispatch-related tasks automated
• 80% of manual dispatch exceptions streamlined
• Dispatch teams freed up for higher-value work
• 33% faster time-to-value

But the part that stuck with me most was not the percentages, it was the operational reality behind them.

Finding the right balance between operational efficiency and customer experience is incredibly difficult in field service. One speaker compared it to the airline industry. Airlines are notorious for maximizing efficiency by overbooking flights, but that optimization often comes at the expense of the customer experience. Field service organizations face a similar challenge every day. They are constantly trying to reduce travel time, improve technician utilization, and lower operational costs without creating friction for the customer.

That balancing act becomes exponentially harder at enterprise scale.

Weather changes. Traffic changes. Customer priorities shift. Technician skills vary. Equipment availability changes throughout the day. Trying to manually coordinate all of that in real time is where organizations burn enormous amounts of operational energy.

What ServiceNow is clearly pushing toward is AI helping orchestrate those decisions continuously inside the workflow itself, balancing operational efficiency with customer outcomes in real time instead of forcing dispatchers to manually manage the tradeoffs all day long.

Sales and Order Management and CPQ

A noticeable change at Knowledge was how connected the CRM conversation has become across the entire revenue lifecycle. Sales and Order Management (SOM) is increasingly being positioned as the bridge between quoting, fulfillment, field execution, and customer support. And after the Logik.ai acquisition, it’s clear ServiceNow sees CPQ becoming the pricing and contract execution layer that ties it all together. The direction is toward a single connected operational layer where a quote becomes an order, an order drives fulfillment, fulfillment connects to field execution, and billing closes the loop, all inside the same platform.

Governance Became a Core Theme

Another thing that stood out throughout the week was how much the AI conversation shifted toward governance and operational control. That focus makes sense.

AI inside customer-facing operations cannot behave like a black box. A bad entitlement decision, an incorrect dispatch, or a billing error creates immediate operational and customer impact.

One comment I heard repeatedly throughout the event was that organizations “can’t AI their way out of fragmented systems.”

Data Still Determines Whether AI Works

One of the most practical lessons from Knowledge was that data and workflow alignment still determine whether any of this works.

AI is only as useful as the operational context it has access to.

If service history lives in one system, asset data lives somewhere else, inventory visibility is incomplete, and workflows are disconnected, AI doesn’t solve the problem. It just scales the inefficiency faster.

Some of the strongest customer stories at the event were not flashy demos. They were operational stories about connecting systems, standardizing workflows, improving governance, and reducing manual coordination across teams.

Where Bolt Data Fits In

If you’re evaluating where to start with AI or CRM inside your own ServiceNow environment, we can help you identify where connected workflows and AI-driven execution can create the biggest operational impact. As a ServiceNow consulting and implementation partner with deep, specialized experience in this area, we can help your organization start delivering value within weeks, not months.

Schedule time with a ServiceNow expert today.