Telnyx Voice

Give the agent the sources it needs to answer accurately: product guides, service instructions, or other knowledge available to your Connic agent. For information that changes, add a tool that checks the relevant system during the call. The order status or available appointment times then come from that lookup.

Use your configured Python or MCP tools for actions such as saving a booking or creating a ticket. Describe which information the agent must collect and what it should confirm with the caller before taking an action. Connect and configure those tools in your project.

Choose a supported realtime model, its voice, and an opening greeting in the agent YAML. Configure interruptions, the pause used to detect when the caller has finished speaking, and the inactivity timeout. When interruptions are enabled, the caller can speak over a response and Connic clears queued playback.

The agent can end the call after saying goodbye, or you can disable that ability in its voice settings. Check the Voice documentation when adapting an existing agent: voice runs have their own supported feature set, and input/output guardrails and human approvals are currently unavailable.

Your phone number stays in your Telnyx account. Connic uses the saved API key to list eligible numbers and configure the selected number's Call Control application. The account's public Ed25519 key lets Connic verify that incoming events were signed by Telnyx.

Save these credentials once and select the same connection when adding another number. You can also reuse it for Telnyx Messaging. Each connector still has its own number or messaging sender, channel, and agent links. Update credentials in the saved connection when they change.

Connic creates a dedicated Call Control application and assigns your selected number to it. You do not need to create a SIP connection for this connector. Check the number's forwarding and destination settings before setup so calls reach the agent under the expected number.

When you switch numbers or remove the connector, Connic clears only the call routing it still owns. Routes changed manually in Telnyx are preserved, and earlier provider settings are not restored. The Telnyx Voice setup guide explains number requirements and what to do if a number cannot be detached automatically.

Open the run to read the transcript and inspect the tools the agent called, their inputs, and their results. Use traces and timings to investigate a slow lookup or an answer that did not match the returned information. Refine the prompt or tool and repeat the test call.

For a failed call, inspect both the Connic run error and the call details in Telnyx. Confirm that the connector is enabled, the number still points to its Connic application, and exactly one deployed voice agent is linked.