Texting can be the right next step after a call, but it still contacts a person and can incur usage. A useful assistant does not treat a text as an invisible side effect. It shows the recipient, the message, and the reason for sending it.
Show the exact message
Before dispatch, the user should review the destination and body. A general instruction to help with an errand is not necessarily permission to send a different message later. Keep sensitive details out unless the person has approved both the content and the channel.
Use the same workspace boundary
The API key belongs to an organization. A messaging operation should use that organization's configured number, limits, and billing record. Do not mix a personal assistant key with another company's contact list or use a browser parameter to choose someone else's account.
Understand delivery states
A provider accepting a message does not guarantee delivery or a reply. Status callbacks can arrive later. The assistant should report the actual recorded state and should not claim the recipient read a message merely because it was sent.
Keep the approval and request identifier
A retry should refer to the same intended operation, not create a second message with a fresh identifier. If a policy check rejects the operation, review the reason instead of changing the request until it slips through. Recipient consent and suppression rules still apply.
Set it up with the right boundaries
Start with a configured workspace, an authenticated account, and a number that is approved for the workflow. Verify the owner phone and test with a destination you control. Keep the first request narrow enough to review without guessing what a successful result should look like.
Before you rely on it, check that the plan, the number, your consent rules, and the usage limits fit the work. If something is not set up, the assistant should say so plainly rather than report a success that did not happen. The person using the assistant should always be able to stop and review the next action.
Explore the Phone plan, read the MCP overview, or book a demo to talk through a specific workflow. The best first setup is one your team can explain, test, and review.