Bring the agent you already have.
Connect your existing application through a webhook. Keep its reasoning, integrations, and state where they are while AgentPhone handles calling and messaging.
See how it worksAgentPhone vs Telnyx
Keep the model, memory, and tools you already built. AgentPhone adds phone numbers, conversation history, and text-based voice handling through one focused API.
Start buildingFree migration from Telnyx.
Connect your existing application through a webhook. Keep its reasoning, integrations, and state where they are while AgentPhone handles calling and messaging.
See how it worksMessage threads, conversation metadata, and call transcripts give your agent information it can act on. Your integration can work with text instead of managing audio.
See how it worksConnect MCP to let your agent manage numbers, call people, read conversations, and send messages. The same tools work from your coding environment or agent runtime.
See how it worksYour agent can initiate signup through the API. After you verify your email, it receives the account, key, starter agent, and number together. Connect your own backend for live replies or use a hosted voice agent to get started.
The API sends a code to your email.
It gets the account, key, agent, and number.
Connect its tools through MCP or the API.
Agent signup requires email verification. US outbound SMS requires carrier registration; iMessage requires access approval. Calling is subject to account verification and funding requirements.
Compare the path from your existing agent to live conversations, from account setup to message history.
| What matters | AgentPhone | Telnyx |
|---|---|---|
| Getting started | API signup bundles key, starter agent, and number after verificationKey, agent, and number arrive together after one email confirmation. | Bot signup provides an account and API key ↗ |
| Where your agent runs | Your own backend via a transcript-and-reply webhookYour runtime stays in charge; AgentPhone is the phone in front of it. | Assistant builder configures model, tools, and voice ↗ |
| Working with context | Read message threads; store your conversation metadataThreads and metadata are yours to read and write through the API. | Conversation history and configurable insights ↗ |
| Voice integration | Return text; AgentPhone handles speechReturn text; speech, turn-taking, and telephony are handled for you. | Configure the assistant’s voice and transcription ↗ |
| Adding messaging | Reuse the voice/message event handler in your backendMessaging reuses the handler you already wrote for voice. | Configure messaging on a Telnyx AI assistant ↗ |
| Tools for your agent | MCP for calls, messages, numbers, and conversationsTools cover the phone actions an agent needs, in one MCP server. | MCP for calls, messages, numbers, and assistants ↗ |
Selected workflows from each platform’s documentation, checked 2026-09-22. Follow the source links for setup details and requirements.
Your agent already knows how to use your database, CRM, and internal tools. In AgentPhone’s webhook mode, incoming voice turns become text requests to that same backend. Return the answer and we handle the voice response. You decide how your agent thinks and what it does next.
Calls and messages arrive in a shared event format. Add SMS, MMS, iMessage, WhatsApp, or RCS as your use case grows. WhatsApp and RCS are in beta; iMessage requires access approval. AgentPhone SMS pricing includes carrier fees and taxes.
Bring your Telnyx setup. We’ll help you connect your agent, plan the migration, and get started on AgentPhone. Volume pricing and price matching are available as you scale.
AgentPhone SMS includes carrier fees and taxes.
Bring your agent. We’ll help with the move.