Trigger Words

Following trigger words are supported by default in the platform (see here for multi-lingual support):

Invocation Names

The Linked bot’s name is considered as an implicit invocation name.

Apart from this, you can define one or more Invocation Names for each of the linked bots. These will be treated as a special set of synonyms defined against linked bot names and the bot users might be using these when referring to the linked bots.

Utterances

Training utterances refer to the typical ways in which the users are expected to ask for intent from a linked bot. This usually includes the key training utterances used for training the intents of the linked bots. Keep in mind unlike the ML training, these utterances can identify multiple linked bots not zero it on one.

You can add up to 500 training utterances.

You can also use the Copy from linked bot option to choose and add the utterances from the linked bot.

From the Linked Bot listing page, you can get an overview of their training status and invocation names, and training utterances.

Exit Phrase

Following trigger words can be used by the user to exit from an exclusive context of a linked bot.

• Exit

None Intent

The None Intents are used to qualify/disqualify the linked bots based on user utterances defined in them. The None intent is a placeholder that prevents the Machine Learning model from identifying the wrong intent for untrained or ambiguous utterances. For more information, see None Intent and Creating a Universal Bot articles.

Configurations

For each linked bot, you can set the Bot Qualification Threshold as the minimum score needed to qualify the bot for the intent identification process.

By default, it is set to 0.3 and can be set to any value between 0 and 1.

Fallback Bots

You can mark certain bots as fallback bots which would be used for detecting intents when no other bots are identified from other training options.

Points to note:

• A maximum of 15 bots can be marked as Fallback Bots
• You can change the list of preferred bots at any time to suit the business needs

Inclusive Bots

Inclusive bots need not be trained with sample utterances to participate in the bot scoping process. These bots will always be considered for Intent Detection at the time of evaluating the user utterances, except when the user invokes a linked bot either using ‘Invocation Phrases’ or ‘Trigger Phrases’.
Up to 3 linked bots can be marked as inclusive bots.

Note: A linked bot can be marked either as Fallback or Inclusive not both.

Linked Bots

The information related to the in-context linked bot would be available in the Session context under the following key:

• currentLinkedBotid for Linked Bot ID;
• currentLinkedBotName for Linked Bot name.

Eligible Bots

As Universal Bot developer you have the ability to assign specific bots to specific end-users so that only the intents from these bots are made available to them.

The following functions can be used in relation to eligible bots:

• To get the list of currently eligible bots for the given user context:
  UserContext.getEligibleBots()
• To set the eligibility bots:
  UserContext.setEligibleBots(["st-linkedBot1","st-linkedBot2"])
  where st-linkedBot1, st-linkedBot2, etc. are the bot ids of the linked bots (obtained from Setting -> Config Settings -> General Setting)
  This function will replace the current eligible bots with the ones given.
• To remove the list of currently eligible bots for the given user context:
  UserContext.removeEligibleBots()

You can set the eligible bots based on the user authorization or any other approach that your organization may have in place.

You can also define the bot behavior when the bot assignments are not provided, from the settings, see below.

Settings

The configuration settings can be accessed from the Build top menu tab, left menu, under Natural Language -> Settings

Following configurations are to be provided in the Bot Builder so that you can configure these thresholds:

• Use of Bot Synonyms – toggle to enable or disable the use of bot synonyms in intent detection. Disabled by default.
• ML threshold to define the minimum ML score to qualify an intent as a probable match can be set to any value between 0 and 1. The default setting is 0.3.
  Post v8.1, this setting has been replaced with Bot Qualification Threshold for each linked bot, see above.
• Switch to Older Version can be used to switch to an older version of Universal Bots. See here for details.
• Trigger Phrases can be used to allow users to trigger linked bots using Trigger Phrases i.e. without specifying the intent. Once enabled you can define the bot behavior to
  • display the Welcome message defined in the linked bot, or
  • show a custom message. Use Manage response to define the message to be displayed.
• Recently Used Bots setting can be used to refine the scoping linked bots when no linked bot is identified from training data. The Bot can be configured to remember up to 5 recently used by the user.
  
• Intent Rescoring can be used to define Universal Bot behavior while handling the linked bot intents. By default, the universal bot rescores the intents received from the linked bots to identify the winning intents. This intent identification process depends on the training provided both at the UB and the linked bot. But if the universal bot is not trained properly, rescoring might lead to wrong intent identification. You have an option to disable the intent rescoring for winning intent identification. The setting (introduced in ver8.0) can be:
  • Rescore the qualified intents to find the best possible match – this is the default selection and you can further configure
    • The proximity of Probable Matches to define the maximum difference allowed between top-scoring and immediate next possible intents to consider them as equally important. It can be set to a percentage between 0 and 20. The default setting is 2%.
  • Present all the qualified intents to the end-user for selection – this would present the list of ambiguous intents to the user if multiple definitive or/and probable matches are returned from one or more linked bots. If only one intent is returned by a single linked bot then that intent is executed.
• Bot Assignment Behaviour can be used to define the behavior when the eligible bots are not set for a given user (see here). The setting can be:
  • Assign all Child Bots: All linked bots are eligible. This is the default setting.
  • Do not Assign any Child Bot: The user is not eligible for any of the linked bots.

  

  If your bot is trained in one or more languages that use NLP Version 2, you will see a banner notifying you about the upcoming auto-upgrade to NLP Version 3.

Implementation

Let us look at how the Universal Bot works.

The universal bot processes user input in multiple stages to identify appropriate bot and invoke the appropriate intent.

Stage 1 – Scoping of Bots

Users should be able to use trigger phrases like “Talk to Salesforce”, “Ask Eva” (Eva being HR bot), or patterns like “Schedule a meeting” or “add a task” to invoke the linked bot.

• The user utterance (invocation phrase) is evaluated for linked bot name (invocation name).
• This bot name is compared with all linked bot names or eligible bot names (in case eligibility criteria for the user is defined) to shortlist one or more scoped linked bots.
  Bot Eligibility: Different users may have access to a different set of bots/skills based on their role or association with teams, in the organization. Using the restricted scope, the universal bot will be able to identify more appropriate bot based on the user’s access controls.

Stage 2 – Fork input to linked bots

Once a set of bots have been scoped, the user input is sent to all the in-scope linked bots. The ranking of intents from each of the linked bots is accumulated and further evaluated.

• The utterance is sent to the scoped linked bots for intent identification.
• Identified intents are then forwarded back to universal bot’s ranking and resolver for further evaluation and action.

Stage 3 – Ranking and Disambiguation

Response from the linked bots is ranked and, if more than one bot is qualified for user input, disambiguated using additional context. If not possible then disambiguation dialog is presented to the bot user.

Stage 4 – Invoke fulfillment

• The winning intent is executed.
• In the case of no winning intent:
  • the universal bot is checked for matching small talk intents.
  • the Fallback bot is executed.

Next Steps

• You can also look into how the Universal Bot can be customized by defining the default dialog and variables from here.
• Learn to enable additional languages from here.