Anima vs AgentPhone
AgentPhone gets you a phone number quickly. Where it ends is also where TCPA gets interesting — consent assertion, the FCC's Reassigned Numbers Database, calling-hour windows, opt-out honoring. AgentPhone leaves all of that to you.
Anima ships every one of those gates server-side, fail-closed by default. Same phone numbers; the regulatory infrastructure is just there. Plus email, voice, and a credential vault on the same identity, all under one bill.
Anima
AgentPhone
Phone Numbers
SMS
Voice
Compliance
Voice Guardrails
Cross-Channel
Pricing
What server-side compliance actually means
Phone APIs that hand you a number and trust you with the law are quick to ship and slow to defend. Anima's voice path runs every outbound call through these gates before the dial:
- TCPA gate. The handler requires a `consent_source` assertion on every request. Missing or malformed → the call is not placed. The assertion is recorded with the request for audit.
- RND check. Twilio Lookup against the FCC Reassigned Numbers Database. Numbers flagged "yes, reassigned since your consent date" never dial. 30-day Postgres cache means repeat numbers cost zero. The safe-harbor protection is yours, not ours — you got it the right way.
- Time-of-day enforcement. The dialer computes the recipient's local hour from the area code and refuses calls outside 8am–9pm local. State-stricter windows are configurable per-org.
- Hard-cap kill-switch. An org admin can flip a toggle that immediately halts all outbound voice/SMS/email from the org. Useful when a misconfigured agent starts calling the wrong list. The toggle is synchronous — takes effect on the very next request.
- Per-tier daily call cap. Stops a runaway agent from dialing thousands of numbers in a loop. Free tier 20 calls/mo, Starter 250, Growth 1,000, Scale 4,000 — past the cap, requests return 402 with an upgrade CTA.
Compliance with TCPA, the National Do-Not-Call Registry, RND, CAN-SPAM, GDPR, and CASL stays the customer's responsibility — Anima is infrastructure, not legal counsel. The full posture is documented at /trust/tcpa-dnc.
Migrating from AgentPhone
If you're already on AgentPhone for SMS/voice, the cleanest path is to stand up Anima alongside, route new outbound through Anima's compliance gates, and keep your existing inbound webhooks pointed wherever they are until you consolidate.
- 1. Provision an Anima identity with phone + voice. The first number costs $2/mo, included in Starter+.
- 2. Move the highest-risk outbound flow first — whatever calls vendors, payers, or numbers your team didn't personally consent. Anima's RND gate catches reassignments before AgentPhone's "trust the customer" model would.
- 3. Wire up the cross-channel correlation ID on the same workflow's email step. Now every email-sent → SMS-followup → voice-callback in that flow is one chain in your audit log.
Phone numbers + the FCC math, included.
Stop writing your own consent assertion middleware. Get the numbers and the gates in one platform.