Connect your Telnyx number to Kipps.AI voice agent for Outgoing calls

Introduction

Connecting your Telnyx number to a Kipps.AI voice agent lets your AI place outbound calls on your behalf — appointment reminders, lead follow-ups, order confirmations, and other proactive outreach — using natural, two-way conversation rather than a pre-recorded blast. Because Telnyx exposes SIP trunking directly, outbound integration involves a few more fields than an incoming setup: you'll be configuring a SIP trunk connection between Telnyx and Kipps.AI, not just pointing a webhook.

This guide is for teams that already use Telnyx and want their Kipps.AI voice agent to initiate calls rather than only answer them. Outbound calling is a fundamentally different flow from inbound — instead of a caller reaching you, your agent reaches out — and it carries real operational and compliance responsibilities that don't apply to inbound. We cover both the setup and those responsibilities below. If you're looking to route calls customers place to you, see our incoming-calls guide instead.

Prerequisites

• An active, funded Telnyx account. Outbound calling draws down your Telnyx balance per minute, so billing needs to be current and topped up.
• A Telnyx number with outbound voice and SIP trunking enabled. Not every number configuration supports origination out of the box — confirm SIP trunking is active for the number you intend to use.
• A Kipps.AI account (sign up here) with a voice agent built for the outbound use case — the script, tone, and objective (reminder, follow-up, survey, etc.) should be configured and tested in the simulator before it starts placing live calls.
• Your Telnyx SIP trunk credentials — the termination SIP URI, trunk username, and trunk password — which you'll need on hand to complete the Kipps.AI side of the configuration.
• A calling list and a clear campaign purpose. Outbound calling only works well when the list is accurate, deduplicated, and the reason for calling is legitimate and expected by the recipient.
• Awareness of consent and calling-hour rules in the jurisdictions you're calling into — covered in more detail in Best Practices below.

How to Get Started with Telnyx Outbound Calls on Kipps.ai

Step 1: Log in to Kipps.AI

Log in (or sign up) at Kipps.AI.

Step 2: Select or create your voice agent

Select an existing voice agent, or create a new one, to integrate with your Telnyx outbound number.

Make sure the agent's conversation flow is built specifically for the outbound scenario — an outbound reminder call needs different opening lines and objection handling than an inbound support call.

Step 3: Go to the Phone Number section

Step 4: Click "Connect phone number"

Step 5: Enter a nickname and your Telnyx number

Use a nickname that identifies the campaign or purpose (e.g., "Appointment Reminders — Telnyx"), since outbound numbers are often tied to specific use cases.

Step 6: Save the telephony integration

Step 7: Copy the Kipps SIP URI

This URI is what allows Telnyx to route your outbound calls into Kipps.AI. You'll paste it into your Telnyx SIP trunk configuration in a later step, so keep this tab or value handy.

Step 8: Enable outbound calls

Step 9: Fill in the termination URL (SIP URL)

This is the same SIP URI you copied in Step 7.

The termination URL tells Telnyx where to send the call once your agent initiates it — getting this exact string right is the single most common point of failure in outbound setup.

Step 10: Fill in the SIP trunk username

This is the credential Telnyx issued when you created your SIP trunk — find it in your Telnyx portal's SIP trunking settings.

Step 11: Enter the SIP trunk password

Treat this credential like any other production secret — don't share it outside the people configuring this integration.

Step 12: Enable outbound SIP

Once enabled, your agent can place calls through this Telnyx number. Run a small batch of test calls to your own phones before pointing the agent at a real calling list.

Troubleshooting

• Outbound calls fail to place at all. Double-check the termination URL matches the Kipps SIP URI exactly, and confirm the SIP trunk username and password were entered without extra spaces or characters.
• Calls place but disconnect immediately. This often points to an authentication mismatch on the Telnyx side — verify the SIP trunk credentials are current and haven't been rotated or revoked in the Telnyx portal.
• Calls connect but there's no audio, or audio only flows one way. Usually a codec or network path issue between Telnyx and the receiving carrier. Test from multiple destination numbers and networks to isolate whether it's specific to one carrier.
• High call failure rate to a specific region or carrier. Some carriers apply spam or robocall filtering to high-volume outbound traffic. If a specific destination consistently fails, check Telnyx's delivery reports for that route.
• Calls are being placed but recipients report caller ID as "Unknown" or "Spam Likely." This is a carrier-side reputation issue tied to your Telnyx number's calling patterns, not a Kipps.AI configuration problem — consistent, expected calling patterns (rather than sudden high-volume bursts) generally help over time.
• SIP trunk shows connected in Telnyx but Kipps.AI can't place calls. Confirm outbound SIP is toggled on in Step 12 — this is a separate switch from simply saving the trunk credentials.

If problems persist, contact kipps.ai/contact-sales with your account details and a sample of failed call timestamps.

Best Practices

• Start with a small test batch, not your full list. Confirm call quality, script accuracy, and answer rates on 10–20 calls before scaling to hundreds.
• Respect consent and do-not-call preferences. Only call numbers that have a legitimate basis for contact — existing customers, opted-in leads, or people who've requested a callback. Maintain and honor any do-not-call or opt-out list your recipients are on, and remove numbers promptly when someone asks not to be called again.
• Observe calling-hour restrictions. Many jurisdictions restrict outbound calling to specific hours (commonly excluding early morning, late evening, and sometimes holidays). Build these windows into your campaign scheduling rather than relying on manual oversight.
• Get familiar with your local regulatory requirements before scaling a campaign — rules on automated and AI-assisted calling vary by country and sector (particularly for financial services and healthcare), and what's acceptable for one type of outreach may not be for another. When in doubt, consult counsel familiar with telemarketing regulation in your target market.
• Monitor delivery and answer-rate metrics, not just whether the SIP trunk stays connected — a sudden drop in answer rate can signal carrier-side filtering rather than an integration issue.
• Keep a human-review loop for edge cases, especially objections, complaints, or requests to stop calling — the agent should recognize these and end the interaction gracefully, logging the request.
• Rotate or diversify calling numbers for large campaigns to avoid concentrating volume in a way that triggers carrier spam filtering.

Get Started

Telnyx SIP trunking paired with a Kipps.AI voice agent turns outbound calling into a scalable, consistent operation instead of a manual grind. Talk to our team about setting up your first outbound campaign, or explore the platform at kipps.ai.