Thanks for clarifying, RWC. I made the tweaks, but as you can see below, instead of just transferring me after two failed attempts to understand the patient, it eventually said it could connect me to a live person [but only if I told it to do so.]
Appears the AVA must have some type of context so it can "do something" with said context. I still think we need some form of "No Match" or "Timeout" setting (just like with Non-Agentic Bots/VAs) with an optional output variable that allows us to indicate the number of attempts the AVA makes to move a conversation forward before escalating out of the AVA. As helpful as AVAs want to be, we don't want the AVAs to hold customers captive while conversations to go off the rails (which mine was teetering on doing, haha).
Brian T. Jones | Ascension | Senior Specialist - Technology | Colossians 3:23-24
Original Message:
Sent: 05-19-2026 13:03
From: Robert Wakefield-Carl
Subject: Ask the Expert: LAM Powered Agentic Virtual Agents
For the escalation, best is to exit the AVA into the Bot Flow with a variable that will let the Bot Flow to follow the transfer to ACD path. I would word it like this:
Say "Sorry-I'm not able to help with that right now. I've tried to clarify twice but still don't have enough information. I'm going to transfer you to a live agent who can help. Please hold while I connect you." only after the caller has failed to provide enough information in two separate clarification attempts, or when the caller cannot describe the issue clearly enough for a third attempt to be useful. Use the set_participantdata with the input of "Agent" and escalate to a live agent.
The Comfort stuff is brand new, but I did see a difference in responses when the AVA repeats itself when turned on. I am not for sure that is the problem. Try this for the second guideline: "Ask at most two clarifying questions, but rephrase each one differently and include an example if helpful. Do not repeat the same wording or engage in small talk. If the caller still cannot provide enough context after the second attempt, set participant data and transfer to a live agent."
------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.com
https://www.ttecDigital.com
https://RobertWC.Blogspot.com
Original Message:
Sent: 05-19-2026 12:38
From: Brian Jones
Subject: Ask the Expert: LAM Powered Agentic Virtual Agents
Thanks for responding RWC. Do you have an example of how you would write the first guideline? I've rephrased that thing a dozen times, yet still get stuck in a loop with the AVA. Also, is what you're proposing reliant on the Agent Escalation feature being enabled in Architect? Asking because we don't have that enabled for a reason (i.e. agent escalations are gracefully handled by other guidelines), and in this test case an agent is not explicitly being requested--the patient is just being difficult 😉
As for your second point, yes, we have the Wait Experience enabled, but I'm unsure how/why that would conflict with the last guideline given the Comfort Statements only come into play when the AVA is using a Tool (which is not the case in my example given it never gets more than a step out of the starting blocks, haha).

------------------------------
Brian T. Jones | Ascension | Senior Specialist - Technology | Colossians 3:23-24
Original Message:
Sent: 05-19-2026 09:53
From: Robert Wakefield-Carl
Subject: Ask the Expert: LAM Powered Agentic Virtual Agents
On your first prompt, try reversing the language. Have it let the caller know they need to escalate to an agent, then tell the AVA to run the function and exit the agent with escalation.
For the second, did you enable the Wait Experience? That might conflict with that guideline.
------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.com
https://www.ttecDigital.com
https://RobertWC.Blogspot.com
Original Message:
Sent: 05-18-2026 14:57
From: Brian Jones
Subject: Ask the Expert: LAM Powered Agentic Virtual Agents
@Mitchell Mason - Hope you've been well. We're at the point where we're throwing all types of edge cases and unscripted scenarios at our AVA, and ran into something interesting. Before I explain what we've noticed, my question to you is "how would you get a conversation that is clearly going nowhere out of the hands of the AVA?" I'm thinking of something like a "No Match" path it can take after x attempts.
For example, despite [what we believe are] clear guidelines to escalate the interaction to a live agent IF the context is unclear or the conversation is not progressing, most, if not all, times the AVA holds onto the conversation asking for more clarity:
AVA: In a few words, speak your inquiry and I will help you or guide you to someone who can manage your appointment, medical questions, billing inquiries, and more. How can I assist you today?
Me: I need help
AVA: I'm here to help. Could you please provide more context or clarify what you need assistance with? This will help me better understand your inquiry and provide a more accurate response.
Me: with that thing we talked about before
AVA: I don't have any information about our previous conversation. Could you please provide more context or clarify what you are referring to? This will help me better understand your inquiry and provide a more accurate response.
Me: you know, that thing you helped me with before
AVA: I don't have any information about our previous conversation. Could you please provide more context or clarify what you are referring to? This will help me better understand your inquiry and provide a more accurate response.
Me: I don't remember, but thought you might. Can you help me?
AVA: I understand that you're trying to recall a previous conversation, but I don't have any information about our previous interactions. I'm here to help with any new questions or concerns you may have. Could you please provide more context or clarify what you need assistance with? This will help me better understand your inquiry and provide a more accurate response.
Me: I don't have additional context--can you just help me?
AVA: I understand that you're seeking help, but I don't have enough information to provide a specific response. Could you please provide more context or clarify what you need assistance with? This will help me better understand your inquiry and provide a more accurate response.
Here are the two primary Guidelines it should've been using, which ironically are the first and last Guidelines to help emphasize the importance. I wouldn't be surprised if there's a better way to write these guidelines, but figured I'd be as verbose as possible just to see what would happen.


------------------------------
Brian T. Jones | Ascension | Senior Specialist - Technology | Colossians 3:23-24
Original Message:
Sent: 05-11-2026 12:02
From: Robert Sterner
Subject: Ask the Expert: LAM Powered Agentic Virtual Agents
Genesys Education is here, along with some experts from the Genesys Product Team to share insights on LAM powered Agentic Virtual Agents, a new approach to virtual self-service that can reason, take action, and move customers toward outcomes, not just respond to questions.
Expert: Mitchell Mason - Principal Product Manager, Virtual Agent
If you're evaluating AI investments, wondering if this is right for your business, or thinking about how to get started, read on.
Q1: What's the #1 thing new users should understand about LAM Agentic Virtual Agents?
LAM Agentic Virtual Agents aren't just more conversational bots, they're designed to work toward an outcome. Instead of following a fixed flow or just answering questions, they can:
- Understand a customer's goal
- Decide what steps are needed
- Use tools and knowledge to take action
That shift, from responding to reasoning + acting, is what makes them different.
Q2: When are LAM Agentic Virtual Agents the right fit?
LAM Agentic Virtual Agents are a strong fit when a customer interaction requires both conversation and action, especially when the path isn't predictable.
Good examples:
- Checking eligibility, then applying a change
- Pulling info from multiple systems, then acting on it
- Handling requests that evolve mid-conversation
Not every use case needs this level of autonomy.
- If you mainly need Q&A from knowledge, an LLM-powered virtual agent may be enough
- If you need strict, repeatable workflows, AI Guides may be a better fit
The key question: Do you need the system to decide and act, or just respond?
Q3: What should decision makers think about before investing?
Start with the problem, not the technology.
LAM Agentic Virtual Agents work best when:
- The customer goal is valuable to automate
- The journey has enough variability that rigid flows break down
- You can clearly define what the agent should and shouldn't do
Also think about:
- What systems or data it needs access to
- What actions should stay human-led
- How you'll measure success (containment, speed, effort, etc.)
A focused first use case usually beats a broad one.
Q4: What do admins and architects need to plan for?
The experience may feel simple, but good setup still matters.
In Genesys Cloud, you'll configure:
- The agent's role and guidelines that keep it aligned to policy
- The tools it can use (actions across systems)
- The knowledge it can draw from
- The guardrails that prevent unwanted behavior
Then you connect it into Architect using a Virtual Agent flow where you can also determine additional aspects such as what information can be shared
So, the work shifts from building hundreds of steps to making smart decisions about scope, access, and boundaries.
Q5: What are some key considerations when starting with LAM Powered Agentic Virtual Agents?
Early decisions and focus areas that can shape your success:
- Start with a focused, high-value journey rather than casting too wide a net early on
- Invest in the right tools and knowledge to fully enable what the agent can accomplish
- Design with clear outcomes in mind, not just the conversation itself
- Evaluate the fit upfront to ensure LAM Agentic Virtual Agents are the right approach versus a simpler solution
Q6: Do you have a favorite tip for getting started?
Yes: design around a customer outcome, not the feature set. Pick one journey where:
- Customers struggle today
- Multiple steps or systems are involved
- Better reasoning + action would clearly help
Start there, test, refine, and then expand.
Q7: Where can learners go for more info?
Join the discussion
What are you trying to solve with AI in your organization?
- Are you evaluating whether LAM Agentic Virtual Agent is the right fit?
- Do you have a use case in mind but aren't sure where it fits?
- Curious how others are getting started?
Drop your questions below, our experts are here to help.
#GenesysCloud
------------------------------
Bob Sterner
Product Manager, Genesys Education
------------------------------