An assigned number creates a familiar way to reach your AI: make a phone call. Inbound behavior depends on the agent and number configuration in your workspace. The caller can explain the request, and the conversation can be kept with the other work in the account. Review that configuration before sharing the number with anyone.
Start with a clear request
Decide who the number is intended for and what it should handle. An agent used for personal errands needs different instructions from a business receptionist. Set a clear introduction, the information it may collect, and the situations it should hand back to a person. Do not publish a number as an urgent contact if the workflow cannot support urgent requests.
Test the conversation with a simple request. Check how the agent introduces itself, asks for clarification, and handles a caller who changes direction. Make sure the goal of the call becomes a clear result, such as a captured question or a request for follow-up. A useful call flow has a stopping point rather than keeping the caller talking indefinitely.
Connect the client you use
Use the workspace to inspect the number assigned to the account. Connecting an MCP client and assigning an inbound voice workflow are related configuration steps, but one does not automatically describe the other. Ask the team about the intended inbound behavior, supported coverage, and any requirements before distributing the number publicly.
Review the result
Read the call record after a test and compare it with what you intended the agent to do. Check names, callback details, and any action it says it completed. If something is unclear, update the instructions and test again. Sharing a number should come after that review, especially when another person will rely on the conversation.
Keep the boundaries clear
Inbound access remains subject to the subscription, number status, fair-use conditions, and provider availability. A number attached to an inactive or paused account may not behave as you expect. Keep another contact path for important communications. The service is not an emergency line and should not be presented as one.
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.