The word unlimited can hide important operational limits. A flat monthly plan can still have limits on daily calls, text messages, call minutes, concurrency, countries, or the kinds of tasks it supports. Those limits should be visible before a person buys the plan.
Separate price from capacity
A plan price describes the commercial offer. Capacity rules describe the amount and pattern of work the service supports. The two should be shown together, along with any behavior when a limit is reached. A limit is not an error to work around with repeated requests.
Check the destination rules
Country coverage, number eligibility, carrier behavior, and provider requirements can vary. Do not assume a plan supports a destination because a phone number is syntactically valid. Coverage should be confirmed in the plan configuration and checked by the server.
Keep approval even when usage is included
A prepaid or flat-price plan does not give an assistant permission to contact anyone it chooses. Recipient consent, a lawful purpose, calling hours, suppression rules, and user approval still matter. Included usage changes billing, not the authority behind an action.
Prefer visible limits to a vague promise
The topdoer.ai Phone plan publishes its limits next to the price. It is $9 for the first month, then $19 a month or $190 a year, and it includes:
- 200 call minutes and 300 text segments per month
- 1 call at a time, up to 30 calls a day, and up to 15 minutes per call
- Calls and texts to US, Puerto Rico and Canada numbers
If you reach the monthly cap, you can add a $10 top-up (about 60 minutes) or wait for the next cycle. International destinations will be billed per minute at published rates when they become available. The Phone plan page always shows the current list.
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.