Telephony Integration

Connect voice agents with telephony providers for inbound and outbound calls

Overview#

Paladin AI's telephony integration system provides a unified interface for connecting with various telephony providers. The same configuration powers both outbound calls (initiated from Paladin) and inbound calls (received on a phone number you own).

Supported Providers#

Configuration#

All telephony providers are configured from a single page in Paladin:

  1. Navigate to /telephony-configurations and click Add configuration
  2. Select your provider
  3. Enter your credentials and save
  4. Open the new configuration and add at least one phone number
  5. (Optional) Assign an Inbound workflow to a phone number to enable inbound calling

A single org can hold multiple configurations (for example, separate Twilio sub-accounts) and multiple phone numbers per configuration. Mark one configuration as the default outbound to use it for test calls and campaigns by default.

Common Features#

The telephony integration in Paladin AI supports:

  • Outbound Calls: Initiate calls to any phone number from a workflow or campaign
  • Inbound Calls: Route incoming calls to the right voice agent — see the Inbound Calling guide
  • Call Transfer: Transfer an in-progress call to a human or another number (provider-dependent)
  • Call Status Tracking: Monitor call lifecycle events (initiated, ringing, answered, completed, failed)
  • WebSocket Audio Streaming: Real-time, bidirectional audio between caller and agent
  • Webhook Signature Verification: Inbound webhooks are verified against the matched configuration's credentials

Inbound Calling#

Inbound calls use a single org-wide webhook URL:

text
https://app.paladin.northmanngrp.com/api/v1/telephony/inbound/run

Paladin resolves the org from the webhook's account credentials and the agent from the called number's Inbound workflow assignment. See Inbound Calling for the full setup.

Troubleshooting#

Calls not connecting
  • Verify credentials are correctly configured
  • Check phone number format (E.164 with country code, e.g. +1234567890)
  • Ensure webhook URLs are publicly accessible
  • Review provider-specific error logs
Audio quality issues
  • Check network bandwidth and latency
  • Verify audio codec compatibility
  • Review WebSocket connection stability
Webhook signature validation failing
  • Confirm auth tokens / API secrets match between provider and Paladin configuration
  • Verify webhook URL matches exactly (including the /inbound/run path)
  • Check for proxy or load balancer modifications

Next Steps#