# RCS Outbound Setup: Registration, API, and SMS Fallback

> Set up RCS outbound messaging right: agent registration, webhooks, and SMS fallback on one platform. Plura AI handles it without custom dev work.

**Published:** 2026-09-02 | **Updated:** 2026-11-06 | **Author:** plurasync
**URL:** https://www.plura.ai/articles/rcs-outbound-setup-guide
**Type:** post

**Categories:** AI SMS Automation

![RCS Outbound Setup: Registration, API, and SMS Fallback](https://plura.sites.aigrowthagent.co/wp-content/uploads/sites/75/2026/09/1788256744744-ca933033b8d9-1024x572.webp)

---

## Content

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

*Updated September 2026*

## Key Takeaways

- RCS outbound setup runs through four stages: agent registration with brand verification, carrier launch registration with compliance documentation, SMS/MMS fallback configuration, and outbound API plus webhook implementation.
- Brand assets must match exactly across submissions, and mismatches in legal name, logo, or use-case selection are the most common causes of registration rejection.
- US carrier launch involves independent reviews by Verizon, AT&T, and T-Mobile, typically taking 6-12 weeks total with possible back-and-forth for additional documentation.
- SMS fallback remains essential because only about 70% of US smartphones support RCS, and fallback content must be written separately from rich RCS elements like cards and suggestion chips.
- Running all four stages on one platform reduces the coordination overhead of managing registration, launch, fallback, and webhooks across separate vendor consoles.

[See how Plura handles RCS registration and fallback on one platform](https://www.plura.ai/plura-webchat?utm_term=rcs-outbound-setup-guide&utm_campaign=ai_growth_agent)

## Prerequisites And Provider Selection

Clean, consistent brand assets prevent the registration rejections that slow launches. Before starting registration, gather the brand assets and legal details below, because mismatches between these items and your verified brand cause most rejections.

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

- Legal brand name and customer-facing display name
- Logo image ([224×224 px, PNG or JPEG, max 50 KB](https://help.postscript.io/en/articles/15349327-get-started-with-rcs-apply-through-postscript))
- Banner image ([1440×448 px, PNG or JPEG, max 200 KB](https://help.postscript.io/en/articles/15349327-get-started-with-rcs-apply-through-postscript))
- Brand description (max 100 characters, no marketing slogans)
- Privacy policy URL and terms of service URL
- Business EIN and registered mailing address
- Use-case classification (Transactional, Promotional, Multi-Use, or OTP)
- Opt-in evidence and opt-out flow documentation
- A physical test device with a US-based RCS-capable number

Provider selection determines how much of the registration and carrier launch work your team handles directly. CPaaS resellers route traffic through a third-party carrier layer, which spreads registration, compliance review, and fallback configuration across multiple vendor consoles. Plura AI is its own FCC-licensed audio bridging carrier, so RCS, SMS, and voice originate on Plura’s domestic infrastructure rather than a third-party CPaaS. For [CRM integration](https://plura.ai/integrations?utm_term=rcs-outbound-setup-guide&utm_campaign=ai_growth_agent) options and [pricing](https://plura.ai/pricing?utm_term=rcs-outbound-setup-guide&utm_campaign=ai_growth_agent), both are available on Plura’s site.

## How To Register An RCS Agent For Outbound Messaging

RCS agent registration submits your brand identity to Google’s RBM (RCS Business Messaging) platform and, through it, to the US carriers. The artifacts submitted during registration include:

![Plura RCS interface showing rich AI-powered messaging with interactive media, branded conversations, and customer engagement.](https://cdn.aigrowthmarketer.co/1779339360346-dcb25322efc5.png)**Plura RCS delivers rich AI-powered messaging with interactive media, branded experiences, and real-time customer engagement.**

- **Agent name:** The customer-facing display name shown in the message thread header, max 40 characters
- **Brand name:** Must match your verified legal entity exactly
- **Logo:** 224×224 px, PNG or JPEG, max 50 KB, no transparency, served from a publicly accessible HTTPS URL
- **Banner:** 1440×448 px, PNG or JPEG, max 200 KB
- **Description:** Up to 100 characters explaining how users interact with the agent, not a company bio
- **Privacy policy URL and terms of service URL**
- **Use-case selection:** OTP, Transactional, Promotional, or Multi-Use
- **Accent color:** A six-digit hex value meeting WCAG AA contrast standards, requiring a minimum 4.5:1 contrast ratio against white

Brand name, logo, and description mismatches are the most common cause of rejection, because the agent identity submitted to carriers must match the verified brand exactly. A display name that differs from the legal entity name, or a logo that does not match the brand’s registered identity, triggers a rejection that requires a full re-registration rather than a simple correction. Telnyx’s RCS onboarding documentation notes that registration fields are locked after submission and the brand remains editable only while its status is CREATED.4

Use-case selection also affects carrier review. Selecting MULTI_USE when only transactional messages will be sent is a common error. MULTI_USE should only be selected if promotional messages will actually be sent, and promotional samples must be shown for carrier verification. Mismatched use-case declarations can result in rejection or post-launch content policy violations.

For a broader look at RCS outbound strategy before setup, see [What Is RCS Outbound? 2026 Business Guide To RCS Messaging](https://www.plura.ai/articles/what-is-rcs-outbound/?utm_term=rcs-outbound-setup-guide&utm_campaign=ai_growth_agent).

## RCS Carrier Launch Requirements In The US

After agent registration is approved, each US carrier requires a separate launch registration. The three major US carriers, Verizon, AT&T, and T-Mobile, each review independently. [Full US coverage requires approval from all three](https://sendblue.com/blog/rcs-business-messaging-setup-guide), covering roughly 95% of US wireless subscribers.3

The carrier launch submission requires a compliance screen recording.2 Bandwidth’s RCS launch documentation specifies that the recording must demonstrate:4

- A greeting explaining what the agent offers and how an end user can opt in, with double opt-in strongly advised
- The opt-in confirmation message the end user receives after opting in, including how they can request help or opt out
- A sample message demonstrating the agent’s use case
- HELP keyword handling, showing the exact response when a user sends HELP
- STOP keyword handling, showing the exact response when a user sends STOP
- An indication that message and data rates apply, which Bandwidth describes as best practice

The recording must be captured from a physical handset. Beyond content, the recording format matters, and not all carriers accept video. Some carriers accept screenshots instead, covering the web opt-in URL or CTA used to capture user consent, the opt-in confirmation, a sample message, and HELP or STOP keyword handling. If HELP and STOP auto-responses are not already implemented on your side, confirm with your provider whether they can temporarily enable them and what exact response text is required for each keyword.

Once the launch submission is in, agent details are locked. [Postscript’s RCS documentation](https://help.postscript.io/en/articles/15349327-get-started-with-rcs-apply-through-postscript) warns that any changes to the logo, banner, or agent configuration after submission require a full relaunch, which causes significant delays.4 Finalize all brand assets before submitting.

## RCS Agent Stuck In Pending Or Setting Up

After submission, your agent will sit in “pending” or “setting up” status while it waits on one or more external review steps. [The review sequence typically runs: third-party brand vetting (such as Aegis verification), Google brand approval, then individual carrier review](https://help.postscript.io/en/articles/15349327-get-started-with-rcs-apply-through-postscript). [Carrier review does not begin until brand vetting is finished](https://help.postscript.io/en/articles/15349327-get-started-with-rcs-apply-through-postscript), so delays in the vetting step push the entire timeline.

Review timelines vary by carrier and use case. [Expect 2-4 weeks per carrier for initial review](https://sendblue.com/blog/rcs-business-messaging-setup-guide), with possible back-and-forth for additional documentation. [Regulated industries such as healthcare and finance can take 6-8 weeks per carrier](https://sendblue.com/blog/rcs-business-messaging-setup-guide). [Total timeline from initial registration to full US coverage across all three carriers is commonly cited at 6-12 weeks](https://sendblue.com/blog/rcs-business-messaging-setup-guide).3 [OneSignal’s RCS documentation](https://onesignal.com/blog/rcs-for-skeptics-answering-the-questions-keeping-marketers-on-plain-sms) cites 8-16 weeks for sender approval.

Each carrier reviews independently. Once a carrier approves the agent, it launches with that carrier and commercial traffic can be sent through that carrier even if the agent is still pending on others. An agent can be partially launched and sending on one carrier while still in review on the remaining carriers.

While waiting, use the pre-launch test environment productively:

- Validate rich cards, carousels, and suggested actions on real Android and iPhone handsets
- Confirm inbound webhooks fire correctly for replies and delivery receipts
- Test the opt-out flow end to end
- Verify SMS fallback triggers when RCS is unavailable

Test devices must be physical handsets with a SIM or eSIM. Toll-free numbers cannot be used as test numbers. The test device receives an invitation from RBM Tester Management and must accept it within 24 hours. AWS documents that the tester invitation arrives within 2-20 minutes and the device status must show VERIFIED before test messages can be sent. For Telnyx, T-Mobile and AT&T numbers cannot be added as test devices for US RCS agents.

See Plura’s RCS launch and testing workflow in action

## How To Set Up RCS Webhooks For Delivery Receipts

Webhook wiring turns carrier events into usable delivery and engagement data. RCS webhook wiring covers two directions: outbound status events such as delivery, read, TTL expiration, and fallback, and inbound interaction events such as user replies, suggestion chip taps, and typing indicators.

For outbound status events, AWS End User Messaging routes delivery, read, expiration, and fallback events through configuration set event destinations to Amazon SNS, Amazon Data Firehose, or Amazon CloudWatch Logs. The key status values to handle are:

- **PENDING:** The RCS platform accepted the message but has not yet delivered it. Start your fallback timer.
- **DELIVERED:** The message reached the recipient’s device. Cancel any pending fallback timers.
- **UNDELIVERABLE:** The platform cannot deliver the message. Trigger SMS or MMS fallback and flag the number for future routing.
- **REJECTED:** Content policy violation. Review message content.

For inbound events, suggestion chip taps (postback events) are delivered to the two-way SNS topic configured on the RCS agent, not to configuration set event destinations. AWS recommends designing PostbackData values as structured identifiers such as `action:confirm_order:12345` so routing logic can parse them programmatically rather than relying on display text.

[RCS Studio’s webhook documentation](https://docs.rcsstudio.ai/reference/forwarding-messages-via-webhook) [distinguishes three event classes.](https://docs.rcsstudio.ai/reference/forwarding-messages-via-webhook) UserMessage fires when a user sends a message or taps a chip. UserEvent covers delivery confirmation, read receipt, typing indicator, and subscribe or unsubscribe. ServerEvent covers server-side outcomes including SENT, FAILED, and TTL events. [Each webhook POST includes an HMAC-SHA512 signature header for verification.](https://docs.rcsstudio.ai/reference/forwarding-messages-via-webhook) Implement idempotent event processing using the message ID plus event type as a deduplication key to handle out-of-order or duplicate deliveries.

Webhook wiring also determines how rich content is rendered. Rich card payloads require CardOrientation (VERTICAL or HORIZONTAL). AWS recommends VERTICAL because horizontal orientation truncates images on iOS. Carousels support 2-10 cards and do not support the TALL media height. Suggestion chips support up to 11 per message, with text labels limited to 25 characters.

Plura runs RCS on the same stateful conversation database as its [AI SMS](https://plura.ai/ai-sms-leads?utm_term=rcs-outbound-setup-guide&utm_campaign=ai_growth_agent) and AI Voice, so an agent that texted a lead at 9 a.m. picks up the RCS thread at noon already knowing what was said. For [AI customer service texting](https://plura.ai/ai-sms-customer-service?utm_term=rcs-outbound-setup-guide&utm_campaign=ai_growth_agent) and CRM-connected SMS support, that cross-channel memory turns a series of sends into a single conversation.

## How To Configure SMS Fallback For RCS

SMS fallback keeps reach high when RCS is unavailable. It ensures recipients on devices without RCS enabled still receive the message, including iPhone users without RCS enabled and Android users on carriers or devices that do not support RCS. Roughly 70% of US smartphones are RCS-capable as of April 2026, meaning 30% of a typical US audience requires fallback.3

![Plura SMS interface showing AI-powered business messaging, automated conversations, and real-time customer engagement tools.](https://cdn.aigrowthmarketer.co/1779339391664-96e3974c3c7f.png)**Plura SMS powers AI-driven business texting with automated conversations, customer engagement, and real-time communication workflows.**

Fallback triggers in three primary cases:

- The recipient’s device or carrier does not support RCS
- The RCS channel rejects the message
- The TimeToLive expiration window elapses before delivery confirmation

To avoid double-sends, the platform must attempt to revoke the original RCS message before the SMS fallback sends. MessageFlow’s fallback documentation describes this as a deduplication step that lower-quality implementations skip, which can result in a recipient receiving both the RCS and SMS versions. AWS distinguishes TTL_EXPIRATION_REVOKED (safe to trigger fallback) from TTL_EXPIRATION_REVOKE_FAILED (message might still deliver, evaluate duplicate risk before sending fallback).

Fallback content must be written separately from RCS content. Suggestion chips and rich cards do not translate to SMS. AWS advises writing fallback content independently, using plain URLs in SMS fallback or MMS fallback to preserve visual content. SMS fallback content can be up to 1,600 characters at the API layer. However, SMS itself carries a 160-character limit per segment, so longer messages split into multiple segments. That segmentation can increase sending costs. MMS fallback supports text and images but requires additional setup and is not supported out of the box by every platform.

Log which channel delivered each message. [Devotel Orbit recommends reporting delivered-on-RCS and delivered-on-SMS as two separate numbers per destination market](https://orbit.devotel.io/en/blog/rcs-sms-fallback-strategy) rather than a blended delivered figure, because a market with a 95% or higher fallback rate is effectively an SMS market and a blended number hides that signal. Once your fallback configuration is live, the next step is optimizing outbound performance; see [RCS Outbound Best Practices For Enterprise Operators](https://www.plura.ai/articles/rcs-outbound-best-practices-2026/?utm_term=rcs-outbound-setup-guide&utm_campaign=ai_growth_agent) for that.

## Business RCS vs. Consumer RCS Settings

Before moving to provider choice and platform architecture, separate business RCS setup from consumer RCS settings, because they appear together in search results and confuse teams mid-implementation. This guide covers business RCS setup only.

Consumer RCS settings refer to the options a person configures on their personal handset, such as turning RCS chat features on or off in Google Messages or Apple Messages, managing read receipts, or troubleshooting a “setting up” status that appears when a device is registering with a carrier’s RCS network. Those steps are handled in the device’s messaging app settings and are outside the scope of business messaging registration.

Business RCS setup, also called RCS Business Messaging (RBM) or A2P RCS, involves creating a verified business agent, completing brand and carrier registration, and wiring an outbound API. The “pending” or “setting up” status that operators encounter is a carrier review state on the business agent, not a device configuration issue.

## How Provider Choice Affects RCS Outbound Setup

Provider choice shapes how much of the registration, carrier launch, and fallback work your team manages across separate systems. Some CPaaS providers require separate consoles and credential sets for RCS registration, carrier launch, fallback routing, and webhook wiring. Plura runs RCS, SMS, and voice on its own FCC-licensed carrier infrastructure, so registration, carrier launch, fallback configuration, and webhook wiring run on one domestic platform instead of a third-party CPaaS layer.

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

## Frequently Asked Questions

### What Is An RCS Test Device?

An RCS test device is a physical handset with a SIM or eSIM and a US-based RCS-capable phone number that has been registered with your RCS agent before carrier launch. The device receives an invitation from RBM Tester Management and must accept it to reach Ready status. Only devices in Ready status can receive test messages. Toll-free numbers cannot be used as test devices. Test number limits vary by provider: [Google’s RBM testing sandbox allows up to 20 test phone numbers](https://sendblue.com/blog/rcs-business-messaging-setup-guide), while Bandwidth pre-launch agents deliver to 10 pre-approved handsets.

### Why Is My RCS Agent Still Pending?

An RCS agent stays in pending because one or more external review steps have not completed. The review sequence and 6-12 week timeline described above apply here, and the most common cause of delay is a slow response to vetting requests from Aegis or Google.

### Does Outbound RCS Fall Back To SMS Automatically?

Fallback behavior depends on the provider and how fallback is configured. AWS End User Messaging includes automated SMS fallback with no additional application logic required. Twilio handles fallback through a Sender Pool containing both an RCS sender and an SMS-capable number. Sinch routes to SMS automatically through its Conversation API. In all cases, fallback content must be written separately from RCS content because suggestion chips and rich cards do not translate to SMS.

### What Does The RCS Compliance Screen Recording Need To Show?

The compliance screen recording must cover the same elements listed in the carrier launch section: greeting, opt-in confirmation, sample message, HELP handling, and STOP handling. The RCS compliance video should indicate that message and data rates apply, which Bandwidth describes as best practice. The recording must be captured from a physical handset. Some carriers accept screenshots instead of video, covering the same elements.

### How Long Does RCS Carrier Launch Review Take?

Expect 2-4 weeks per carrier for initial review, with possible back-and-forth for additional documentation. Regulated industries such as healthcare and finance can take 6-8 weeks per carrier. Because the three major US carriers review independently, total time from submission to full US coverage across Verizon, AT&T, and T-Mobile commonly runs 6-12 weeks. Third-party brand vetting must complete before carrier review begins, so delays in vetting extend the overall timeline.

### What Happens To An Outbound RCS Message When The Recipient Is On An iPhone Without RCS Enabled?

If SMS fallback is configured, the message is delivered as SMS to the recipient’s number. If fallback is not configured, the message is not delivered at all. The fallback message must be written as a standalone plain-text SMS because rich cards, carousels, and suggestion chips are stripped. If the RCS message contains action buttons with URLs, include a plain URL in the fallback text so the recipient can still reach the destination.

### Do I Need A Separate Provider For RCS And SMS?

Many CPaaS providers require separate credential sets, sender registrations, and API configurations for RCS and SMS. Providers that operate on their own carrier infrastructure can handle both channels on a single platform. Plura runs RCS, SMS, and voice on its own FCC-licensed carrier infrastructure, and its cross-channel memory keeps conversation context intact when a thread moves between RCS, SMS, and voice.

### How Does Plura AI Handle RCS Outbound Setup?

Plura handles RCS outbound setup on its own FCC-licensed carrier: agent registration and brand verification, carrier launch registration with the compliance screen recording, SMS/MMS fallback configuration, and outbound API and webhook wiring. Plura’s infrastructure is 100% US-based, with TCPA compliance support, DNC compliance support, and SHAKEN/STIR caller ID verification built into the platform.1 Plura supports compliance, and customers remain responsible for their own regulatory obligations.

## Conclusion: Run The Setup On One Platform

RCS outbound setup is a multi-stage launch project: agent registration and brand verification, carrier launch registration with the compliance screen recording, SMS/MMS fallback configuration, and outbound API and webhook wiring. The exact sequence and whether fallback is mandatory vary by provider. Each stage has specific artifact requirements, waiting windows, and failure modes that most provider documentation covers only within its own console scope.

Plura runs RCS, SMS, and voice on its own FCC-licensed carrier infrastructure. Plura Connect acts as Carrier of Record for its regulated communications services, and its memory-driven AI agents maintain stateful conversation context across channels. The same infrastructure that supports TCPA compliance support and DNC compliance support on SMS applies to every RCS send. An agent that texted a lead at 9 a.m. picks up the RCS thread at noon already knowing what was said.

See how Plura runs RCS, SMS, and voice on one carrier platform

[Run your numbers through Plura’s calculator to check your ROI in real time](https://plura.ai/calculator?utm_term=rcs-outbound-setup-guide&utm_campaign=ai_growth_agent)

[Compare plans and rates side by side](https://plura.ai/pricing?utm_term=rcs-outbound-setup-guide&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 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

- [RCS Outbound Service: Pricing, Contracts, and Go-Live](https://www.plura.ai/articles/buy-rcs-outbound-service/?utm_term=rcs-outbound-setup-guide&utm_campaign=ai_growth_agent)
- [RCS Outbound Orchestration and Multi-Channel Integration](https://www.plura.ai/articles/rcs-outbound-multichannel-integration/?utm_term=rcs-outbound-setup-guide&utm_campaign=ai_growth_agent)
- [RCS Outbound vs SMS: How to Route Outbound Messages in 2026](https://www.plura.ai/articles/rcs-outbound-vs-sms/?utm_term=rcs-outbound-setup-guide&utm_campaign=ai_growth_agent)
- [RCS Business Messaging Integration: The Complete Build Guide](https://www.plura.ai/articles/rcs-business-messaging-integration-guide/?utm_term=rcs-outbound-setup-guide&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-setup-guide&utm_campaign=ai_growth_agent)

---

## Structured Data

**@graph:**

  **FAQPage:**

  **MainEntity:**

    **Question:**

    - **Name:** What Is An RCS Test Device?
      **Answer:**

      - **Text:** An RCS test device is a physical handset with a SIM or eSIM and a US-based RCS-capable phone number that has been registered with your RCS agent before carrier launch. The device receives an invitation from RBM Tester Management and must accept it to reach Ready status. Only devices in Ready status can receive test messages. Toll-free numbers cannot be used as test devices. Test number limits vary by provider: Google’s RBM testing sandbox allows up to 20 test phone numbers, while Bandwidth pre-launch agents deliver to 10 pre-approved handsets.
    **Question:**

    - **Name:** Why Is My RCS Agent Still Pending?
      **Answer:**

      - **Text:** An RCS agent stays in pending because one or more external review steps have not completed. The review sequence and 6-12 week timeline described above apply here, and the most common cause of delay is a slow response to vetting requests from Aegis or Google.
    **Question:**

    - **Name:** Does Outbound RCS Fall Back To SMS Automatically?
      **Answer:**

      - **Text:** Fallback behavior depends on the provider and how fallback is configured. AWS End User Messaging includes automated SMS fallback with no additional application logic required. Twilio handles fallback through a Sender Pool containing both an RCS sender and an SMS-capable number. Sinch routes to SMS automatically through its Conversation API. In all cases, fallback content must be written separately from RCS content because suggestion chips and rich cards do not translate to SMS.
    **Question:**

    - **Name:** What Does The RCS Compliance Screen Recording Need To Show?
      **Answer:**

      - **Text:** The compliance screen recording must cover the same elements listed in the carrier launch section: greeting, opt-in confirmation, sample message, HELP handling, and STOP handling. The RCS compliance video should indicate that message and data rates apply, which Bandwidth describes as best practice. The recording must be captured from a physical handset. Some carriers accept screenshots instead of video, covering the same elements.
    **Question:**

    - **Name:** How Long Does RCS Carrier Launch Review Take?
      **Answer:**

      - **Text:** Expect 2-4 weeks per carrier for initial review, with possible back-and-forth for additional documentation. Regulated industries such as healthcare and finance can take 6-8 weeks per carrier. Because the three major US carriers review independently, total time from submission to full US coverage across Verizon, AT&T, and T-Mobile commonly runs 6-12 weeks. Third-party brand vetting must complete before carrier review begins, so delays in vetting extend the overall timeline.
    **Question:**

    - **Name:** What Happens To An Outbound RCS Message When The Recipient Is On An iPhone Without RCS Enabled?
      **Answer:**

      - **Text:** If SMS fallback is configured, the message is delivered as SMS to the recipient’s number. If fallback is not configured, the message is not delivered at all. The fallback message must be written as a standalone plain-text SMS because rich cards, carousels, and suggestion chips are stripped. If the RCS message contains action buttons with URLs, include a plain URL in the fallback text so the recipient can still reach the destination.
    **Question:**

    - **Name:** Do I Need A Separate Provider For RCS And SMS?
      **Answer:**

      - **Text:** Many CPaaS providers require separate credential sets, sender registrations, and API configurations for RCS and SMS. Providers that operate on their own carrier infrastructure can handle both channels on a single platform. Plura runs RCS, SMS, and voice on its own FCC-licensed carrier infrastructure, and its cross-channel memory keeps conversation context intact when a thread moves between RCS, SMS, and voice.
    **Question:**

    - **Name:** How Does Plura AI Handle RCS Outbound Setup?
      **Answer:**

      - **Text:** Plura handles RCS outbound setup on its own FCC-licensed carrier: agent registration and brand verification, carrier launch registration with the compliance screen recording, SMS/MMS fallback configuration, and outbound API and webhook wiring. Plura’s infrastructure is 100% US-based, with TCPA compliance support, DNC compliance support, and SHAKEN/STIR caller ID verification built into the platform. Plura supports compliance, and customers remain responsible for their own regulatory obligations.

  **BlogPosting:**

  - **Headline:** RCS Outbound Setup: Registration, API, and SMS Fallback
  - **Description:** Set up RCS outbound messaging right: agent registration, webhooks, and SMS fallback on one platform. Plura AI handles it without custom dev work.
  - **DateModified:** 2026-09-29T09:22:00.099Z
  - **Image:** https://cdn.aigrowthmarketer.co/1779337911454-8c3a9645d906.png, https://cdn.aigrowthmarketer.co/1779339360346-dcb25322efc5.png, https://cdn.aigrowthmarketer.co/1779339391664-96e3974c3c7f.png, https://cdn.aigrowthmarketer.co/1779338680098-bf2bbd201647.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:41:50 GMT+0000*