LogoLogo
  • GETTING STARTED
    • Welcome to the NLX platform
    • How NLX works
    • Guides
      • Analytics dashboard
      • Chat
      • Generative Journey (Slots)
      • Model Context Protocol
      • Voice
      • Voice+ script
      • Touchpoint components
        • Carousel modality
        • Video modality
    • Terms & concepts
    • Generative AI
    • Developer
  • Build
    • Workspace setup
    • Flows
      • Intro to flows & variables
      • The Canvas
      • Flow settings
      • Nodes
      • Flow appearance
    • Resources
      • Actions
        • Implementation
        • Request model
      • Analytics tags
      • Context variables
      • Data requests
        • Implementation
        • Response model
        • Request model
      • Knowledge bases
        • Ingest content
        • Add metadata (beta)
        • Apply KB
      • Lifecycle hooks
        • Implementation
      • Modalities
      • Secrets
      • Slots (custom)
        • Adding values
        • Translating slots
      • Voice+ scripts
        • Add + download script
        • Deploy script + install SDK
        • Create Voice+ flow
    • Integrations
      • Channels
        • Alexa
        • Amazon Chime SDK
        • Amazon Connect
        • AWS End User Messaging SMS
        • AWS End User Messaging Social
        • Bandwidth
        • Genesys
        • Twilio
        • Zendesk Sunshine
      • LLM services
        • Amazon Bedrock
        • Anthropic
        • Azure OpenAI
        • Cerebras
        • Cohere
        • Google Vertex AI
        • Groq
        • NVIDIA
        • OpenAI
        • xAI
      • NLP
        • Amazon Lex
        • Google Dialogflow
        • Google Dialogflow CX
        • Custom NLP
    • Translations
  • Deploy & test
    • Applications
      • Attach flows
      • Assign default behavior
      • Add channels
        • API
          • REST API
        • Alexa
        • Amazon Chime SDK
        • Amazon Connect
        • AWS End User Messaging SMS
        • AWS End User Messaging Social
        • Genesys
        • Genesys SMS
        • Messenger
        • Microsoft Teams
        • Slack
        • SMS via Bandwidth
        • Twilio SMS
        • Twilio Voice
        • WhatsApp via Twilio
        • Zendesk Sunshine
      • Deploy
      • Optional: Set lifecycle
      • Optional: Set languages
    • Test
      • Test a conversation
      • Automated tests
      • Test an external integration
  • Analyze
    • Conversations
    • Analytics
      • Creating dashboards
      • Formulas & multi-metrics
      • Canvas analytics
    • Training
  • Workspace Settings
    • Escalation channels
    • Resource tags
    • Audit
  • Admin
    • Access control
      • Roles & permissions
    • Notifications
    • FAQ
    • Contact support
Powered by GitBook
On this page
  • What's the Default behavior tab of an application?
  • Required default behaviors
  • Optional behavior types
  • Quick reply vs flow
  1. Deploy & test
  2. Applications

Assign default behavior

Learn how to adjust the out-of-the box behaviors for your conversational application in your NLX workspace

Last updated 1 month ago

What's the Default behavior tab of an application?

Default behaviors define which conversation flows the application should follow in specific situations. This includes how the conversational AI application initially greets the user as well as how it responds to technical issues or unknown user responses.

Flows assigned to handle these behaviors must first be attached to your application through the application's .


Required default behaviors

Open the application you wish to edit and select the Default behavior tab. A few behavior types that are always enabled for an application include:

  • Welcome: What your application follows when a conversation session is initialized


Optional behavior types

Optional behaviors are disabled by default, but you may enable and edit these for your conversational AI:

  • Help: When a user expresses they are in an emergency situation

  • Frustration: When a user expresses frustration

  • Escalation: When an escalation process is triggered

  • Repeat: When a user requests the last message be repeated

  • Resume: When a user requests a pause before continuing the conversation

Optional behaviors are handled by Fallback behavior when not turned on.


Quick reply vs flow

For most behavior types, you may toggle between a built-in quick reply or custom flow.

Quick replies allow you to enter the phrase the conversational AI delivers to the user in a particular situation.

At least one phrase is required for the behavior to work in this mode. Additional phrases can be added for variety by choosing Add quick reply. You can remove a phrase by clicking on the remove icon.

The Flow option allows you to bypass quick reply responses and instead point to a workflow created within your workspace.

When the toggle field is set to Flow, you may choose a flow from those attached to the application that best handles the situation.

Fallback: What your application follows during timeouts, integration failures, and exceeding the number of permitted

Unknown: What your application follows when incomprehension occurs (inability to understand the user's response). You may assign a from your workspace to the Unknown default; this allows your application to check the knowledge repository for a response to a common question without the need for a dedicated intent flow.

NLX provides quick reply phrases, but it's recommended that you create custom for handling all mandatory behavior types.

Knowledge base
flows
Flows tab
incomprehension events
Required behaviors for an application