LogoLogo
  • GETTING STARTED
    • Welcome to the NLX platform
    • How NLX works
    • Guides
      • Analytics dashboard
      • Chat
      • Generative Journey (Slots)
      • Model Context Protocol
      • Voice
      • Voice+
      • 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
  • Test & Deploy
    • 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 are custom Slots?
  • Requirements
  • Slot features
  • Slot settings
  1. Build
  2. Resources

Slots (custom)

Provide choices and direct conversations more efficiently using custom slots with NLX

Last updated 26 days ago

What are custom Slots?

Slots are variable pieces of information needed to fulfill a user's intent. For example, in "I want to book the deluxe room," deluxe is a slot representing the room type. Custom slots have a limited range, can be tailored to your business, and may also appear as clickable options in chat applications.

Examples:

  • Yes / No (Boolean)

  • Small / Medium / Large

  • I want to signup / I want something else

Standardized slots, such as time, freeform text, date, email, etc., are available as and are accessed when attaching slots to your flow.

To access, click Resources in your workspace menu and choose Slots:


Requirements

A custom Slot must always employ the following to function:


Slot features


Slot settings

A Slot's Settings tab provides a few options:

  • Description: Enter or modify an explanation of the resource for better filing and organization in the workspace

  • Sensitive: Prevents the slot's values from being stored in conversation logs

  • Transient: Does not retain slot value through duration of conversation. For example, Yes/No slot values may be reused in a conversation, so enabling this setting prevents retention of the value and potential auto-traversal through a flow

  • Static: Restricts the NLP to only match user responses against the values defined for the slot. If you do not know all possible values, you may disable this setting, allowing the NLP to expand its matching algorithms beyond the values provided

Tags: Add or remove for better filing and organization in the workspace

To delete a custom Slot and all of its values, select the Delete option under Danger zone. If the Slot is attached to an intent(s), create a to experience the change.

Adding values
Translating slots
Resource tags
new application build and re-deploy
built-in slots
attached to a flow