Virtual Agent topic is not triggering

ChittiS
Tera Guru

Hello Team,

I have two requirements related to the Virtual Agent configuration and would like to share a status update along with an issue I need guidance on.


Requirement 1 – Custom Fallback Message (Completed)

I have successfully configured a custom fallback message by creating a topic and associating it under the sys_cs_context_profile table using the Fallback setup topic type. When the fallback topic is triggered, it is working as expected. Please refer to the attached screenshot for reference.


Requirement 2 – Live Agent Intent Trigger (Issue)

As per AC4, the requirement is: "Given the user enters a prompt containing phrases like 'live agent' or 'request live chat' or similar, the Virtual Agent should display an information card titled 'Need to connect with support?' which provides the following support options:

  • IT Support: Chat with an IT Specialist anytime (available 24/7) or call IT Support
  • HR Support: Submit an HR Request or call the HR Contact Center during business hours."

What I have configured so far:

  1. Created a custom topic with the "Need to connect with support?" information card associated with it.
  2. Added this custom topic under the Live Agent setup topic type in the sys_cs_context_profile table (visible in the attached screenshot as "Live Agent Card").
  3. Associated the topic with the relevant LLM Assistant under "Select LLM assistants to make topics available to them and any primary assistants."

Issue:

After the fallback message is displayed, when the user types "live chat" or "live agent", the custom "Live Agent Card" topic is not being triggered. Instead, the default "Talk to an IT Specialist" live agent topic is being triggered.

Additional Context:

There are multiple live agent topics configured in the environment, each associated with both LLM and NLU. It is likely that one of these existing topics is taking priority over my custom topic, preventing it from being triggered.

Could someone please guide me on the correct steps to ensure my custom "Live Agent Card" topic is triggered when a user types phrases like "live agent" or "live chat," instead of the default live agent behavior?

Thank you in advance for your support.



ChittiS_0-1787838787296.png

 

3 REPLIES 3

kmohammed
Tera Guru

Hi ChittiS,

 

Your suspicion in the last paragraph is right, but there is a more fundamental mix-up to fix first: a setup topic is never triggered by what the user types.

 

Setup topics (the entries in sys_cs_context_profile, type Live Agent, Fallback, etc.) are invoked by the platform at fixed points in the conversation. The Live Agent setup topic runs when a live-agent transfer is initiated; the Fallback setup topic - which you already have working - runs when nothing matches. Putting the "Live Agent Card" topic into the Live Agent setup slot does not connect it to the phrases "live agent" or "live chat" in any way.

 

Typed phrases go through topic discovery instead. For an LLM assistant, discovery compares the utterance with the topics made available to that assistant, using each topic's discovery settings (topic name, description and example utterances). The default live agent topic shipped with the product already has discovery wording for these exact requests, and it is available to your assistant, so discovery selects it. Having multiple live agent topics linked to both LLM and NLU makes that overlap permanent.

 

To make the card topic the one that fires:

 

1. Allow only one live agent winner per assistant. In the assistant's topic list (Conversational Interfaces / Assistant Designer > your LLM assistant), make the default live agent topic unavailable for this assistant. You do not need to delete or deactivate it globally - availability is per assistant, so other assistants keep their default behaviour.

2. Give the custom topic real discovery of its own. In the topic's discovery settings, write the description so it explicitly covers requests to connect with a human or with support (for example: "Shows support contact options when the user asks for a live agent, live chat, or to speak to a person"), and add example utterances: "live agent", "live chat", "request live chat", "talk to a person", "connect me to support". Then publish the topic and confirm it is still assigned to the same LLM assistant.

3. Do the equivalent cleanup on the NLU side. If any NLU assistant or model is in play, the custom topic needs an NLU intent whose utterances are those same phrases, trained and published - and the default topic's intent must not be linked in that model, otherwise NLU will keep routing "live agent" to the default topic for the identical reason.

4. Keep the setup-topic configuration for the transfer itself, not for the card. The card is an information step; when the user picks the IT Specialist chat option inside it, that action should start the actual transfer handled by the Live Agent setup topic. So leave the setup slot pointing at the topic that performs the handoff, and let discovery (steps 1-2) route the typed phrase to the card.

 

One more thing about your test sequence: the Fallback topic is not blocking you. Fallback runs for the first unmatched utterance; when the user then types "live agent", that new utterance goes through discovery again within the same conversation - and that is where the default topic takes over.

 

After the changes, test in a fresh conversation and use the assistant's discovery test or preview with the exact phrases "live agent" and "live chat" - your card topic should now be the top match before you roll it out.

 

Regards,

Karimuddin

ChittiS
Tera Guru

Thanks @kmohammed 

You're welcome, ChittiS — glad it helped. Good luck with the discovery cleanup, and let me know how the retest goes if the default topic still wins.