Virtual Agent with agentic reasoning in the October release, and what it means for you

@Victor Chen , the KB article you've linked (KB2548818) is restricted and cannot be viewed even after logging in to support.

@qprinsloo - try again? (You must be a customer in Now Support to view this KB.)

I'm logged in as a customer...

I logged in, but KB is still not visible. showing error "Your role does not grant you access to this article. Please use Search to find related content."

We'll look into this. In the meantime, the article has been updated with specific performance improvement stats!

@anand9 can you please try again? 

@LohitYogi - same error:- 

What are the other changes in Zurich patch 2. My custom Agentic AI had a accuracy of 80% on patch 1, which is significantly dropped to <50% immediately after moving to patch 2, and I am kinda frustrated having trust issues (instead of having better performance and accuracy, I am getting issues and have no idea where to look) - I am not using VA yet. Now sure what was the changes in patch 2, but How do I revert to what was there in patch 1? 

I am also not having access to this KB Article although I am logged-in with my customer account.

@anand9 can you share more about the details of what is "My custom Agentic AI" and if you submitted a case on the issue?  would love to hear more on the challenges and how we can improve .   

@Eric Merkle - I am developing a custom Agentic AI, where good amount of the AI instructions are being picked from article (as it is not a good idea to keep a lengthy instruction in workflow, and also it gives a customer chance to modify the instruction later if required).

The Agentic AI is related to CSDM, where I am defining some definitions in article. For example, in Article, I have mentioned Application service, service instance and deployed instance are the same thing.

Zurich Patch 1 - when user wants anything to do with service instance, or deployed instance, Agentic AI would pick the right AI Agent and execute the workflow (most of time).

Zurich Patch 2 - Immediately after upgrading my instance to patch 2 - same question from user on service instance, or deployed instance, is triggering irrelevant AI Agent.

I have been following "AI Agents Prompting Guide" uploaded by Victor few weeks back - and I am sure there's nothing wrong with instruction, and yet, I am helpless why workflow is picking wrong AI Agent. Nothing valuable I see in Decision log as well. It was almost working before upgrade, now I am afraid to do any changes in instruction, as it would break something else.

Did I raise ticket - NO - because I have raised similar ticket (CS8200183) in past, and it was straight rejected due to the fact that it was a "custom" AI Agent, even though the case agent agreed that the provided instructions are good, but system behavior is not. So, I am sure they will reject it again. 

There are other non-consistent issues (occurred before patch upgrade as well) in how AI Agent works, but for now I am trying to fix the issue occurred after the upgrade. 

so the discovery of the AI agent with the same intent now seems to be a issue from ZP1 to ZP2 ? I'll share with the team 

@anand9 Could you pls create a case, it would be hard for me to understand what your end to end scenario is and what is not working upgrading to ZP2. 

We can get more context through case, like you have upgraded to ZP2 and Oct version of store apps as well. Are you testing through VA, NAP or playground in Agentic Studio etc. How you are developing agents that picks up instructions from KB, how are you making those available to Agentic platform. Why can't you put instructions in worlflow/agent itself, anyone should be able to change those by going into workflow/agents. 

@Eric Merkle , @sriii1 - created CS8662226 with required details.

thanks the team will look into it 

The KB (KB2548818) still isn't available will this be resolved or is there a different KB link

Hi,

The latest update definitely brings in faster performance but we noticed the conversational experience where there follow-up questions if VA is unable to understand the intent of the query is now gone.

An example prompt: I want to install software

Before this release: There would be follow-up questions to verify which software the user would want to install 

After this release: We noticed the bot would try to answer the question straight-away

Is there a way to decrease the 'temperature' to make it ask follow-up questions to understand the intent before responding? 

Hi @anand9, @MikeJ1, @qprinsloo, @himmat10005, and everyone else who might be reading this!

I think the knowledge article @Victor Chen linked to was hard-coded to a specific version (sys_id) of the KB, and it's probably been revised a few times since - so the previous version is no-longer available. Here's a link to the latest version of the knowledge article using the number: KB2548818. At least it worked when I tried it! (3:39pm Eastern time on 17 Nov, 2025). For reference, I am a customer with access to ServiceNow Support.

Hope this helps!

Mitch

Thanks @Mitch Fleischm1 - I've likewise updated the URL in the article.

@ayman_h - Hi, you're correct to point out disambiguation behavior changed. In the latest patch, we now only ask follow-up questions if the query is very unclear/one-worded. That aside, there is no way to change the behavior. We may be looking into further improvements into how this looks. 

@Victor Chen 

Regarding this info in your post - AI Agents are prioritized in Virtual Agent responses by default, but this is configurable via a system property - sn_aia.use_agents_in_planner

When was the system property - sn_aia.use_agents_in_planner made available for configuration to turn on/off the AI Agents access from NA?

In earlier releases I think this property was used to prioritize AI Agent vs KBs, Catalog items content from the defined data sources/search profile content.

Please clarify

Thank you!