Limits and compliance
The limits that apply to outbound AI calling and campaigns, what blocked contacts mean, and your responsibility for who you call.
Limits
| Limit | Value |
|---|---|
| Recipients per campaign | 1,000 |
| Contacts per CSV import | 5,000 |
| Calls per person per hour (Test call, Call now on a contact, the API) | 20 |
| Calls per workspace per hour (same sources) | 200 |
| Campaign calls | Not counted in the hourly caps above; limited by live calls at once |
| Live calls at once per workspace | 20 by default |
| Longest single call | One hour by default |
| Phone provider for outbound | Twilio |
When a cap is hit you see "Call limit reached. Try again later." or "Workspace call limit reached. Try again later."
What Phynxa enforces
- Blocked contacts are never called. Set a contact's status to Blocked to keep them off every campaign and call.
- Only published, outbound agents place calls.
- Each campaign number is claimed before dialling, so nothing is dialled twice.
Your responsibility
Warning. You are responsible for calling only people you have the right to contact. Laws on automated and recorded calls, consent, calling hours and do-not-call lists differ by country. Phynxa does not check these for you. Respect them, keep your own consent records, and use the Blocked status for anyone who asks not to be called.
Your phone provider has its own rules and may suspend an account that makes unwanted calls.
Related guides
Something here does not match what you see in the dashboard? Let us know.