Keep your agent’s brain.
Your model, memory, tools, and business logic stay in your application. Send AgentPhone a text reply and it handles speaking to the caller.
See how it worksAgentPhone vs Twilio
Give your existing agent a number, conversation history, and the tools to call and text. AgentPhone handles the voice pipeline, so you can focus on what your agent does.
Start buildingFree migration from Twilio.
Your model, memory, tools, and business logic stay in your application. Send AgentPhone a text reply and it handles speaking to the caller.
See how it worksRead message history, store conversation metadata, and receive voice transcripts through an agent-focused API. Give your agent context for its next action.
See how it worksMCP tools let your agent buy a number, place a call, read a transcript, and send a follow-up. You don’t have to build each tool wrapper.
See how it worksAgentPhone has a signup flow an agent can run through the API. You verify your email; it gets an account, an API key, a starter agent, and a phone number together. Then it can use phone tools from the environment where it already works.
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.
For teams adding a phone to an existing AI agent. The comparison below uses Twilio’s documented Agent Connect (TAC) and ConversationRelay workflows.
| What matters | AgentPhone | Twilio |
|---|---|---|
| Agent onboarding | API signup returns a key, starter agent, and number after email verificationYour agent can provision itself; you only confirm the email. | TAC quickstart starts with account credentials and a number ↗ |
| Your voice handler | Receive a transcript; return text over HTTPAny HTTP backend works. There is no socket to keep open per call. | ConversationRelay uses a WebSocket connection ↗ |
| Conversation context | Message threads and custom metadata in the APIHistory and your own metadata live on the thread, with nothing extra to wire. | TAC integrates Conversation Orchestrator and Memory ↗ |
| Calls and messages | One agent.message event format for your handlerOne handler covers calls and every messaging channel. | TAC configures SMS and voice webhook paths ↗ |
| Agent phone tools | MCP actions for calls, texts, numbers, and transcriptsPhone actions are ready to call from your agent runtime. | Documentation MCP; operational tools can be built ↗ |
| Account structure | An agent, its numbers, and its conversationsEverything hangs off the agent, so setup mirrors how you think about it. | Main account, keys, and optional subaccounts ↗ |
Selected workflows from each platform’s documentation, checked 2026-09-22. Follow the source links for setup details and requirements.
In webhook mode, AgentPhone sends your agent the caller’s words. Your backend returns text; we handle the speech. You keep the reasoning and tool calls in the application you already run. Hosted mode is also available when you want to start from a system prompt.
Your agent can read the call transcript and send the next message. Use voice, SMS, MMS, iMessage, WhatsApp, and RCS through AgentPhone. WhatsApp and RCS are in beta; iMessage requires access approval. You choose the channels your workflow needs.
Bring your Twilio 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.