Genesys Cloud - Developer Community!

 View Only

Sign Up

  • 1.  AVA end context

    Posted 10 hours ago

    Hi everyone,

    I understand that end context variable has to be either from tool or start context. When I create it as a start context variable, and I want AVA to set it's value during the conversation, it is always NOT SET. How do I make the AVA populate the end context purely from the conversation or is that not possible?

    Thank you!


    #Architect

    ------------------------------
    Marija Kovrlija
    NA
    ------------------------------


  • 2.  RE: AVA end context

    Posted 8 hours ago

    Hi Marija,

    From my understanding, AVA cannot arbitrarily populate End Context variables purely from the conversation unless the value is explicitly mapped from either:

    • a tool/action result
    • or an existing Start Context variable

    The conversational reasoning itself does not automatically persist values into End Context.

    So if you create a Start Context variable and expect the AVA to dynamically assign/update it during the conversation without a tool/action involved, it will typically remain NOT SET.

    In practice, the common pattern is:

    • collect/extract the information during the conversation
    • pass it through a tool/action
    • map the returned value into the End Context variable

    At the moment, I don't believe there is native support for directly persisting arbitrary conversational state into End Context variables without that intermediary mapping/action step.



    ------------------------------
    Gabriel Garcia
    NA
    ------------------------------



  • 3.  RE: AVA end context

    Posted 8 hours ago

    Hi Marija,

    From my understanding, AVA cannot arbitrarily populate End Context variables purely from the conversation unless the value is explicitly mapped from either:

    • a tool/action result
    • or an existing Start Context variable

    The conversational reasoning itself does not automatically persist values into End Context.

    So if you create a Start Context variable and expect the AVA to dynamically assign/update it during the conversation without a tool/action involved, it will typically remain NOT SET.

    In practice, the common pattern is:

    • collect/extract the information during the conversation
    • pass it through a tool/action
    • map the returned value into the End Context variable

    At the moment, I don't believe there is native support for directly persisting arbitrary conversational state into End Context variables without that intermediary mapping/action step.



    ------------------------------
    Gabriel Garcia
    NA
    ------------------------------



  • 4.  RE: AVA end context

    Posted 8 hours ago

    Agree with @Gabriel Garcia, currently no method to achieve this other than what Gabriel mentioned. Out of curiosity, what prompts have you tried to achieve this?



    ------------------------------
    Savino Ricci
    Senior Technical Consultant
    ------------------------------



  • 5.  RE: AVA end context

    Posted 8 hours ago

    Thanks Savino.

    I tested a few variations trying to make the AVA persist the value directly from the conversation itself, something like:

    • "Store the customer account number into variable X"
    • "Update the end context variable with the collected value"
    • "Persist this information for Architect output"

    I also tried reinforcing it through role/guideline instructions and confirmation steps during the conversation, but the End Context still remained NOT SET unless the value came back from a tool/action mapping.

    So from what I could validate, prompts alone do not seem enough today to persist values into End Context variables.



    ------------------------------
    Gabriel Garcia
    NA
    ------------------------------



  • 6.  RE: AVA end context

    Posted 8 hours ago

    Ok, so I need a "dummy" tool to achieve this. Thank you! that was my current workaround but wanted to check if I am missing anything. Thank you Gabriel.
    Savino, I tried with: Once the value has been identified populate the custom_field variable with the result. Or "immediately set custom_field to Emergency and transfer to an agent", but saw they are not populating no matter the description, nor did it say in the documentation it can be done. Thank you!



    ------------------------------
    Marija Kovrlija
    NA
    ------------------------------