# Missed Call Text Back: TCPA Consent Rules Explained

> Understand TCPA consent tiers, quiet hours, and DNC rules for missed call recovery. Plura AI supports compliance across voice, SMS, and webchat.

**Published:** 2026-09-03 | **Updated:** 2026-11-06 | **Author:** plurasync
**URL:** https://www.plura.ai/articles/missed-call-recovery-tcpa-compliance
**Type:** post

**Categories:** AI SMS Automation

![Missed Call Text Back: TCPA Consent Rules Explained](https://plura.sites.aigrowthagent.co/wp-content/uploads/sites/75/2026/09/1788342626237-206d56dfaf73-1024x572.webp)

---

## Content

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

## Key Takeaways

- A missed call provides implied consent for a single transactional text-back. Any promotional follow-up requires prior express written consent under 47 CFR § 64.1200(a)(2).2
- The TCPA draws a strict line between transactional and telemarketing messages. The transactional exemption applies solely to the first informational response.2
- AI voice callbacks are treated as artificial or prerecorded voice under the FCC’s February 2024 ruling. This treatment raises the consent bar for any marketing content.2
- Quiet hours, DNC scrubbing, and opt-out rules apply to any delayed or secondary recovery sequence that qualifies as a telephone solicitation.
- Plura AI enforces these compliance gates inside the workflow through real-time DNC scrubbing, automated quiet-hours enforcement, and immutable consent logging.

[See how Plura automates TCPA-aware missed-call recovery.](https://www.plura.ai/plura-webchat?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent)

## How Implied Consent Works After a Missed Call

A missed call counts as implied consent to address that specific inquiry. A one-time transactional text-back responding to a user-initiated call falls under the lower prior express consent standard rather than prior express written consent, as long as the message stays informational and not promotional.

Implied consent remains tied to that single inquiry. Adding the number to a recurring marketing list or outbound broadcast campaign requires a separate, higher consent tier.

Prior express written consent is the standard for promotional messages. Under [47 CFR § 64.1200(f)(9)](https://govregs.com/regulations/47/64.1200), this consent is a written agreement bearing the signature of the person called that clearly authorizes the seller to deliver advertisements or telemarketing messages using an autodialer or artificial or prerecorded voice.

Quiet hours under [47 CFR § 64.1200(c)(1)](https://govregs.com/regulations/47/64.1200) and DNC scrubbing under [47 CFR § 64.1200(c)(2)(i)(D)](https://govregs.com/regulations/47/64.1200) apply to any delayed or secondary sequence that constitutes a telephone solicitation.

AI voice callbacks fall under the [FCC’s February 2024 declaratory ruling (FCC 24-17, CG Docket No. 23-362)](https://theleveragedyears.com/ai-regulation-news/us-fcc-tcpa-ai-generated-voice-calls-2024). That ruling treats calls using AI to generate or clone human voices as an “artificial or prerecorded voice” under the TCPA, which raises the consent requirement for marketing content.

## How TCPA Classifies Transactional and Marketing Messages

The TCPA separates transactional messages from telemarketing messages. [47 CFR § 64.1200(f)(13)](https://govregs.com/regulations/47/64.1200) defines telemarketing as the initiation of a telephone call or message for the purpose of encouraging the purchase or rental of, or investment in, property, goods, or services. [47 CFR § 64.1200(f)(15)](https://govregs.com/regulations/47/64.1200) defines telephone solicitation in similar terms, excluding calls made with prior express invitation or permission and calls to persons with an established business relationship.

A transactional message is informational or service-related and responds to consumer-initiated contact. A one-time text-back confirming a missed call, providing a callback number, or relaying account status fits on the transactional side of that line. The transactional exemption applies to that first touch only.

A subsequent message that introduces promotional content, encourages a purchase, or shifts to marketing escalates the consent requirement to prior express written consent under [47 CFR § 64.1200(a)(2)](https://govregs.com/regulations/47/64.1200).

Operators running [missed-call recovery](https://plura.ai/ai-voice-demo?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent) at volume should consult qualified counsel to confirm where their specific message content falls on this classification line before launching a multi-touch sequence.

## Consent Tiers for Each Missed-Call Recovery Step

Most exposure appears on the second and third touch, not on the first text-back. Each stage of the recovery workflow carries a distinct consent requirement tied to a specific regulatory citation.

**Step 1: One-Time Transactional Text-Back Responding to a User-Initiated Call.** Prior express consent is the applicable standard as long as the message remains informational and not promotional.

**Step 2: AI Voice Callback.** Prior express consent is required absent an emergency purpose or exemption. Prior express written consent is required if the call includes or introduces an advertisement or constitutes telemarketing. The February 2024 FCC ruling and [47 CFR § 64.1200(a)(3)](https://govregs.com/regulations/47/64.1200) govern this step.

**Step 3: Second Follow-Up Introducing Promotional Content.** When the second touch shifts to marketing or introduces promotional content, prior express written consent is required under [47 CFR § 64.1200(f)(9)](https://govregs.com/regulations/47/64.1200).

**Step 4: Transition Into a Marketing Sequence.** Prior express written consent is required for any step that constitutes telemarketing or telephone solicitation under [47 CFR § 64.1200(a)(2)](https://govregs.com/regulations/47/64.1200).

[Plura’s Missed-Call Recovery Implementation Checklist](https://www.plura.ai/articles/missed-call-recovery-checklist/?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent) maps these steps to operational tasks for operators preparing to launch at scale.

[See how Plura enforces consent gates in a live workflow.](https://plura.ai/ai-voice-demo?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent)

## How the TCPA Treats AI Voice Callbacks

The [FCC’s February 2024 declaratory ruling (FCC 24-17, CG Docket No. 23-362, adopted February 2, 2024, effective February 8, 2024)](https://theleveragedyears.com/ai-regulation-news/us-fcc-tcpa-ai-generated-voice-calls-2024) confirmed that calls using AI to generate or clone human voices qualify as an “artificial or prerecorded voice” under the TCPA. The ruling applies to any caller using an AI voice, including legitimate businesses making ordinary marketing or service calls, regardless of intent to deceive.

The ruling ties AI voice callbacks to the consent rules for artificial or prerecorded voice. Prior express consent applies absent an emergency purpose or exemption. Prior express written consent applies when the call includes or introduces an advertisement or constitutes telemarketing. [47 CFR § 64.1200(b)](https://govregs.com/regulations/47/64.1200) also requires that all artificial or prerecorded voice messages clearly state at the beginning the identity of the business responsible for initiating the call and provide a telephone number for do-not-call requests.

Operators deploying an [AI voice agent](https://plura.ai/ai-voice-demo?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent) for callbacks should confirm with qualified counsel that their consent posture aligns with this ruling before any outbound AI voice contact is initiated.

## Disclosures and Opt-Out Handling Across Channels

Under [47 CFR § 64.1200(b)](https://govregs.com/regulations/47/64.1200), every artificial or prerecorded voice message must clearly state at the beginning the identity of the business responsible for initiating the call. Telemarketing messages must also provide a telephone number for do-not-call requests during regular business hours.

Under [47 CFR § 64.1200(a)(10)](https://govregs.com/regulations/47/64.1200), a called party may revoke prior express consent by any reasonable method, including reply texts containing “stop,” “quit,” “end,” “revoke,” “opt out,” “cancel,” or “unsubscribe.” All revocation requests must be honored within a reasonable time not to exceed ten business days.

Under [47 CFR § 64.1200(a)(12)](https://govregs.com/regulations/47/64.1200), a one-time text message confirming a revocation request is permitted without violating the robocall or robotext prohibitions, provided the confirmation contains no marketing or promotional information.

Opt-out must carry across voice and SMS channels. A STOP on [AI SMS](https://plura.ai/ai-sms-leads?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent) should suppress voice callbacks as well. Channel-specific silos for opt-out create operational gaps and downstream exposure.

## Quiet Hours and DNC Scrubbing for Later Touches

The instant text-back fires immediately. Any delayed or secondary sequence falls under quiet-hours and DNC rules when it qualifies as telemarketing or solicitation.

Under [47 CFR § 64.1200(c)(1)](https://govregs.com/regulations/47/64.1200), telephone solicitations to residential subscribers may not be initiated before 8:00 a.m. or after 9:00 p.m. local time at the called party’s location. Any delayed or secondary missed-call follow-up that constitutes telemarketing or solicitation must respect the same local-time window, scheduled by the recipient’s local time zone, not the campaign’s originating time zone.

Under [47 CFR § 64.1200(c)(2)(i)(D)](https://govregs.com/regulations/47/64.1200), entities making telephone solicitations must use a version of the national DNC registry obtained no more than 31 days before the date any call is made. Under [47 CFR § 64.1200(d)(3)](https://govregs.com/regulations/47/64.1200), a residential subscriber’s do-not-call request must be recorded and honored within a reasonable time not to exceed ten business days.

For a deeper operational walkthrough of DNC scrubbing mechanics, see [Missed Call Recovery: The Complete Operator’s Playbook](https://www.plura.ai/articles/best-missed-call-recovery-practices/?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent).

## How Plura AI Supports Compliance Inside the Workflow

Plura AI operates as its own FCC-licensed audio bridging carrier. Voice traffic does not route through a third-party CPaaS. Plura issues branded caller ID at the carrier level and runs STIR/SHAKEN (Secure Telephone Identity Revisited / Signature-based Handling of Asserted information using toKENs) authentication on every outbound call.1

Plura enforces real-time DNC scrubbing against federal and state registries before dial, and automated quiet-hours enforcement runs through time-zone detection on every contact. Consent records are immutable, timestamped, and audit-ready inside the platform. Those controls matter because [TCPA violations can cost $500 to $1,500 per text or call](https://www.plura.ai/guides/ai-marketing-automation?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent), and [class action settlements have averaged into the tens of millions of dollars](https://leadcompliant.com/articles/consent-and-optin/fcc-one-to-one-consent-rule-telemarketing-january-27-2025-loophole). The compliance infrastructure inside the platform is designed to support operators in managing that exposure at scale.

![Screenshot of Plura’s fully compliant AI communications platform showing business registration and phone number provisioning workflows for AI Voice, SMS, RCS, and Webchat communication automation.](https://cdn.aigrowthmarketer.co/1779337911454-8c3a9645d906.png)**Plura’s FCC-licensed AI communications platform simplifies compliant business registration and phone number provisioning for AI Voice, SMS, RCS, and Webchat workflows.**

Plura’s AI Voice, [AI SMS](https://plura.ai/ai-sms-leads?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent), and AI RCS share a Stateful Conversation Database. A lead who texted at 9 a.m. is the same lead when the callback runs at noon. This continuity matters for consent across the recovery workflow because the platform holds the consent event, the channel history, and the opt-out status in one place rather than siloed by channel.

Plura’s [managed workflows](https://plura.ai/managed-workflows?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent) and no-code workflow builder let operators configure consent gates, quiet-hours rules, and DNC suppression at the campaign level without engineering. [Conversation intelligence](https://plura.ai/business-intelligence?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent) surfaces audit-ready reporting on demand. [Integrations](https://plura.ai/integrations?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent) across 50+ tools ensure consent records and opt-out signals flow into the systems operators already use.

![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**

Plura supports customer compliance. Customers remain responsible for their own regulatory obligations, the consent language they present to end users, and the claims they make about their own programs.

[Walk through a missed-call recovery workflow with Plura.](https://plura.ai/ai-voice-demo?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent)

## Consent Requirements by Recovery Stage

The table below maps each stage of a missed-call recovery workflow to its required consent tier and the governing citation, so operators can see where the consent bar rises.

| Recovery Stage | Consent Tier Required | Regulatory Citation |
| --- | --- | --- |
| One-time transactional text-back responding to user-initiated call | Prior express consent | [47 CFR § 64.1200(a)(1)](https://govregs.com/regulations/47/64.1200) |
| AI voice callback (no advertisement or telemarketing) | Prior express consent | FCC 24-17, CG Docket No. 23-362; [47 CFR § 64.1200(a)(3)](https://govregs.com/regulations/47/64.1200) |
| AI voice callback (includes or introduces advertisement or telemarketing) | Prior express written consent | FCC 24-17, CG Docket No. 23-362; [47 CFR § 64.1200(a)(3)](https://govregs.com/regulations/47/64.1200) |
| Second follow-up introducing promotional content | Prior express written consent | [47 CFR § 64.1200(f)(9)](https://govregs.com/regulations/47/64.1200) |
| Transition into recurring marketing sequence | Prior express written consent | [47 CFR § 64.1200(a)(2)](https://govregs.com/regulations/47/64.1200) |

## Frequently Asked Questions

### Is a Missed Call Implied Consent Under the TCPA?

A missed call counts as implied consent to address that specific inquiry, and it does not grant permission to add the number to a recurring marketing list or outbound broadcast campaign. The transactional exemption applies to the one-time text-back responding to a user-initiated call. Promotional messages require prior express written consent under 47 CFR § 64.1200(f)(9).

### Does a Missed Call Text Back Require Prior Express Written Consent?

A one-time transactional text-back responding to a user-initiated call requires prior express consent, not prior express written consent, as long as the message is informational and not promotional. Telemarketing or promotional texts require prior express written consent under 47 CFR § 64.1200(a)(2). Operators should consult qualified counsel to confirm their specific message content falls on the transactional side of that line.

### What Are the TCPA Quiet Hours for Missed Call Follow-Up?

Federal quiet hours for telephone solicitations are 8:00 a.m. to 9:00 p.m. in the called party’s local time zone under 47 CFR § 64.1200(c)(1). The instant text-back is immediate, and any delayed or secondary sequence that constitutes telemarketing or solicitation must respect the same local-time window. Several states impose narrower windows: Florida and Oklahoma close at 8:00 p.m., and [Connecticut prohibits texts before 9:00 a.m.](https://purduegloballawschool.edu/blog/news/tcpa-sms-compliance) Multi-state operators often apply the strictest window applicable to each recipient’s location.

### Do AI Voice Callbacks Count as Artificial or Prerecorded Voice Under the TCPA?

The [FCC’s February 2024 declaratory ruling (FCC 24-17, CG Docket No. 23-362)](https://theleveragedyears.com/ai-regulation-news/us-fcc-tcpa-ai-generated-voice-calls-2024) treats calls using AI to generate or clone human voices as an “artificial or prerecorded voice” under the TCPA. Callers must obtain prior express consent absent an emergency purpose or exemption, and prior express written consent when the call includes or introduces an advertisement or constitutes telemarketing. The ruling applies to any caller using an AI voice, regardless of intent to deceive.

### Does This Work with GoHighLevel?

Plura integrates with GoHighLevel through its automations category, alongside Make and Zapier.3 The platform’s no-code workflow builder and Stateful Conversation Database let operators enforce consent gates, quiet hours, and DNC scrubbing inside the recovery workflow regardless of the CRM or automation layer in use. The full integrations directory is at plura.ai/integrations.

## Conclusion

TCPA compliance for missed-call recovery operates on a per-step basis. The first text-back is transactional. The AI voice callback is a separate contact event with a stricter consent tier. The second and third touches often create exposure because the content shifts toward marketing before the consent posture has been updated to match.

Plura AI is built to enforce these compliance gates inside the workflow, not as a bolt-on after the fact. Its FCC-licensed carrier, real-time DNC scrubbing, automated quiet-hours enforcement, immutable consent logging, and Stateful Conversation Database allow operators to run missed-call recovery at volume with infrastructure that supports their compliance obligations at each step. Customers remain responsible for their own regulatory posture and the consent language they present to end users.

[Run your numbers through Plura’s calculator to check your ROI in real time.](https://plura.ai/calculator?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent)

[Compare plans and rates side by side.](https://plura.ai/pricing?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent)

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 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

- [Missed Call Booking Compliance: The Pre-Send Gate Playbook](https://www.plura.ai/articles/missed-call-booking-compliance/?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent)
- [TCPA Compliance for AI Call Centers: A 2026 Guide](https://www.plura.ai/articles/ai-call-center-tcpa-compliance/?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent)
- [Automatic Missed Call Recovery: The Operator’s Build Guide](https://www.plura.ai/articles/automatic-missed-call-recovery/?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent)
- [TCPA Compliance for Text-To-Call Workflows](https://www.plura.ai/articles/text-to-call-tcpa-compliance/?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent)
- [TCPA Compliance for AI Calling, SMS, and RCS Campaigns](https://www.plura.ai/articles/tcpa-compliant-conversational-ai/?utm_term=missed-call-recovery-tcpa-compliance&utm_campaign=ai_growth_agent)

---

## Structured Data

**@graph:**

  **FAQPage:**

  **MainEntity:**

    **Question:**

    - **Name:** Is a Missed Call Implied Consent Under the TCPA?
      **Answer:**

      - **Text:** A missed call counts as implied consent to address that specific inquiry, and it does not grant permission to add the number to a recurring marketing list or outbound broadcast campaign. The transactional exemption applies to the one-time text-back responding to a user-initiated call. Promotional messages require prior express written consent under 47 CFR § 64.1200(f)(9).
    **Question:**

    - **Name:** Does a Missed Call Text Back Require Prior Express Written Consent?
      **Answer:**

      - **Text:** A one-time transactional text-back responding to a user-initiated call requires prior express consent, not prior express written consent, as long as the message is informational and not promotional. Telemarketing or promotional texts require prior express written consent under 47 CFR § 64.1200(a)(2). Operators should consult qualified counsel to confirm their specific message content falls on the transactional side of that line.
    **Question:**

    - **Name:** What Are the TCPA Quiet Hours for Missed Call Follow-Up?
      **Answer:**

      - **Text:** Federal quiet hours for telephone solicitations are 8:00 a.m. to 9:00 p.m. in the called party local time zone under 47 CFR § 64.1200(c)(1). The instant text-back is immediate, and any delayed or secondary sequence that constitutes telemarketing or solicitation must respect the same local-time window. Several states impose narrower windows: Florida and Oklahoma close at 8:00 p.m., and Connecticut prohibits texts before 9:00 a.m. Multi-state operators often apply the strictest window applicable to each recipient location.
    **Question:**

    - **Name:** Do AI Voice Callbacks Count as Artificial or Prerecorded Voice Under the TCPA?
      **Answer:**

      - **Text:** The FCC February 2024 declaratory ruling (FCC 24-17, CG Docket No. 23-362) treats calls using AI to generate or clone human voices as an artificial or prerecorded voice under the TCPA. Callers must obtain prior express consent absent an emergency purpose or exemption, and prior express written consent when the call includes or introduces an advertisement or constitutes telemarketing. The ruling applies to any caller using an AI voice, regardless of intent to deceive.
    **Question:**

    - **Name:** Does This Work with GoHighLevel?
      **Answer:**

      - **Text:** Plura integrates with GoHighLevel through its automations category, alongside Make and Zapier. The platform no-code workflow builder and Stateful Conversation Database let operators enforce consent gates, quiet hours, and DNC scrubbing inside the recovery workflow regardless of the CRM or automation layer in use. The full integrations directory is at plura.ai/integrations.

  **BlogPosting:**

  - **Headline:** Missed Call Text Back: TCPA Consent Rules Explained
  - **Description:** Understand TCPA consent tiers, quiet hours, and DNC rules for missed call recovery. Plura AI supports compliance across voice, SMS, and webchat.
  - **DateModified:** 2026-09-29T08:47:29.450Z
  - **Image:** https://cdn.aigrowthmarketer.co/1779337911454-8c3a9645d906.png, 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)
- **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)

## Citations

- [Stop Keyword Opt-Out Requirements for SMS: 2026 Guide](https://www.plura.ai/articles/sms-stop-keyword-opt-out-requirements)
- [Automated Text Back When a Lead Form Is Filled Out](https://www.plura.ai/articles/automated-text-back-lead-form)
- [AI SMS Agent Opt-Out Handling: A Build Spec for Dev and Ops](https://www.plura.ai/articles/ai-sms-agent-opt-out)
- [How To Run AI SMS Follow-Up for Window and Door Leads](https://www.plura.ai/articles/ai-sms-follow-up-window-door)
- [Mortgage Lead SMS Follow-Up: Consent and Compliance](https://www.plura.ai/articles/mortgage-lead-sms-compliance-guide)

---

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