Start with a legal review
TCPA compliance cannot be solved by adding one checkbox to a form. The rules depend on:
- Who is being called.
- Whether the number is mobile or landline.
- Whether the call is marketing or informational.
- Whether an autodialer or artificial voice is involved.
- How consent was obtained.
- Whether the recipient has opted out.
- Where the recipient is located.
- Which technology and vendor are used.
This article provides operational guardrails, not legal conclusions. Get advice for your actual program.
Consent must be specific and documented
A generic “I agree to the terms” may not be enough for every call or text. Your process should capture:
- The phone number.
- The business or brand making contact.
- The purpose of the messages.
- The channel: calls, texts, or both.
- The consent language shown to the lead.
- The timestamp and source.
- Whether consent was later revoked.
Keep the exact form and wording used at the time of consent. If the consent language changes, do not assume old consent covers a new use.
Honor do-not-call and opt-out requests
A person who asks not to be contacted should be suppressed across the appropriate systems. This includes:
- The account's do-not-call list.
- Internal suppression files.
- Vendor and dialer suppression.
- SMS opt-out status.
- New form submissions that do not override the prior request.
Do not require the person to use a magic phrase beyond what the rules and your policy require. If a lead says “stop calling me,” that is a signal to stop and investigate.
Be careful with automated and artificial voice calls
AI voice agents, prerecorded messages, and automated dialing may be treated differently from a live person dialing manually. Technology labels can matter, but so does the actual capability and use of the system.
Before launching:
- Determine whether consent is required.
- Identify the caller accurately.
- Use required disclosures.
- Provide a path to a human.
- Maintain opt-out and suppression controls.
- Review call recordings and vendor practices.
- Document the legal analysis.
Read AI cold calling for the operational side of AI voice agents.
Respect calling windows
Do not call at times that are prohibited by applicable law or that disregard the recipient's time zone. Build the time-zone logic into the dialer or campaign. A lead in another state is not necessarily in the same local time.
Quiet hours, holiday rules, and local restrictions can vary. Your compliance review should define the windows for each market.
Keep caller identity accurate
Do not spoof or misrepresent the caller. The recipient should be able to understand who is contacting them and why. For AI or recorded calls, follow the disclosure requirements that apply to your program.
A clear identity can also improve trust and reduce complaints. Deceptive caller ID may create legal and deliverability problems.
Record the outcome and the evidence
A compliance program needs evidence:
- Consent records.
- Suppression requests.
- Call logs.
- Scripts and versions.
- Disclosure settings.
- Recording retention.
- Vendor certifications or contracts.
- Complaint handling.
- Training records.
If you cannot show how a contact was obtained and what disclosure was used, you have a weak process even if the call sounded fine.
Vet vendors and subprocessors
Your dialer, AI provider, SMS provider, CRM, and email platform may all play a role in compliance. Ask:
- How does the vendor capture consent?
- How does it handle opt-outs?
- Does it support calling windows and time zones?
- What records does it retain?
- Does it use the data for its own purposes?
- Can it provide a data processing agreement?
- How does it handle a complaint or audit request?
You remain responsible for the program you run. A vendor's tool does not transfer that responsibility.
Build a complaint and correction process
When a recipient complains:
- Stop the relevant contact.
- Record the complaint.
- Investigate the source and consent.
- Fix the suppression or campaign rule.
- Review whether other contacts are affected.
- Escalate to counsel when appropriate.
A complaint is a signal that the process failed somewhere. Treat it as an operational defect, not a customer-service annoyance.
A practical sales-call checklist
- Written consent and source captured.
- Suppression lists applied before dialing.
- Quiet hours and time zones configured.
- AI/recorded disclosures reviewed.
- Caller identity accurate.
- Human handoff defined.
- Opt-out honored across systems.
- Scripts and versions archived.
- Vendor review completed.
- Legal review scheduled for changes.
The best time to build compliance is before the first campaign. The second-best time is before the next call—not after a complaint or demand letter.