Leopard Chat Client
  • Quick Start
  • Screenshots
  • Setup
    • Extension Helper
    • Context Variables
      • Greeting Message
      • Channel
      • User's Time Zone
      • Location Context Parameters
    • Build Variables
  • Content Styling
    • CSS Styles
    • Icons
    • Markdown & HTML
  • Components Simple Syntax
  • Components
    • Answer Borders
    • Audio Player
    • Auto Open Leopard with Link
    • Alerts
    • Buttons and Lists
    • Card
    • Response Icons
    • Date & Time Pickers
    • Emergency Button
    • Expensive Operations
    • Field Masks
    • Chat Field Types (Email, Password, Location, Upload)
    • Forms
      • Feedback Form
      • Custom Forms
        • Example Config
        • Postback Object
        • Button Object
        • Field Types
        • Style Object
        • Icons Object
        • Masks
        • Validation
    • Google Map
    • Help Text
    • HTML Modal
    • Hyperlinks
    • Images
      • Image
      • Image Carousel
    • Tables
      • Tables - Simple
      • Tables - Advanced
    • Theme Change
    • Toasts
    • Language Auto Switch
    • Minimize Chat after Delay
    • Multiple Components - Same Response
    • Modal Size & Positioning
    • Open Long Response in Modal
    • Print Icon
    • Prompt Trigger Polling
    • Splitting Answers - Chunks
    • Video Player
  • Administration Area
    • Solution Configuration
    • Demo Mode - iFrames & URLs
    • ASR and TTS
  • Integrations
    • Logging / Reporting
    • Social Authentication
    • Live Chat
  • Embedding / Production
Powered by GitBook
On this page
  • Output Parameters
  • Additional Output Parameters
  • Language Condition
  • Screenshot
  1. Components

Language Auto Switch

Leopard can be told to switching to another language solution's Teneo Interaction Engine (TIE) URL based off NER Language Detection.

PreviousToastsNextMinimize Chat after Delay

Last updated 4 years ago

Although this functionality in Leopard was created to showcase the ability to switch solutions based off the spoken language of the user it could just as well be applied in alternative scenarios.

For instance maybe you have separate Teneo Solutions that handle different domains of knowledge. If a classifier in one solution knew that the user's question related to something in another solution then a switch could be triggered.

Output Parameters

To tell Leopard that a switch needs to occur you must define a couple output parameters in the Source Solution.

langinput = User input text you want to send to the new Teneo Runtime URL

The language Input will usually be the captured user input that triggered a flow that looks for alternative languages spoken. 

langengineurl = the new target Teneo Interaction Engine URL

With both of these output parameters Leopard will automatically make a request to the new TIE url and it will pass the text found in the langinput output parameter as the user input. For the remainder of the user's session, Leopard will continue to communicate with the new TIE server.

If you want the Leopard UI to show labels in the respective language then you mush specify the following output parameter.

lang=en/es/de/nl/fr/ru

To have the Leopard UI load a different Iframe for the new language solution then specify the URL as an output parameter.

langurl=https://some-new-url.es/

If you have the Amazon Polly voices enabled you will need to send an output parameter that instructs Leopard to switch the voice.

voice=Ruben

A list of available Amazon Polly voices can be found here:

Additional Output Parameters

You can control not just the new target iframe url and TIE url but also the Leopard Chat Title and locale for UI labels and ASR and TTS.

Language Condition

%$RU.LANG:{lob.confidence>0.78}

Screenshot

https://docs.aws.amazon.com/polly/latest/dg/voicelist.html