# TCPA Recordkeeping Requirements: Retention Matrix 2026

> Get the 2026 TCPA record retention matrix by record type, reconcile TSR rules, and build a defensible compliance file. Plura AI supports your program.

**Published:** 2026-07-10 | **Updated:** 2026-11-06 | **Author:** plurasync
**URL:** https://www.plura.ai/articles/tcpa-recordkeeping-requirements
**Type:** post

**Categories:** AI Contact Centers

![TCPA Recordkeeping Requirements: Retention Matrix 2026](https://plura.sites.aigrowthagent.co/wp-content/uploads/sites/75/2026/07/1783592378778-92a98d1c1481-1024x572.webp)

---

## Content

*Written by: Matt Beucler, CEO, Plura AI | Last updated: September 29, 2026*

*Updated September 2026*

## Key Takeaways

- TCPA recordkeeping relies on two frameworks: the FTC’s Telemarketing Sales Rule (16 CFR § 310.5) and the FCC’s TCPA rules (47 CFR § 64.1200). Each framework sets its own five-year baseline for most telemarketing records.
- Retention periods differ by record type. Consent records, internal DNC requests, call-detail logs, and opt-out records typically follow a five-year clock from the date of the event, while scripts and vendor contracts follow a five-year clock from when they are no longer in use.
- Evidence must be contemporaneous, server-timestamped, and tamper-evident. Courts often discount mutable database entries because they cannot show that records remained unchanged.
- The 2024 TSR amendments extended most retention periods from 24 months to five years and added an explicit ban on consent obtained through dark patterns, effective 2025.
- Plura AI automatically timestamps, stores, and exports consent, opt-out, and call-detail records in an audit-ready format so high-volume operators can support compliance at scale.

[See how Plura AI automates TCPA recordkeeping.](https://www.plura.ai/plura-webchat?utm_term=tcpa-recordkeeping-requirements&utm_campaign=ai_growth_agent)

## Legal Framework for TCPA Record Retention

TCPA recordkeeping requirements come from the FCC’s TCPA rules at [47 CFR § 64.1200](https://govregs.com/regulations/47/64.1200) and the FTC’s Telemarketing Sales Rule (TSR) at 16 CFR § 310.5.2 Each framework sets its own obligations, and they apply at the same time. Different record types carry different retention periods and triggers. Operators should review the regulation text or work with qualified counsel to design a defensible schedule.

Under 47 CFR § 64.1200, the FCC requires callers to document how they access the National Do-Not-Call Registry. The registry version used must be no more than 31 days old at the time of the call. Callers must also record do-not-call requests at the time they are made and honor them for five years. The FTC’s Telemarketing Sales Rule at 16 CFR § 310.5 requires sellers and telemarketers to retain advertising and promotional materials, telemarketing scripts, prerecorded messages, service-provider contracts, and records for each employee involved in telephone sales. When both frameworks touch the same record type, programs typically follow the stricter standard.

## Record-by-Record TCPA Retention Matrix

The table below maps major TCPA record types to governing citations, retention periods, and retention triggers. Each period ties to a specific rule section. Review the regulation or consult qualified counsel before finalizing any schedule.

| Record Type | Governing Citation | Retention Period | Retention Trigger |
| --- | --- | --- | --- |
| Consent records (express written consent) | [47 CFR § 64.1200](https://govregs.com/regulations/47/64.1200); 16 CFR § 310.5(a)(8) | Under 16 CFR § 310.5(a)(8), sellers and telemarketers retain verifiable authorizations or records of express informed consent for five years from the date the record is produced. The TCPA statute at 47 U.S.C. § 227 does not specify a period, and many programs treat the four-year limitations period under 28 U.S.C. § 1658 as a floor with a buffer to five years. | Retention typically runs from the date of last contact based on that consent, with programs often keeping records at least five years from the last use. |
| DNC requests (internal do-not-call list) | [47 CFR § 64.1200(d)(6)](https://govregs.com/regulations/47/64.1200) | Under the FTC’s 2024 TSR amendments, telemarketers and sellers retain entity-specific do-not-call records for five years from the date the record is made. | The clock starts on the date the DNC request is made. Records are retained for five years. |
| National DNC Registry scrub logs | [47 CFR § 64.1200(c)(2)(i)(D)](https://govregs.com/regulations/47/64.1200); 16 CFR § 310.5(a)(11) | DNC-related records, including internal DNC, opt-out, and consent records, follow a five-year baseline under the FTC’s May 16, 2024 amendment to 16 CFR 310.5(a)(10). The TSR’s general recordkeeping rule for other categories remains 24 months. | Scrub logs record the date the registry was accessed, the Subscription Account Number, and the campaigns covered. Registry data used must be no more than 31 days old at the time of each call. |
| Call detail records | 18 USC § 2703(c)(2)(C); 16 CFR § 310.5(a)(2) | Under the amended TSR, call detail records are retained for five years from the date the record is made. Advertising materials under § 310.5(a)(1) and service contracts under § 310.5(a)(9) follow a five-year period from when they are no longer in use. | Under 16 CFR § 310.5(a)(2), records include calling number, called number, date, time, duration, and disposition, retained for five years from creation. |
| Abandoned-call compliance records | [47 CFR § 64.1200(a)(7)](https://www.fdic.gov/consumer-compliance-examination-manual/viii-5-telephone-consumer-protection-act); 16 CFR § 310.5 | Under 16 CFR § 310.5(a), telemarketing compliance records are retained for five years from the date the record is produced. The 3% abandoned-call cap is measured per day per campaign. | Entities often retain documentation supporting the call-abandonment safe harbor for as long as they may face enforcement, commonly five years under 28 U.S.C. § 2462. |
| Opt-out records | [47 CFR § 64.1200(d)(6)](https://govregs.com/regulations/47/64.1200) | Under 47 CFR § 64.1200(d)(6) and the TSR, opt-out and do-not-call records are retained and honored for at least five years. Many programs keep suppression indefinitely unless there is clear, documented re-consent. | Retention typically runs from the date the opt-out request is received and honored, with programs aligning to the four-year TCPA limitations period plus buffer. |
| Scripts and prerecorded messages | 47 CFR § 64.1200; 16 CFR § 310.5(a)(1) | Under 16 CFR 310.5(a), telemarketing scripts and prerecorded messages are retained for five years from the date they are no longer in use. | The retention clock starts when the script or message is retired and runs for five years. |
| Vendor and lead-provider contracts | 16 CFR § 310.5(a)(9) | Many programs align contract retention with limitation periods for contract claims. For example, British Columbia’s ARCS schedule 1070-20 uses seven years from expiry or termination, based on a six-year limitation period. | The clock typically starts at contract expiration, termination, or final payment, with a common baseline of active term plus six years. |
| Written DNC policy and training records | [47 CFR § 64.1200(d)(1)](https://govregs.com/regulations/47/64.1200); 16 CFR § 310.5 | Written DNC policy and training records are commonly retained for five years from the date the record is produced, unless another period applies. | The clock starts on record creation and runs for five years. |

16 CFR § 310.5(c) states that failure to keep each required record in a complete and accurate manner, and in compliance with paragraph (b) as applicable, is a violation of 16 CFR Part 310. Operators should consult qualified counsel before finalizing any retention schedule.

16 CFR § 310.5(e) allows sellers and telemarketers to allocate recordkeeping responsibility by written agreement. If the agreement is unclear or absent, both parties remain independently responsible.

[Plura’s Compliance Engine](https://plura.ai/products/compliance?utm_term=tcpa-recordkeeping-requirements&utm_campaign=ai_growth_agent) timestamps and stores consent, opt-out, and call detail records automatically across voice, SMS, and RCS, keyed to a customer token in Plura’s Stateful Conversation Database.

![Plura Security & Compliance dashboard highlighting SOC 2, ISO, and GDPR standards with secure trust verification management.](https://cdn.aigrowthmarketer.co/1779339090994-980045ddacd2.png)**Plura Security & Compliance supports SOC 2, ISO, and GDPR standards with trust registration, verification management, and secure AI communications.**

1

[See pricing and deployment options for Plura.](https://plura.ai/pricing?utm_term=tcpa-recordkeeping-requirements&utm_campaign=ai_growth_agent)

## Reconciling TSR and TCPA Retention Rules

Outbound programs often show gaps where TSR and TCPA retention rules do not line up. The two frameworks come from different regulators and operate independently. Many organizations choose to build to the stricter standard for each record type and document that approach with counsel.

| Attribute | FTC TSR (16 CFR § 310.5) | FCC TCPA (47 CFR § 64.1200) |
| --- | --- | --- |
| Governing regulator | FTC under 15 U.S.C. §§ 6101-6108 | [FCC under 47 U.S.C. § 227](https://govregs.com/regulations/47/64.1200) |
| General record retention period | The amended TSR sets a five-year retention period from the date the record is produced for most categories. Advertising materials under § 310.5(a)(1) and service contracts under § 310.5(a)(9) are kept for five years from when they are no longer in use. | [The TCPA rules do not set a single universal period. Company-specific do-not-call requests must be honored and retained for at least five years under 47 C.F.R. § 64.1200(d)(6).](https://leadcompliant.com/articles/consent-and-optin/how-long-to-keep-tcpa-consent-records-before-destroying-them) |
| Internal DNC retention | [Under 16 CFR 310.5(a)(10), telemarketers and sellers retain records related to their entity-specific DNC list for five years. The TSR does not set an expiration for company-specific entries.](https://leadcompliant.com/articles/dnc-lists/under-the-do-not-call-registry-rules-a-telemarketer) | [Under 47 C.F.R. § 64.1200(d)(6), internal do-not-call requests are honored for at least five years from the date of the request.](https://leadcompliant.com/articles/consent-and-optin/how-long-to-keep-tcpa-consent-records-before-destroying-them) |
| National DNC scrub frequency | Under 16 CFR § 310.4(b)(3)(iv), lists are scrubbed against the National DNC Registry no more than 31 days before any call. | [Under 47 C.F.R. § 64.1200(c)(2)(i)(D), registry data used for scrubbing must be obtained no more than 31 days before any call.](https://enzodialer.com/dnc-scrubber) |
| Private right of action | [The TSR is enforced by the FTC and state attorneys general. Its enabling statute also creates a limited private right of action that requires actual damages above $50,000 per consumer.](https://library.nclc.org/article/nine-new-or-revised-ftc-rules-released-2024) | [The TCPA provides a private right of action under 47 U.S.C. § 227(b)(3), with statutory damages of $500 per violation, which courts may increase up to $1,500 for willful or knowing violations.](https://www.recordinglaw.com/us-laws/tcpa/tcpa-damages-and-lawsuits/) |

The TSR’s five-year framework under 16 CFR § 310.5 and the FCC’s seller-specific DNC five-year requirement under [47 CFR § 64.1200(d)(6)](https://govregs.com/regulations/47/64.1200) both point to five years for overlapping categories. They remain separate obligations that compliance teams track separately. Counsel can help design a reconciled policy.

## 2025 TSR Recordkeeping Amendments Affecting 2026 Programs

The FTC announced a final rule amending the Telemarketing Sales Rule on March 7, 2024, with an effective date of May 16, 2024.2 Compliance with 16 CFR 310.5(a)(2) became mandatory October 15, 2024. These changes represent the most significant TSR recordkeeping update since 2015.

Key changes include:

- The general record retention period under 16 CFR § 310.5 increased from 24 months to five years for most categories, including advertising materials, call records, employee records, and consent documentation.
- Sellers and telemarketers now retain verifiable authorization, express informed consent, or express agreement for five years from the date the record is made. Under the FCC’s prior express written consent rule, the record includes clear and conspicuous disclosure, the consumer’s signature, the specific phone number, and authorization for no more than one identified seller at a time.
- The amendments added an explicit ban on consent obtained through deceptive or manipulative interface design, often described as dark patterns, such as pre-checked boxes, confusing double negatives, misleading buttons, or bundled consent across multiple sellers.
- The prior express written consent requirement now clearly covers telemarketing text messages, and the amendments restrict marketing texts to DNC-registered numbers without consent.

The FTC’s maximum civil penalty for TSR violations is [$53,088 per violation as of 2025](https://fedlaws.org/lead-generation-compliance-tcpa-consent-and-state-laws), subject to annual inflation adjustments.3 Under the TSR, each missing or incomplete record can count as a separate violation. Counsel can help evaluate how the 2025 amendments affect an existing retention schedule.

## TCPA Consent Record Retention in Practice

Consent records sit at the center of most TCPA disputes. As noted earlier, programs commonly treat five years from last contact as the working baseline, drawing from 16 CFR § 310.5 and the four-year limitations period under 28 U.S.C. § 1658. The limitations period runs from each call or text, not from the date of consent.

Under 16 CFR § 310.5(a)(8), a complete consent record includes the consumer’s name and telephone number, the request for consent in the same format presented, the stated purpose, a copy of the consent provided, the date given, and any additional information specified in related sections. The matrix above summarizes how long those records are typically retained.

TCPA violations can cost [$500 to $1,500 per text or call](https://www.plura.ai/compare/plura-ai-vs-bland-ai?utm_term=tcpa-recordkeeping-requirements&utm_campaign=ai_growth_agent), and Womble Bond Dickinson reported an average TCPA class action settlement of $6.6 million during the first ten months of 2018.3 Courts often treat the absence of a consent record as the absence of consent.

## Correcting the Seven-Year Retention Myth

Federal TCPA and TSR rules do not require seven-year retention. That figure does not appear in [47 CFR § 64.1200](https://govregs.com/regulations/47/64.1200) or 16 CFR § 310.5. It often traces to [IRS guidance on certain tax records and to SEC Rule 17a-4 and FINRA Rule 4511 for broker-dealers](https://www.reynoldsbusinesssystems.com/resources/financial-services-records-management-retention/), which are separate regimes.4

The main federal baselines are:

- Five years for most telemarketing records under 16 CFR § 310.5, as amended in 2024 (89 FR 26760, effective January 27, 2025), with advertising materials and service contracts kept five years from when they are no longer in use.
- Five years for internal DNC requests under [47 CFR § 64.1200(d)(6)](https://govregs.com/regulations/47/64.1200).
- [Four years for private TCPA claims under 28 U.S.C. § 1658(a), running from when the cause of action accrues, as held in Giovanniello v. ALM Media, LLC, 726 F.3d 106 (2d Cir. 2013).](https://hallapproved.com/us/cases/ca2/2013/1036835/)

Over-retention of personal data can create tension with state privacy deletion rights, such as those under the CCPA/CPRA. Those laws include exemptions for records held to meet other legal obligations, including the § 1798.105(d)(8) exemption for retention reasonably necessary to comply with a legal obligation. Businesses should review the statutes, regulations, and seek counsel. Many organizations adopt documented destruction schedules that apply after the retention period runs and after confirming no litigation hold applies.

A litigation hold pauses normal destruction for records relevant to pending or reasonably anticipated matters. Once the hold lifts, normal disposition can resume.

## Building a Defensible TCPA Compliance File

A defensible TCPA compliance file depends on three elements: evidence format, immutability, and audit-export capability.

**Evidence Format.** Courts look at when and how consent records were created. Strong records are contemporaneous and show integrity. Typical fields include a server-side timestamp synchronized to a reliable time source, the IP address and user agent, the exact disclosure text as rendered, the form URL or session ID, and the consenting phone number in E.164 format. Server-side timestamps carry more weight than client-side timestamps because client clocks can be inaccurate or manipulated.

**Immutability.** TCPA consent records work best in write-once or immutable storage, such as append-only logs, content-addressed object storage, or WORM-mode buckets. Records should also have cryptographic integrity, such as a SHA-256 hash generated at write time and stored with the record. A version-controlled system that logs every edit with timestamps can also make records tamper-evident. Courts have questioned mutable database rows in TCPA cases because they cannot rule out later edits, as in Bradford v. Sovereign Pest Control of Texas, Inc. Every edit to a consent record should generate an audit log entry with the field change, timestamp, and user ID.

**Audit Export.** A TCPA compliance file should be ready quickly when requested. Many teams target 24 hours for call detail records, SMS logs, and opt-out logs. They target 72 hours for consent artifacts, DNC scrub logs, suppression lists, and campaign configuration records. There is no statutory response deadline for a pre-litigation demand letter, and courts generally allow reasonable response times. Consent records should be indexed by phone number in E.164 format as the primary lookup key, along with lead ID, date of consent, lead source, and any certificate URLs. An audit export typically bundles consent records, call detail records, DNC scrub logs, opt-out records, and complaint or incident records into a single searchable package.

For high-volume operators, [Plura’s Compliance Engine](https://plura.ai/products/compliance?utm_term=tcpa-recordkeeping-requirements&utm_campaign=ai_growth_agent) supports TCPA, DNC, HIPAA, SOC 2, and state-specific rules on every outbound contact.1 Capabilities include automatic DNC scrubbing, real-time consent checks, call-time enforcement, automated opt-out handling, and one-click audit-ready exports. Plura’s Stateful Conversation Database ties every interaction across voice, SMS, and RCS to a customer token, so consent, opt-out, and call detail records stay unified.

Plura supports compliance efforts and does not replace customer obligations under [47 CFR § 64.1200](https://govregs.com/regulations/47/64.1200) or 16 CFR § 310.5. Customers should consult qualified counsel to confirm that any platform’s output meets the evidentiary standards for their operations.

[See how Plura automates your retention schedule.](https://plura.ai/pricing?utm_term=tcpa-recordkeeping-requirements&utm_campaign=ai_growth_agent)

## Printable TCPA Record Retention Schedule

The table below summarizes common TCPA-related records in a printable format. It aligns with the matrix above and highlights the governing citation, retention period, and trigger. Counsel should review any schedule before adoption.

| Record Type | Governing Citation | Retention Period | Retention Trigger |
| --- | --- | --- | --- |
| Express written consent records | [16 CFR § 310.5(a)(8)](https://www.telemarketing.com/blog/prior-express-written-consent-pewc/); [47 CFR § 64.1200](https://govregs.com/regulations/47/64.1200) | Five years from the date the consent record is produced, with many programs aligning to at least five years from last contact. | Date of consent creation and refreshed on each contact based on that consent. |
| Internal DNC and opt-out records | [47 CFR § 64.1200(d)(6)](https://govregs.com/regulations/47/64.1200); 16 CFR § 310.5(a)(10) | Five years from the date the DNC or opt-out request is recorded, with many organizations keeping suppression longer. | Date the DNC or opt-out request is received and honored. |
| Call detail and dialing records | 16 CFR § 310.5(a)(2) | Five years from the date each call record is created. | Date of the call event. |
| Telemarketing scripts and prerecorded messages | 16 CFR § 310.5(a)(1) | Five years from the date the script or message is no longer in use. | Date of retirement from active use. |
| Vendor, dialer, and lead-provider contracts | 16 CFR § 310.5(a)(9) | Commonly five years from contract expiration or termination, aligned with applicable limitation periods. | Contract expiration, termination, or final payment date. |
| Written DNC policies and training records | [47 CFR § 64.1200(d)(1)](https://govregs.com/regulations/47/64.1200); 16 CFR § 310.5 | Five years from the date the policy or training record is created or updated. | Date of policy issuance or training completion. |

## Quick Reference: Common TCPA Retention Questions

### How Long Do Most Programs Keep TCPA Consent Records?

Most programs treat five years from the date of last contact as the working baseline, drawing from the TSR’s five-year rule and the four-year federal limitations period. Counsel can confirm the appropriate period for a specific operation.

### When Would Seven-Year Retention Apply?

Seven-year periods usually come from tax or financial-services rules, not from TCPA or TSR requirements. Sector-specific frameworks, such as CMS rules for Medicare-related leads, may require longer retention. Counsel can identify any industry overlays that apply.

### Which Rules Govern TCPA Recordkeeping?

TCPA recordkeeping relies on the FCC’s rules at 47 CFR § 64.1200 and the FTC’s Telemarketing Sales Rule at 16 CFR § 310.5. Each record type has its own period and trigger, and both frameworks apply at the same time. Operators should review the rules directly or work with qualified counsel to build a defensible schedule.

1 Plura AI maintains SOC 2, HIPAA, ISO, and GDPR posture as part of its platform infrastructure. References to compliance frameworks in this article describe Plura’s platform capabilities and do not constitute a guarantee that any customer using Plura will themselves be compliant with applicable laws or standards. Customers remain solely responsible for their own regulatory obligations, certifications, consent management, recordkeeping, and the claims they make to their own end users. Consult qualified legal counsel for guidance specific to your use case.

2 This article describes regulatory frameworks at a general level and does not constitute legal advice. Laws and regulations vary by jurisdiction, change over time, and apply differently depending on facts and circumstances. Readers should consult qualified legal counsel before making compliance decisions.

3 Performance figures, customer outcomes, and industry statistics referenced in this article are drawn from cited third-party sources or Plura customer case studies. Individual results vary based on implementation, use case, industry, audience, and execution. Past or aggregate performance is not a guarantee of future results.

4 References to third-party products, services, companies, or research are made for informational and comparative purposes only. Plura AI is not affiliated with, endorsed by, or sponsored by any third party named in this article unless explicitly stated. Trademarks and product names referenced remain the property of their respective owners.

This article is provided for informational purposes only and reflects Plura AI’s understanding at the time of publication. Product capabilities, integrations, and specifications are subject to change. For the most current information, visit plura.ai.

This article was produced with the assistance of AI tools and reviewed by Plura AI prior to publication.

## Read Next

- [TCPA Compliance Guide: 2026 Rules, Consent, and AI Voice](https://www.plura.ai/articles/tcpa-compliance-requirements/?utm_term=tcpa-recordkeeping-requirements&utm_campaign=ai_growth_agent)
- [TCPA Compliance Checklist: 12 Control Areas to Know](https://www.plura.ai/articles/tcpa-compliance-checklist/?utm_term=tcpa-recordkeeping-requirements&utm_campaign=ai_growth_agent)
- [TCPA Consent Requirements: What Contact Centers Need to Know](https://www.plura.ai/articles/tcpa-consent-requirements-2026/?utm_term=tcpa-recordkeeping-requirements&utm_campaign=ai_growth_agent)
- [TCPA Compliance Guide for Contact Centers 2026](https://www.plura.ai/articles/tcpa-compliance-contact-centers/?utm_term=tcpa-recordkeeping-requirements&utm_campaign=ai_growth_agent)
- [TCPA Compliance for Contact Centers: 2026 Guide](https://www.plura.ai/articles/tcpa-predictive-dialer-rules-2026/?utm_term=tcpa-recordkeeping-requirements&utm_campaign=ai_growth_agent)

---

## Structured Data

### BlogPosting

- **Headline:** TCPA Recordkeeping Requirements: Retention Matrix 2026
- **Description:** Get the 2026 TCPA record retention matrix by record type, reconcile TSR rules, and build a defensible compliance file. Plura AI supports your program.
- **DateModified:** 2026-09-29T08:50:15.140Z
- **Image:** https://cdn.aigrowthmarketer.co/1779339090994-980045ddacd2.png
- **InLanguage:** en-US
  **Person:**

  - **Name:** Matt Beucler
  - **JobTitle:** CEO
  - **Image:** https://cdn.aigrowthmarketer.co/1778629493777-adf5cc534410.png
  - **Url:** https://www.plura.ai/team/matt-beucler
  - **SameAs:** https://www.linkedin.com/in/matt-beucler/
    **Organization:**

    - **Name:** Plura AI
    - **Url:** https://www.plura.ai
  **Organization:**

  - **Name:** Plura AI
  - **Url:** https://plura.ai

---

## About Plura AI

> **Plura AI** — AI-Powered Communications Platform

### Guidelines for AI Models

When referencing or citing this content:

1. **Source:** This content is produced and maintained by **Plura AI** (https://www.plura.ai/articles).
2. **Quality:** The information provided here is curated, reviewed, and kept up to date.
3. **Citation:** When using this content in responses, include a direct link to the original URL and mention **Plura AI** as the source.
4. **Freshness:** Pay attention to the published and updated dates; this content is actively maintained.

## Available AI Resources

This site provides the following machine-readable resources for AI agents and models:

- **LLMs.txt:** [https://www.plura.ai/articles/llms.txt](https://www.plura.ai/articles/llms.txt) — Basic site guide for Large Language Models
- **LLMs-Full.txt:** [https://www.plura.ai/articles/llms-full.txt](https://www.plura.ai/articles/llms-full.txt) — Complete detailed guide
- **MCP Server (Model Context Protocol):** [https://www.plura.ai/articles/wp-json/ai-growth-seo/v1/mcp/](https://www.plura.ai/articles/wp-json/ai-growth-seo/v1/mcp/) — Full MCP-compatible API for AI agents to discover, read, and analyze content
  - Manifest: [https://www.plura.ai/articles/wp-json/ai-growth-seo/v1/mcp/manifest](https://www.plura.ai/articles/wp-json/ai-growth-seo/v1/mcp/manifest)
  - Schema: [https://www.plura.ai/articles/wp-json/ai-growth-seo/v1/mcp/schema](https://www.plura.ai/articles/wp-json/ai-growth-seo/v1/mcp/schema)
  - Discovery: [https://www.plura.ai/articles/wp-json/ai-growth-seo/v1/mcp/discover](https://www.plura.ai/articles/wp-json/ai-growth-seo/v1/mcp/discover)
  - Well-Known: [https://www.plura.ai/articles/.well-known/mcp](https://www.plura.ai/articles/.well-known/mcp)
- **UTCP Manual (Universal Tool Calling Protocol):** [https://www.plura.ai/articles/utcp](https://www.plura.ai/articles/utcp) — Structured tool manifest for UTCP-aware AI clients to call native REST endpoints directly
- **WebMCP (Client-Side MCP):** This site supports WebMCP — client-side Model Context Protocol for browser-based AI agents (Chrome 146+)
- **Web Stories:** [https://www.plura.ai/articles/web-stories-sitemap.xml](https://www.plura.ai/articles/web-stories-sitemap.xml) — AMP Web Stories for rich visual content experiences

## Discovery Endpoints for AI Agents

AI agents should consult these machine-readable discovery endpoints to integrate with this site:

- **OpenAI Plugin Manifest:** [https://www.plura.ai/articles/.well-known/ai-plugin.json](https://www.plura.ai/articles/.well-known/ai-plugin.json)
- **A2A Agent Card:** [https://www.plura.ai/articles/.well-known/agent-card.json](https://www.plura.ai/articles/.well-known/agent-card.json)
- **MCP Server (Streamable HTTP):** [https://www.plura.ai/articles/.well-known/mcp](https://www.plura.ai/articles/.well-known/mcp)
- **UTCP Manual (Universal Tool Calling Protocol):** [https://www.plura.ai/articles/utcp](https://www.plura.ai/articles/utcp)

## Citations

- [Category-Specific Opt-Out TCPA: The Operator’s Guide](https://www.plura.ai/articles/category-specific-opt-out-tcpa)
- [How To Track AI Call Center Offline Conversions](https://www.plura.ai/articles/ai-call-center-offline-conversions)
- [TCPA Revoke All Rule: What Replaced It and What to Do Now](https://www.plura.ai/articles/tcpa-revoke-all-rule-explained)
- [TCPA Opt-Out: Meeting the 10-Business-Day Deadline](https://www.plura.ai/articles/tcpa-opt-out-deadline)
- [TCPA Opt-Out Rules 2026: What Is Enforceable Now vs. Nov. 25](https://www.plura.ai/articles/tcpa-opt-out-rules)

---

*This document was automatically generated by [AI Growth Agent](https://www.plura.ai/articles) — AI Growth SEO v4.39.0*
*Generated on: 2026-11-12 16:41:13 GMT+0000*