A phone-enabled AI can use texts for a short approved follow-up, a confirmation, or a clear update. topdoer.ai Phone gives a compatible client access to a send_text tool alongside its call tools. You provide the destination and message, review what will be sent, and approve the action before it leaves the workspace.
Start with a clear request
Start with a recipient who is allowed to receive the message. Keep the text useful and specific: identify yourself or your business, explain the purpose, and include only the details necessary for that purpose. Verify the destination number carefully. A familiar name in a chat does not prove that a saved phone number is current or belongs to that person.
Ask the assistant to show you the proposed wording. Review dates, amounts, links, and personal information before approving. If the text follows a call, make sure it reflects the actual call result rather than an expected outcome. A message saying an appointment is confirmed should be based on a confirmed appointment, not merely a request for one.
Connect the client you use
Connect a supported remote MCP client and inspect the send_text tool description. Keep its approval controls enabled. If your application uses the API instead, show the final destination and body to a person before submitting the request. Store credentials privately and keep the server's actual response visible to the user.
Review the result
Read the message state in your workspace. Submission, delivery, and a recipient response are different events. An accepted request does not establish that the person read it. Preserve the message record with its related call or task so a later follow-up starts with the right context. Avoid sending repeated messages just because a response is not immediate.
Keep the boundaries clear
Texting has consent, fair-use, and destination requirements. Keep opt-out preferences respected and do not use the service for unsolicited bulk messages. The final plan publishes texts per day and allowed countries. Carrier handling, registration requirements, and recipient availability can affect delivery. Ask the team about a business messaging workflow before assuming a personal AI phone plan covers it.
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.