# RCS Outbound Limitations: A Failure Diagnostic Guide

> Diagnose RCS send failures fast. Plura AI covers payload limits, fallback logic, rate limiting, and pre-flight testing for messaging ops teams.

**Published:** 2026-07-14 | **Updated:** 2026-11-06 | **Author:** plurasync
**URL:** https://www.plura.ai/articles/rcs-outbound-limitations-2026
**Type:** post

**Categories:** AI SMS Automation

![RCS Outbound Limitations: A Failure Diagnostic Guide](https://plura.sites.aigrowthagent.co/wp-content/uploads/sites/75/2026/07/1783877478560-902b26f2ebff-1024x572.webp)

---

## Content

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

*Updated September 2026. Current device baselines: iOS 18 and Android 6.0+.*

## Key Takeaways

- RCS outbound limitations come from a stack of platform, carrier, and device constraints that can break delivery after API validation.
- Four primary failure modes, API rejection, carrier throttling, silent SMS fallback, and render degradation, each need different diagnostic steps.
- Seven root causes, from unsupported devices to content policy violations and TTL expiration, determine whether an RCS message reaches the recipient.
- Provider-published limits for text, media, carousels, and suggestion chips often differ from carrier-enforced limits, which creates unpredictable delivery behavior.
- Plura AI owns its FCC-licensed carrier stack and supports compliance checks inside the platform before any message leaves the network.

[See how Plura handles RCS failures in a live demo](https://www.plura.ai/plura-webchat?utm_term=rcs-outbound-limitations-2026&utm_campaign=ai_growth_agent)

## The Four Ways An Outbound RCS Message Fails

Every RCS outbound failure produces one of four operator-visible outcomes. The table below maps each symptom to its cause, the layer where it occurs, and the remediation.

| Symptom | Likely Cause | Where It Occurs | Remediation |
| --- | --- | --- | --- |
| API rejection – message never leaves the platform (“stuck on sending” at submission) | Payload, media, or compliance validation failure returned synchronously. AWS surfaces a `ValidationException` for invalid requests or media.3 Twilio returns channel-specific error objects including code 61337 (“Recipient does not have RCS enabled”).3 | Platform API | Validate payload against the strictest provider in your path before send. Check media size, character count, and country block rules. |
| Carrier throttle – accepted by the API but delivery slows or stalls mid-campaign | Account-specific, reputation-driven throughput limits. Twilio returns HTTP 429 with a Retry-After header (error code 20429) when request volume exceeds API rate limits. | Carrier / platform rate layer | Pace sends, monitor sender reputation, and split high-volume OTP and promotional traffic across separately registered campaigns. |
| Silent SMS fallback – arrives, but as SMS with rich elements stripped (“delivered but not received as RCS”) | Device not RCS-capable, carrier not enabled for A2P RCS, TTL (time-to-live) expired, or no data connectivity at delivery time. AWS reports `UNDELIVERABLE` messageStatus when the recipient’s device does not support RCS. | Carrier / device | Configure fallback explicitly, tag delivery receipts by channel, and confirm SMS sender (10DLC or Toll-Free) is provisioned before launch. |
| Render degradation – arrives as RCS but renders wrong (“silently downgrading” inside the thread) | iOS renderer collapses interactive elements. [Carousels and action buttons lose visual fidelity on iOS compared with Android](https://help.postscript.io/en/articles/15382848-guide-to-rcs-on-ios-vs-android). | Device / OS | Design for the strictest renderer and test on both iOS and Android before campaign launch. |

## Why RCS Fails To Send

RCS outbound failures cluster into seven root causes, and each one sits at a different layer of the delivery path.

![Plura RCS messaging interface showing rich mobile communication with branded media, interactive messaging, and AI engagement tools.](https://cdn.aigrowthmarketer.co/1779338832429-847c53c76db5.png)**Plura RCS enables rich mobile messaging with interactive media, branded customer experiences, and AI-powered conversational engagement.**

1. **Recipient device is not RCS-capable.** Older Android models, RCS disabled in settings, or iPhones running earlier than iOS 18 [cannot accept RCS; RCS for Business requires Android 6.0 (Marshmallow) or higher](https://messente.com/blog/state-of-rcs-business-messaging).
2. **Carrier has not enabled RCS for Business.** A carrier that supports consumer RCS may not support A2P (application-to-person) RCS. [Businesses are verified and approved by Google or the mobile carrier depending on the infrastructure used, and send via an approved aggregator or messaging provider](https://messente.com/blog/state-of-rcs-business-messaging).
3. **No data connectivity at delivery time.** RCS requires an active cellular data or Wi-Fi connection. [Android and iOS devices both require an active internet connection to send and receive RCS messages, while SMS works over the cellular signaling channel](https://messente.com/blog/state-of-rcs-business-messaging).
4. **Payload or media breached a provider limit.** Validation fails synchronously and the message never leaves the platform. AWS End User Messaging surfaces a `ValidationException` for invalid requests or media and recommends handling it with backoff and error handling in production.
5. **Content policy violation.** Restricted content categories trigger a rejection at the platform or carrier layer. AWS documents a `REJECTED` messageStatus meaning the message was rejected due to a content policy violation, with guidance to alert the operations team and review the message content.
6. **Destination number is opted out or blocked.** AWS End User Messaging returns `DESTINATION_PHONE_NUMBER_OPTED_OUT` when the destination number appears on the Default opt-out list. The send is suppressed before it reaches the carrier.
7. **TTL expired before delivery.** AWS documents two distinct TTL outcomes: `TTL_EXPIRATION_REVOKED` (expired message successfully removed, safe to trigger fallback) and `TTL_EXPIRATION_REVOKE_FAILED` (revocation failed, message might still deliver, which requires evaluation of whether a fallback would create a duplicate).

[See Plura’s full breakdown of RCS outbound pain points and carrier-layer fixes.](https://www.plura.ai/articles/rcs-outbound-pain-points/?utm_term=rcs-outbound-limitations-2026&utm_campaign=ai_growth_agent)

## Payload And Character Limits Across Providers And Carriers

Every limit below is platform-dependent, not universal. Provider-published limits differ from carrier-enforced limits, so operators need to treat those figures as ceilings, not guarantees.

- **Text body:** AWS End User Messaging documents 1-3,072 UTF-8 characters for the `SendRcsMessage` API. [Kaleyra documents 3,072 characters for the US region and 2,500 for India](https://developers.kaleyra.io/docs/rcs-payload-specification).
- **Media file size:** AWS allows up to 100 MB at the API layer and recommends keeping video under 5 MB because carriers frequently enforce lower limits.
- **Carousel cards:** [Google RCS for Business](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rich-cards) and AWS both document a minimum of 2 and a maximum of 10 rich cards per carousel.
- **Suggestion chips:** AWS documents 11 suggestion chips per message and 4 per card. [Kaleyra documents the same values across US and India regions](https://developers.kaleyra.io/docs/rcs-payload-specification).
- **Rich card titles and descriptions:** AWS documents a 200-character title limit and a 2,000-character description limit.
- **Postback data:** [Kaleyra’s API permits up to 2,048 characters of postback data, while the US carrier recommendation is 500 characters or fewer](https://developers.kaleyra.io/docs/rcs-payload-specification). That gap shows how a message can pass API validation and still behave unexpectedly at the carrier layer.

For the complete reference table of limit values, see Plura’s [RCS outbound best practices guide for enterprise operators](https://www.plura.ai/articles/rcs-outbound-best-practices-2026/?utm_term=rcs-outbound-limitations-2026&utm_campaign=ai_growth_agent).

[Compare plans and rates side by side.](https://plura.ai/pricing?utm_term=rcs-outbound-limitations-2026&utm_campaign=ai_growth_agent)

Walk through RCS payload limits in a live session

## The iOS 18 Rendering Gap

Render degradation is the fourth failure mode, and on iOS 18 it follows a specific pattern. This section focuses on which interactive elements degrade, when it happens, and how that affects live campaigns.

[iOS 18+ supports RCS, but rich cards and carousels lose visual fidelity compared with Android](https://help.postscript.io/en/articles/15382848-guide-to-rcs-on-ios-vs-android). The degradation is worst when a card includes multiple suggested actions. The specific behaviors operators encounter:

- **Suggested action buttons collapse.** [When a card includes more than one suggested action, iOS collapses the extras into a dropdown labeled “Options” instead of displaying them inline. Message-level suggested action chips collapse under an “Options” dropdown when there are more than two](https://help.postscript.io/en/articles/15382848-guide-to-rcs-on-ios-vs-android).
- **Button placement differs by type.** Suggested action buttons such as Open URL or Add Calendar Event render inside the rich card on iOS, while Android places them in a separate bubble below the card. Suggested reply buttons can render in a separate bubble below the card on iOS.
- **GIFs render as static images.** [iOS renders GIFs inside rich cards or carousels as static images only, while Android animates them](https://help.postscript.io/en/articles/15382848-guide-to-rcs-on-ios-vs-android). Design so the first frame works as a standalone image.
- **Carousel card heights vary.** [iOS sizes each carousel card based on its media and text length, so cards in the same carousel can render at different heights](https://help.postscript.io/en/articles/15382848-guide-to-rcs-on-ios-vs-android). Android keeps every carousel card the same size by center-cropping media to fit.
- **Hyperlinks behave positionally.** [A URL as the last element with no trailing text may render as a separate “tap to preview” bubble, and a URL followed by text will not render a preview card at all, appearing as raw text. Android renders previews regardless of position](https://help.postscript.io/en/articles/15382848-guide-to-rcs-on-ios-vs-android).
- **Missing card titles produce poor previews.** [If a rich card omits a title, iOS shows “One Message” as the lock screen and conversation list preview instead of pulling text from the body](https://help.postscript.io/en/articles/15382848-guide-to-rcs-on-ios-vs-android).

Use these design rules to keep messages usable across both renderers:

- Keep titles and descriptions to three lines or less per field.
- Use one CTA (call-to-action) per message and lead with the primary action.
- Put hyperlinks last and add punctuation immediately after the URL to keep the preview inline.
- Design for static images and avoid relying on GIF animation for meaning.
- Always include a rich card title.
- [Preview on both an iPhone and an Android device before activating a flow or scheduling a campaign](https://help.postscript.io/en/articles/15382848-guide-to-rcs-on-ios-vs-android).

[iOS rendering behaviors are dictated by Apple’s RCS implementation at the operating system level and cannot be overridden by the sending platform, Google, or carriers. Specific behaviors may vary by iOS version, device model, and carrier](https://help.postscript.io/en/articles/15382848-guide-to-rcs-on-ios-vs-android).

## Throughput, Rate Limiting, And Sender Reputation

Render degradation is a device-layer problem. Throttling lives on a different layer and behaves as an account-specific, reputation-driven control instead of a fixed global limit. Operators who treat it as a static ceiling misread stalled campaigns.

- AWS End User Messaging surfaces a `ThrottlingException` for rate limiting and recommends handling it with backoff and error handling in production.
- Twilio’s Bulk Messaging API returns HTTP 429 with a Retry-After header (error code 20429) when request volume exceeds API rate limits. Throughput throttling appears as an HTTP-level signal, not a carrier-level rejection.
- Sender reputation compounds over time. AWS advises registering high-volume OTP (one-time passcode) use cases separately so sender reputation is not impacted by the lower engagement rates typical of promotional traffic. Carriers subject multi-use agents to stricter vetting scrutiny. They prefer single-purpose agents.
- [ClickSend’s RCS documentation (July 2026) states that RCS senders have a default throughput of 100 MPS (messages per second), which can be increased based on volume needs, and notes that throughput specifics are evolving as RCS matures in the US market](https://help.clicksend.com/en/articles/68274-understanding-mps-and-speed-of-message-delivery-rcs).3
- [Platform-level controls on maximum number, size, and type of content also apply, and providers reserve the right to limit throughput measured in TPS (texts per second) based on content type and operational conditions](https://vibes.com/company/rcs-studio-subscription-terms-and-conditions). Throttling can occur at the provider layer before carrier behavior is involved.

## Fallback Architecture: When RCS Silently Becomes SMS

Unconfigured fallback is the most common cause of “my message never arrived” in RCS programs. When RCS cannot deliver and no fallback is configured, recipients who cannot receive RCS get nothing.

![Plura SMS interface showing AI-powered business text messaging, automated customer conversations, and personalized engagement workflows.](https://cdn.aigrowthmarketer.co/1779338938448-00c130f59594.png)**Plura SMS enables personalized AI-powered text messaging with real-time customer engagement, automation, and conversational workflows.**

Fallback triggers include:

- Unsupported devices or carriers that have not enabled RCS for Business
- The recipient disabling chat features in their messaging app
- Lack of mobile data or Wi-Fi at delivery time
- The phone being off or out of range
- Delivery timeout expiration (TTL)

Without a FallbackConfiguration, recipients who cannot receive RCS get nothing, and suggestion chips and rich cards do not translate to SMS fallback.

When RCS falls back to SMS, the rich content is removed entirely:

- Interactive buttons cannot be sent via SMS and must be replaced with URLs. Images and carousels are removed, and branded sender profiles do not carry over.
- Standard SMS fallback carries a 160-character limit, and messages exceeding it split into multiple segments, which can increase sending costs.
- [Fallback depends on proper 10DLC (10-digit long code) and Toll-Free registration. If the SMS sender is not provisioned, the downgrade cannot complete even when the RCS side is healthy](https://telgorithm.com/news/how-rcs-business-messaging-actually-works-and-the-importance-of-fallback).1
- [RCS can be approved to send at significantly higher volumes than legacy SMS, and fallback traffic is constrained by 10DLC campaign throughput limits](https://telgorithm.com/news/how-rcs-business-messaging-actually-works-and-the-importance-of-fallback).

Plura’s [AI SMS](https://plura.ai/ai-sms-leads?utm_term=rcs-outbound-limitations-2026&utm_campaign=ai_growth_agent) capability operates on the same stateful conversation database as AI RCS, so a lead who received an RCS message at 9 a.m. is the same lead when the SMS fallback or follow-up call arrives later. Context persists across the channel boundary.

## Compliance Constraints That Block Sends

Fallback is one way a message fails to arrive as RCS. Compliance blocks are another, because consent, opt-out handling, and content category restrictions function as delivery blockers at the platform and carrier layer. The frameworks below are described neutrally, and operators should consult the relevant regulation or qualified counsel for guidance on their specific obligations.

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

- A2P business RCS messages use TLS (transport layer security) in transit and a verified Brand Agent profile for trust, and they do not use end-to-end encryption.
- Regulatory frameworks including CTIA and TCPA (Telephone Consumer Protection Act) guidelines describe expectations around explicit prior consent, prompt opt-out handling, and treatment of restricted content categories.1 [SHAFT-C content categories, sex, hate, alcohol, firearms, tobacco, and cannabis, are blocked or restricted by carriers, which triggers message rejection at the platform or carrier layer. Sex and hate are always prohibited, while alcohol, firearms, and tobacco are restricted and may be allowed with age-gating on certain number types](https://docs.messagedesk.com/messaging/restrictions).2
- For US and Canadian numbers, a destination number appearing on an opt-out list is suppressed at the network or carrier level before the message is delivered.2 For example, US toll-free MT messages fail with error code 9 (Illegal Number), and platform-level suppressions refuse the send before it goes out. AWS End User Messaging best practices include processing `UNSUBSCRIBE` subscription events immediately for regulatory compliance.

## Pre-Flight Testing Before A Campaign Ships

The failure modes described above are cheaper to catch before a campaign ships than after. The following pre-flight steps test each layer of the delivery path before you expose production volume.

- Start by validating the payload against the strictest provider in your path, including character count, media size, and postback data length. That step catches API-layer rejections before they reach live traffic.
- Next, test on both iOS and Android renderers before activating any flow or scheduling any campaign. That confirms how carousels, buttons, and previews behave on real devices.
- Then confirm fallback behavior with a deliberately oversized send to a device taken offline. That test verifies that the downgrade path completes and that the SMS content remains readable.
- Verify sender registration status, including the RCS agent, 10DLC brand, and campaign, before you introduce volume. That check reduces the risk of silent blocks at the carrier layer.
- Confirm the platform revokes the original RCS message before the SMS fallback sends. If both versions land on the test device, the revocation logic is faulty and risks double-sending to real recipients.

Review your RCS pre-flight checklist with a Plura specialist

## Where Plura Fits

Most RCS and AI messaging tools act as API resellers on top of third-party telecom carriers. That architecture leaves carrier-level behavior, branded caller ID, and pre-network compliance enforcement outside their control.

![Plura Unified Inbox interface showing centralized AI Voice, SMS, RCS, and Webchat conversations in one omnichannel workspace.](https://cdn.aigrowthmarketer.co/1779338680098-bf2bbd201647.png)**Plura Unified Inbox centralizes AI Voice, SMS, RCS, and Webchat conversations into one streamlined omnichannel communication workspace.**

Plura AI is its own FCC-licensed audio bridging carrier and holds its own operating company number. It runs STIR/SHAKEN (Secure Telephone Identity Revisited / Signature-based Handling of Asserted information using toKENs) authentication on every outbound call.1 Plura’s [AI SMS](https://plura.ai/ai-sms-leads?utm_term=rcs-outbound-limitations-2026&utm_campaign=ai_growth_agent), AI RCS, and [AI Voice](https://plura.ai/ai-voice-demo?utm_term=rcs-outbound-limitations-2026&utm_campaign=ai_growth_agent) share a Stateful Conversation Database, so a lead who texted at 9 a.m. is the same lead when the call comes at noon. The platform supports compliance on every outbound contact with real-time DNC (Do Not Call) scrubbing, automated quiet hours, and immutable consent logging.1

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

For operators troubleshooting RCS outbound failures, the infrastructure layer is where durable fixes live.

[Compare plans and rates.](https://plura.ai/pricing?utm_term=rcs-outbound-limitations-2026&utm_campaign=ai_growth_agent)

[Run your numbers through the ROI calculator.](https://plura.ai/calculator?utm_term=rcs-outbound-limitations-2026&utm_campaign=ai_growth_agent)

For background on what RCS outbound is and how it fits into an enterprise messaging stack, see [What Is RCS Outbound? 2026 Business Guide To RCS Messaging](https://www.plura.ai/articles/what-is-rcs-outbound/?utm_term=rcs-outbound-limitations-2026&utm_campaign=ai_growth_agent).

Discuss your RCS outbound strategy with Plura

## Frequently Asked Questions

### How Should I Read RCS Delivery Receipts?

Treat the delivery receipt as your primary diagnostic tool. Start by distinguishing synchronous API rejections from carrier-level undeliverable statuses and from silent SMS fallback. That separation tells you whether to adjust payload, registration and reputation, or fallback configuration.

### Why Are My Messages Sending As SMS Instead Of RCS?

The platform falls back when the recipient’s device or carrier cannot accept RCS, the recipient disabled chat features, or the device was offline at delivery. Without a configured fallback, those recipients would receive nothing. As noted in the fallback section, the downgrade cannot complete without a provisioned SMS sender. Check delivery receipts for the channel used on each message, not just the top-line delivered count.

### Can You Use RCS Without Data?

RCS traffic requires an active cellular data or Wi-Fi connection to send and receive. SMS uses the cellular signaling channel, which is why fallback to SMS succeeds when RCS cannot. A device that goes offline between the capability check and the send can still produce a failed RCS delivery even when the pre-send lookup showed the number as RCS-capable.

### How Big Of A File Can You Send Over RCS?

The 100 MB API ceiling and the roughly 5 MB video limit described earlier are the two figures that matter most for media-heavy campaigns. Treat those numbers as planning anchors and validate with the actual file types and sizes your campaign will use before sending at volume.

### Why Is My iPhone Sending RCS Instead Of iMessage?

iMessage is Apple’s proprietary messaging service and applies only between Apple devices. When an iPhone messages a non-Apple recipient, the device uses RCS if the carrier supports it and the recipient’s device is RCS-capable, and SMS otherwise. [RCS on iPhone requires iOS 18 or later and a carrier that has enabled RCS for that plan and region. The RCS Messaging toggle appears under Settings, and if it is absent, the carrier may not support RCS for that specific plan or device](https://itechguides.com/rcs-messaging-between-iphone-android-how-it-works). Bubble color alone cannot confirm the channel used, because [iOS displays RCS, SMS, and MMS conversations in the same green bubble](https://itechguides.com/rcs-messaging-between-iphone-android-how-it-works).

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

- [RCS Outbound Delivery Rates: Benchmarks and How to Improve](https://www.plura.ai/articles/rcs-outbound-delivery-rates/?utm_term=rcs-outbound-limitations-2026&utm_campaign=ai_growth_agent)
- [RCS Outbound Pain Points: A Diagnostic Field Guide](https://www.plura.ai/articles/rcs-outbound-pain-points/?utm_term=rcs-outbound-limitations-2026&utm_campaign=ai_growth_agent)
- [What Is RCS Outbound? A Guide for Business Senders](https://www.plura.ai/articles/what-is-rcs-outbound/?utm_term=rcs-outbound-limitations-2026&utm_campaign=ai_growth_agent)
- [RCS Outbound Best Practices: The 2026 Operator’s Playbook](https://www.plura.ai/articles/rcs-outbound-best-practices-2026/?utm_term=rcs-outbound-limitations-2026&utm_campaign=ai_growth_agent)
- [RCS Outbound Setup: Registration, API, and SMS Fallback](https://www.plura.ai/articles/rcs-outbound-setup-guide/?utm_term=rcs-outbound-limitations-2026&utm_campaign=ai_growth_agent)

---

## Structured Data

**@graph:**

  **FAQPage:**

  **MainEntity:**

    **Question:**

    - **Name:** How Should I Read RCS Delivery Receipts?
      **Answer:**

      - **Text:** Treat the delivery receipt as your primary diagnostic tool. Start by distinguishing synchronous API rejections from carrier-level undeliverable statuses and from silent SMS fallback. That separation tells you whether to adjust payload, registration and reputation, or fallback configuration.
    **Question:**

    - **Name:** Why Are My Messages Sending As SMS Instead Of RCS?
      **Answer:**

      - **Text:** The platform falls back when the recipients device or carrier cannot accept RCS, the recipient disabled chat features, or the device was offline at delivery. Without a configured fallback, those recipients would receive nothing. As noted in the fallback section, the downgrade cannot complete without a provisioned SMS sender. Check delivery receipts for the channel used on each message, not just the top-line delivered count.
    **Question:**

    - **Name:** Can You Use RCS Without Data?
      **Answer:**

      - **Text:** RCS traffic requires an active cellular data or Wi-Fi connection to send and receive. SMS uses the cellular signaling channel, which is why fallback to SMS succeeds when RCS cannot. A device that goes offline between the capability check and the send can still produce a failed RCS delivery even when the pre-send lookup showed the number as RCS-capable.
    **Question:**

    - **Name:** How Big Of A File Can You Send Over RCS?
      **Answer:**

      - **Text:** The 100 MB API ceiling and the roughly 5 MB video limit described earlier are the two figures that matter most for media-heavy campaigns. Treat those numbers as planning anchors and validate with the actual file types and sizes your campaign will use before sending at volume.
    **Question:**

    - **Name:** Why Is My iPhone Sending RCS Instead Of iMessage?
      **Answer:**

      - **Text:** iMessage is Apples proprietary messaging service and applies only between Apple devices. When an iPhone messages a non-Apple recipient, the device uses RCS if the carrier supports it and the recipients device is RCS-capable, and SMS otherwise. RCS on iPhone requires iOS 18 or later and a carrier that has enabled RCS for that plan and region. The RCS Messaging toggle appears under Settings, and if it is absent, the carrier may not support RCS for that specific plan or device. Bubble color alone cannot confirm the channel used, because iOS displays RCS, SMS, and MMS conversations in the same green bubble.

  **BlogPosting:**

  - **Headline:** RCS Outbound Limitations: A Failure Diagnostic Guide
  - **Description:** Diagnose RCS send failures fast. Plura AI covers payload limits, fallback logic, rate limiting, and pre-flight testing for messaging ops teams.
  - **DateModified:** 2026-09-29T07:00:20.001Z
  - **Image:** https://cdn.aigrowthmarketer.co/1779338832429-847c53c76db5.png, https://cdn.aigrowthmarketer.co/1779338938448-00c130f59594.png, https://cdn.aigrowthmarketer.co/1779339090994-980045ddacd2.png, https://cdn.aigrowthmarketer.co/1779338680098-bf2bbd201647.png, https://cdn.aigrowthmarketer.co/1779337911454-8c3a9645d906.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

- [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.39.0*
*Generated on: 2026-11-12 15:46:52 GMT+0000*