Let your agent actually take the call.
Place and receive live calls through AgentPhone. Your agent gets the transcript and returns an answer; AgentPhone handles the speech and phone connection.
See how it worksAgentPhone vs Linq
Beyond Linq messaging. Give your agent a voice.
Give your agent live calling and dedicated SMS numbers alongside rich messaging. Handle conversations through AgentPhone without adding a second telephony provider for calls.
Start buildingFree migration from Linq.
Your AI agent
AgentPhoneVoice
SMS / MMS
iMessage
WhatsAppBeta
RCSBeta
Keep building your agent.
We’ll handle the phone.
Make SMS its own workflow.
Provision an SMS-capable US or Canadian number and send messages directly through the API. SMS is available independently of an iMessage line.
See how it worksLet the agent manage its numbers.
Buy, attach, and release ordinary voice/SMS numbers through the API or MCP. Your agent can perform these steps as part of its own setup.
See how it worksGive your agent the number directly.
With AgentPhone, an agent can initiate signup through the API. After email verification, the account, key, starter agent, and phone number are created together. Your agent can then use that number through MCP or the API, with free help migrating from Linq.
- 1Your agent starts signup
The API sends a code to your email.
- 2You verify your email
It gets the account, key, agent, and number.
- 3Give it work to do
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.
What changes when
you use AgentPhone.
The difference is how your agent gets a number, handles live calls, and uses each messaging channel.
| What matters | AgentPhone | Linq |
|---|---|---|
| Live voice API | Place and receive calls directlyYour agent answers and places calls without a second provider. | No direct calling API; use external telephony ↗ |
| Number provisioning | US/Canada voice + SMS numbers via APINumbers are an API call away, so the agent can set itself up. | Ask a representative for V3 lines ↗ |
| SMS delivery | Dedicated SMS numbers and direct messaging APISend plain SMS from a dedicated number when the workflow calls for it. | V3 lines; “SMS” prefers RCS, then SMS ↗ |
| iMessage | Supported; access approval requiredAvailable once approved, on the same account and API. | Supported ↗ |
| RCS | Supported; in betaAvailable in beta through the same API as SMS. | V3 protocol option with SMS fallback ↗ |
| Supported; in betaAvailable in beta alongside your other channels. | Separate API; beta access required ↗ |
Selected workflows from each platform’s documentation, checked 2026-09-22. Follow the source links for setup details and requirements.
A call should reach your agent.
Linq’s V3 API routes calls through external telephony; it does not directly place or answer them. AgentPhone handles the live call. Use your own backend for the answer or configure a hosted voice agent. Keep calling and messaging in the same AgentPhone account.
Choose the channels your agent needs.
Use voice, SMS, MMS, iMessage, WhatsApp, and RCS through AgentPhone. WhatsApp and RCS are in beta. iMessage requires access approval; the starting plan supports replies to conversations someone else initiates. Dedicated send-and-receive lines are available when your workflow needs them.
We’ll help you make the move. For free.
Bring your Linq 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.
Your agent has work to do.
Give it a number.
Start building Bring your agent. We’ll help with the move.