The configuration YAML defines a dictionary of (key, value) pairs that contain definitions both for SAL templates and Entity Data Types as described below. Also, Imports and Lookups are configured within the same Configuration YAML.

Defining SAL templates

Templates are defined with key templates within a “Literal Block Scalar”:

templates: |
  SAL line 1
  SAL line 2
  ...  

Defining Entity Data Types

Entity Data Types are defined with key entities that has a list of (name, type) pairs as its value:

entities:
 - name: entity1_name
   type: entity1_type
 - name: entity2_name
   type: entity2_type
   ...

Example configuration YAML

This is a simple example that shows what a complete configuration YAML with entity types and templates looks like:

entities:
 - name: product_name
   type: string
 - name: product_amount
   type: number
 - name: delivery_date
   type: date_future
templates: |
  product = [apples | oranges | bananas | grapefruits | mangoes | apricots | peaches]
  amount = [1..99]
  *add_to_cart {add} $amount(product_amount) $product(product_name)
  *set_delivery_date [{schedule} delivery for | delivery on] $SPEECHLY.DATE(delivery_date)  

Advanced settings

There are a number of advanced settings you can use to alter the behavior of your application. These settings are also available in the Dashboard by going to Application > Settings.

silence_triggered_segmentation: <number>

Duration of silence in milliseconds that creates a new segment. Defaults to 0, which means that a new segment is never triggered due to silence.

fast_intent_detector: <boolean>

When enabled, the system tries to detect intents faster at the cost of accuracy. Default false.

enable_strict_nlu: <boolean>

Experimental: when enabled, the systems guarantees that if an utterance is present in the configuration, it should be tagged with greater accuracy. Default false.