Documentation / Telephony Integration
Telephony Integration
Connect voice agents with telephony providers for inbound calls
Overview
Tigy AI's telephony integration provides a unified interface for connecting supported providers and routing inbound calls to your agents.
Supported Providers
Industry-leading cloud communications platform with global reach
Receive calls through Telnyx Call Control
Receive VoIP calls through the SIP number assigned to an agent
Configuration
All telephony providers are configured from a single page in Tigy AI:
- Navigate to /telephony-configurations and click Add configuration
- Select your provider
- Enter your credentials and save
- Open the new configuration and add at least one phone number
- (Optional) Assign an Inbound agent to a phone number to enable inbound calling
A single workspace can hold multiple configurations and multiple phone numbers per configuration. Assign an inbound agent to each number that should receive calls.
Common Features
The telephony integration in Tigy AI supports:
- 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:
https://api.tigyai.com/api/v1/telephony/inbound/run
Tigy AI resolves the org from the webhook's account credentials and the agent from the called number's Inbound agent assignment. See Inbound Calling for the full setup.
Troubleshooting
Calls not connecting
- Verify credentials are correctly configured
- Check phone number format ([E.164](https://en.wikipedia.org/wiki/E.164) — the international standard: a `+`, then country code, then the number, no spaces or dashes, 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 Tigy AI configuration
- Verify webhook URL matches exactly (including the `/inbound/run` path)
- Check for proxy or load balancer modifications
