An AI assistant becomes more useful when it can finish an ordinary phone errand. With topdoer.ai Phone, you connect a supported client, describe the outcome you want, and approve the communication. The agent can then use its own number to reach the other party. Your workspace keeps the record so you can check what happened afterward.
Start with a clear request
Start by choosing a task with a clear boundary. Moving an appointment, asking for opening hours, or checking whether a repair shop offers a service are good examples. Give the assistant the destination number and the details it may share. Keep payment instructions, sensitive account changes, and uncertain decisions outside the initial request.
Write the desired result as a small brief. Include the person or business to contact, the question to ask, any acceptable alternatives, and what should happen if nobody answers. A useful boundary might be: ask for available times, but do not confirm a booking until I choose one. The assistant should not have to guess your preference.
Connect the client you use
Choose the AI client you already use. Claude, ChatGPT, Codex, and Cursor have different connector settings, and support can vary by plan or administrator policy. The setup dialog gives client-specific instructions. For a different agent, check its support for remote MCP using streamable HTTP before proceeding.
Review the result
When the call is finished, read the result in context. A summary is useful, but the underlying conversation matters when a date, name, amount, or condition affects your decision. If the other party needs another answer from you, supply it deliberately. Keep the assistant working from an updated request rather than assuming it knows a changed plan.
Keep the boundaries clear
A phone number is a communication channel. It does not give an assistant permission to act on every possible request. Keep approval prompts enabled, follow the final plan limits, and verify important outcomes yourself. Your workspace must be configured with a number, an active entitlement, verified phone access, and allowed destinations before outbound calls can run.
Set up the connection in three steps
- Choose your AI in the Phone setup dialog. Check that the client supports the remote connection and that your workspace permits it.
- Connect the MCP endpoint with supported authentication. Use a read-only request first, then review a specific call or message before approving it.
- Review the plan at checkout. Choosing a client does not charge you, and a connection does not activate an unconfigured number or subscription.
Read the plan before you start
The first month is $9, then $19 per month, or $190 a year with two months free. Fair use applies: 200 call minutes and 300 text segments a month, one call at a time, 30 calls a day, and up to 15 minutes per call, to US, Puerto Rico and Canada numbers. Over the cap, add a $10 top-up (about 60 minutes) or wait for the next cycle. See the full fair-use list.
Keep a record of what you approved and what actually happened. If a request fails, read the error and check its state before trying again. Review the billing terms shown by Stripe, including renewal and taxes. Your workspace Billing page opens the supported customer portal for subscription changes. You can also contact our team when a plan or client requirement needs clarification.
Frequently asked questions
Do I approve the call or text?
Yes. Review the destination, goal, and information to be shared before approving an outbound action. Keep your client's approval controls enabled.
Can I use English or Spanish?
English and Spanish are supported choices. Specify the language before the action and check the result for important names, dates, and numbers.
Where do I see the price and limits?
It costs $9 for the first month, then $19 a month or $190 a year. Fair-use limits apply, and checkout shows the final terms before you pay.
Connection reference
Use the remote endpoint shown below. Store a real credential only in your client's supported private authentication setting, and consult the MCP setup documentation for the current client contract.
Transport: streamable HTTP
Server URL: https://mcp.topdoer.ai/mcp
Authentication: workspace API key, or configured OAuth sign-in
Read tools: list_calls, get_call_result
Actions requiring approval: place_call, send_text