AI & Automation

AI Voice Compliance Checklist Before You Dial

What to have in place before an AI agent calls or texts your customers: registration, consent, disclosure, recording, calling windows and the records that prove it.

Mauricio Esparza By ·Published ·2 min read
mithub.club
Short answer

Before an AI agent contacts customers, have six things settled: carrier registration for messaging, a documented consent basis, a disclosure practice, a recording and retention policy, calling windows set to local rules, and an opt out that actually works. In the United States, application to person messaging requires brand and campaign registration, and an unapproved registration blocks texting entirely while voice can usually proceed.

Most AI calling launches slip on paperwork rather than on technology. This is the operational checklist, written from deployments rather than from a statute. It is not legal advice, and anything with regulatory exposure should be reviewed by counsel in your market.

1. Carrier registration for messaging

In the United States, application to person messaging is registered with the carriers through brand and campaign registration. Until it is approved, texting is blocked. Rejections happen and they take time to resolve.

Practical sequencing: start the registration early, design the SMS follow up, and ship voice while it is pending. Voice is not gated by the same process.

For every list you intend to contact, write down: where the contact came from, when, what they agreed to, and where that record lives. If you cannot answer those four for a list, that list is not ready to dial.

Existing customers, inbound requests and purchased lists are different categories with different risk. Treat them differently rather than uniformly.

3. Disclosure

Decide what the agent says about being an agent, and say it the same way every time. Requirements vary by jurisdiction and are changing, so the defensible position is disclosure by default.

It is also the better product decision. Trust survives disclosure. It does not survive discovery.

4. Recording and retention

Who is notified that the call is recorded, in what words, and at what point. Where recordings are stored, who can access them, and how long they are kept. Consent to record varies by jurisdiction, including within the United States.

5. Calling windows

Set by local rule and local reality, per market, not by convenience. This overlaps with something that also improves results: calling in the window that actually connects produces better outcomes and fewer complaints.

6. An opt out that works

The most common failure on this list. Someone asks to stop, it is recorded in one system, and a different channel contacts them the following week.

Requirements: the opt out is honoured immediately, it propagates to every channel, and it is verifiable in the record. Test it end to end with a real contact before launch.

Two more worth having

A human path. Anyone who asks to speak to a person gets one, during hours when a person exists. An agent that cannot escalate produces complaints that are entirely avoidable.

An audit trail. For every contact: which list, which consent basis, what was said, what the outcome was. If you cannot reconstruct a contact six months later, you cannot defend it either.

Before you switch on

Run one final check that has nothing to do with law. Confirm somebody answers transfers during the calling window. An agent that qualifies and transfers into an unanswered line damages more than it earns, and no amount of compliance fixes that.

Frequently asked questions

Does voice need the same registration as SMS?

No. In the United States, application to person messaging is gated by brand and campaign registration with the carriers. Voice is governed by different rules. That difference is why the practical sequencing is to ship voice first and enable messaging when registration clears.

Do we have to disclose that it is an AI?

Requirements vary by jurisdiction and are moving. Treat disclosure as the default rather than the exception, decide the exact wording once, and apply it consistently. It is also better for trust, which is the thing you are actually protecting.

This is general guidance, not legal advice?

Correct. This is an operational checklist written from deployment experience. Rules differ by country, state and industry, and anything with regulatory exposure should be reviewed by counsel who knows your market.

What is the most common failure?

An opt out that does not propagate. Someone asks to stop, it is recorded in one system, and another channel contacts them next week. Test the opt out end to end before launch, with a real record.

Sources

  1. A2P 10DLC registration · Twilio Docs (accessed 2026-09-22)
  2. Building effective agents · Anthropic (accessed 2026-09-22)
AI & AutomationComplianceOperations
Mauricio Esparza
Mauricio EsparzaGTM Systems Lead · Revenue Engineer · Founder of MitHub. Designs and runs revenue systems for multi-location businesses: AI voice campaigns, enrichment, CRM automation and attribution. Founded MitHub to teach the method in the open.

Part of AI & Automation on MitHub.

Keep going

AI & Automation

Rolling Out AI Calling Across a Branch Network

What changes when an AI calling pilot has to work in thirty locations: treating a branch as a configuration, the compliance gate, branch level reporting and the QA that keeps it honest.

Read · 3 min →mithub.club
AI & Automation

AI SDR vs Human SDR: What Each One Is Actually For

A practical comparison for revenue leaders: what an AI SDR does well, what it does badly, the hybrid that works in production, and the failure mode that wastes the investment.

Read · 2 min →mithub.club
AI & Automation

The Pilot to Production Gap in AI Projects

The pilot worked and the rollout did not. The six failures that sit between a demo and a production system, and what has to exist before the second unit goes live.

Read · 3 min →mithub.club
AI & Automation

How to Choose an Agentic AI Implementation Partner

Twenty questions that separate a partner who will reach production from one who will stall in your company, grouped by what each protects you from.

Read · 2 min →mithub.club
AI & Automation

Human in the Loop: Where People Belong in AI Workflows

How to place humans in AI workflows on purpose: risk tiers, seven approval patterns, the rubber-stamp trap, and written criteria for removing a review gate.

Read · 9 min →mithub.club
AI & Automation

When to Hire a Forward Deployed Engineer

The buyer's view of the forward deployed engineer: the problems that need someone embedded in your systems, how the engagement is scoped, and how to tell a real one from a consultant with slides.

Read · 3 min →mithub.club