FTC makes covered telemarketing a reconstructable record

Make the call traceable to the commercial principal

An AI dialer, voice service, outsourced team, or sequencing platform can distribute execution across several systems, but the revenue record still needs to identify the seller, telemarketer, good or service, recipient, time, number, and disposition. Preserve the campaign, account, contact source, calling identity, service-provider chain, script or model version, and CRM outcome together. A summary such as AI outreach completed cannot reconstruct who acted for whom or what the person actually encountered.

Version the message and the authority to call

Store the approved script, prerecorded message, generated variation rules, consent evidence where relied upon, Do Not Call source and access record, suppression state, and the version used for each covered call. When an AI system composes speech dynamically, retain enough information to reproduce the material representation without treating a model identifier as the message. Test that opt-outs and corrections propagate across every provider before another call is attempted.

Allocate responsibility without losing evidence

The FTC guidance says sellers and telemarketers can divide recordkeeping responsibility by contract, while both bear responsibility if no contract does so. Revenue leaders should map each required record to a named system and owner, specify access and export rights, and test retrieval during the relationship and after termination. A contractual allocation does not help if one provider retains the call detail while another holds consent, scripts, suppression, and caller-ID authorization with no common key.

Keep coverage and exemptions outside the automation

The TSR has definitions, coverage rules, exemptions, and distinctions among consumer, business-to-business, inbound, outbound, live, and prerecorded calls. The 2024 amendments also expanded certain misrepresentation protections for business calls, but that does not mean every sales conversation has identical recordkeeping duties. Determine scope with qualified review using the actual campaign facts. The system should preserve those facts and the resulting decision, not infer universal permission or obligation from the presence of AI.

Turn this source into a reviewable decision

For AI for Chief Revenue Officers, use this briefing as a dated decision record rather than a substitute for the source. Preserve U.S. Federal Trade Commission, the exact URL, the July 25, 2026 review date, the supported facts above, the editorial interpretation, the limitations, and any buyer-specific evidence. Link that record to the decisions most directly affected: Seller outreach assistance; Conversation intelligence and coaching; Revenue operations and data quality. State whether the source changes the scope, evidence requirement, control, sequence, or only the language used to describe the decision.

Before action, name the accountable owner, affected population and workflow, exact offering or configuration, source data and rights, human decision point, exception and appeal path, complete cost, expected benefit, failure and stop conditions, retained evidence, and next review date. Keep official facts, provider statements, buyer observations, representative tests, measured outcomes, editorial inferences, and unknowns visibly separate. Reopen the record when the source, offer, model, integration, data, policy, population, responsible person, or measured result changes.

Limitations and unknowns

The FTC guidance summarizes amended TSR recordkeeping for covered activity and does not resolve the coverage, exemption, consent, call-content, jurisdiction, or liability questions for a particular campaign. It is not a July 2026 change.