What makes an invoice collection call TCPA compliant?
What makes an invoice collection call TCPA compliant?
Short answer
Five requirements have to be in place. First, the call must disclose that an AI is speaking, before any business content. Second, the recording must be announced and consented to. Third, the call window must respect the debtor's local timezone, not yours — federally 8am-9pm, often stricter at the state level. Fourth, attempt frequency caps must be honored. Fifth, federal and state Do Not Call lists must be checked and enforced.
TCPA compliance is not a single rule; it is a stack of specific operational behaviors that have to all be true at the moment the call happens. Missing any one creates statutory liability of $500-$1,500 per call, and class actions aggregate quickly across recipients.
The AI disclosure requirement is the most often missed. If an AI voice is on the call, the recipient must be informed at the start, before any business reason is stated. 'Hi, this is the billing department' is not enough. 'Hi, I'm an AI assistant calling on behalf of [Your Business]' is. Federal TCPA enforcement on this point sharpened materially after FCC clarifications in 2024.
Call windows are timezone-dependent on the debtor, not the caller. If you are in California calling a New York customer, the California time of 7:30pm is 10:30pm in New York — past the federal 9pm boundary. State variations narrow this further. Florida's FCCPA cuts off at 8pm. Massachusetts adds frequency caps. The compliant approach is to derive the timezone from the billing address on file, not from the area code (which is increasingly unreliable as people keep their numbers when they move).
Frequency caps are also state-specific. Federal TCPA does not specify an exact maximum, but courts have consistently held that more than 7 calls in 7 days, or 4 calls in 4 weeks to a known non-responder, constitutes harassment. Most state laws specify lower caps — Massachusetts limits to a defined frequency, Texas similarly. The safe operational floor is no more than 3 attempts per invoice with at least 3 days between attempts.
DNC enforcement is the easiest to get wrong because the lists are both federal and state-level. The National DNC Registry is the headline; state-level DNC lists exist in California, Florida, Indiana, Louisiana, Massachusetts, Mississippi, Missouri, Pennsylvania, Tennessee, Texas, and Wyoming, sometimes with rules that extend beyond the federal baseline. A compliant collections operation has to check all relevant lists before every dial, not just the federal one.
Recording consent is one-party in some states and two-party in others. The safe approach is to announce recording at the start of every call, regardless of state — this satisfies the consent requirement everywhere, including two-party-consent states like California, Florida, and Pennsylvania.
Syntharra runs all five of these as deterministic gates, before the AI agent speaks. The compliance layer derives timezone from billing address, checks federal and state DNC lists, enforces 8am-8pm windows where states require it (stricter than federal), caps at 3 attempts per invoice, and prepends the AI disclosure and recording notice. None of those can be skipped or modified by the LLM.