Compliant by design · TCPA-aware

Built to keep you on the right side of the TCPA.

Calling and texting people is heavily regulated — a single wrong call can cost hundreds of dollars. AI Phone Genius is built to stop an illegal call before it happens: consent gating, contact-local calling windows, an internal do-not-call list, one-click opt-out, and a full audit trail are wired into the platform, not bolted on.

Compliance is the product's biggest differentiator — not a checkbox.

What the platform enforces — and how

Eight guardrails run on every campaign. None of them are optional, and none of them depend on you remembering to switch them on.

Consent gating on every dial

No contact is dialed unless their recorded consent clears the level a campaign requires.

  • Five tracked consent levels; only prior express written consent (pewc) and express consent are ever callable.
  • Written consent covers any campaign; verbal express consent covers only campaigns that ask for the lighter level.
  • “No consent on record,” “Do not call,” and “Opted out” are never dialed — the campaign filters them out before the queue is built.

Contact-local calling windows

Calls only place inside legal hours in the contact's own time zone — never yours.

  • A hard 8:00am–9:00pm clamp is enforced contact-local, no matter what a campaign is configured to allow.
  • Time zone is detected from the phone's area code (US & Canada) at dial time when it isn't set on the contact.
  • If an area code can't be resolved, the platform skips the call rather than guessing the hour.

Internal do-not-call list

Your workspace keeps its own suppression list that overrides everything.

  • Any number on the internal DNC is never dialed by any campaign — regardless of that contact's consent status.
  • Importing a number already on your DNC forces it back to do-not-call automatically (shown as “Forced to DNC”).
  • Add or remove numbers by hand from Settings → Compliance, with an optional reason on record.

One-click opt-out that propagates

When someone says “stop,” one action makes it true everywhere — by voice or by chat.

  • Flips their consent to “Opted out” so no future campaign can include them.
  • Adds their number to the internal do-not-call list.
  • Pulls them out of every active campaign immediately, so no queued call goes out — and writes it to the audit log with a timestamp and source.

Mandatory AI disclosure

Callers are told they're speaking with an AI assistant — it's baked into the agent, not left to chance.

  • Every agent template opens with the AI disclosure, and re-states it if a caller asks “who is this?”
  • The pre-launch checklist won't pass unless disclosure is enabled on the agent making the calls.
  • Disclosure toggles are written to the audit log so you can prove the state at any point in time.

Append-only audit log

Every compliance-relevant event is recorded and never rewritten.

  • Consent changes, opt-outs, campaign launches, checklist acknowledgements, and disclosure toggles are all captured.
  • Entries are written, never edited — each contact carries a plain, timestamped consent audit trail on their page.
  • The activity timeline merges calls, chats, and consent events into one newest-first story you can hand to anyone who asks.

Pre-launch compliance checklist

No campaign goes live until you've acknowledged the four things that matter.

  • Confirm you have the right consent for these contacts.
  • Confirm the list is scrubbed against your internal do-not-call list, and that AI disclosure is enabled.
  • Accept responsibility for the campaign per the Terms of Service — and the acknowledgement is logged.

Multi-tenant data isolation

Your contacts, calls, and consent records are scoped to your workspace alone.

  • Every tenant table carries an org identifier with row-level security enforced at the database.
  • Application code additionally scopes every query to your session's workspace.
  • One workspace can never read or dial another's list — isolation is enforced in two places, not one.

Consent, in plain words

Five levels are tracked on every contact. Only the top two can ever be dialed — and the platform decides, not you.

LevelPlain meaningCallable?
Prior express written consentSigned a form, checked a box, or scanned a consent card agreeing to automated calls or texts. The strongest grant.Any campaign
Express consentVerbally agreed to be contacted (e.g. “sure, call me” at your booth).Express-level only
No consent on recordYou have the number but no record they agreed to be contacted.Never
Do not callOn your suppression list — an absolute stop.Never
Opted outAsked to stop hearing from you.Never

When you build a campaign you tell it which level it requires, and the platform quietly filters out anyone who doesn't clear that bar. You can't accidentally include them.

Shared responsibility

The platform does a lot — but it isn't your lawyer. Here's the honest line between what AI Phone Genius enforces and what stays your job.

What AI Phone Genius handles

  • Gate every dial on recorded consent level
  • Clamp calls to 8am–9pm in the contact's local time
  • Detect time zone from area code, or skip the call
  • Honor opt-outs everywhere, instantly, on voice and chat
  • Keep an append-only audit trail of consent events
  • Enforce AI disclosure and the pre-launch checklist
  • Isolate every workspace's data from every other

What you must still do

  • Obtain valid consent before you upload a contact
  • Keep your own proof of that consent (forms, opt-in screenshots)
  • Truthfully record how each list was collected
  • Follow the state and federal laws that apply to your calls
  • Have your own counsel review your scripts and program
  • Connect federal DNC-registry scrubbing if you cold-call at scale

You don't have to be a lawyer. You just have to tell the truth about where each contact came from and what they agreed to — the platform does the rest. AI Phone Genius's guardrails reduce your exposure; they don't replace your own legal review or your obligation to obtain and keep valid consent.

Security practices

The essentials, stated plainly. We only claim what's true today — anything still in progress is labeled as roadmap.

Encrypted in transit

All traffic between your browser, the API, and the platform runs over TLS.

Least-data by design

The platform stores the contact fields it needs to call and stay compliant — nothing more is required to run a campaign.

Wallet & billing integrity

An append-only ledger is the source of truth for money; calls of 15 seconds or less bill zero, and balances update in the same transaction as every charge.

Federal DNC scrubbing

Roadmap

Registry scrubbing is an optional connector your provider can enable — on the roadmap for turnkey setup.

No fake certifications, no borrowed badges. If it isn't listed here, we're not claiming it.

Compliance you can hand to your legal team.

Spin up your first agent and see the guardrails run on every dial — consent-gated, time-boxed, and fully logged.