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
  • Step 1: Phone number setup
  • Step 2: Create Twilio Voice channel in NLX
  1. Deploy & test
  2. Applications
  3. Add channels

Twilio Voice

Learn to set up a Twilio Voice communication channel for your application in your NLX workspace

Last updated 16 days ago

The Twilio Voice channel requires ain your workspace before a channel can be created.

Step 1: Phone number setup

To allow for full control, a phone number for your voice flow is managed within your Twilio account. Each flow is tied to one phone number, but you can provision multiple phone numbers for a single Twilio workspace.

To assign a number:

  • Go to the Phone Numbers section of your Twilio account

  • Select Manage > Active numbers

  • Go to the details for one of your Active numbers

  • In the Voice & Fax section, manually set the incoming call configuration to Studio Flow and assign the flow that was auto-created for that application


Step 2: Create Twilio Voice channel in NLX

  • Navigate to Channels tab of your application

  • Expand Twilio Voice option

  • Click + Create channel

  • Choose your from the Integration dropdown

Optional:

  • Custom conversation timeout: Allows you to specify the time (in minutes) when a conversation will time out

  • Escalation: Select from an escalation integration set up under your workspace Settings for optional agent transfer. Agent escalation is not managed within NLX. You may customize this in your Twilio Studio account, which can be controlled by the "Send to Flex" widget found in each Twilio Studio Flow that's automatically created during deployment. The NLX application sends the appropriate action to Twilio, and it will respond accordingly.

  • Twilio Fulfillment Lambda endpoint: Allows you to override the Fulfillment Lambda set in the Twilio integration. This is needed to deploy an application that can escalate to Twilio Voice and is pulled from the channel if it is there. Otherwise, it is pulled from the integration. Setting it in either of these is required to deploy a voice application. If neither is set, then the deployment will fail

  • Click Create channel

Due to your one-time integration at the workspace level, whenever your application is deployed in NLX, a default flow is auto-created in your Twilio Studio account. This flow is created for every application you deploy. The deployment creates the initial default flow; however, if you wish to make further customizations, be sure to make changes in both NLX and Twilio Studio flows.

one-time integration
Twilio workspace integration