# RCS Outbound Cost Per Message: 2026 U.S. Operators Guide

> Break down every line on your RCS invoice. Plura AI helps contact center and marketing leaders control outbound messaging costs at scale.

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

**Categories:** AI SMS Automation

![RCS Outbound Cost Per Message: 2026 U.S. Operators Guide](https://plura.sites.aigrowthagent.co/wp-content/uploads/sites/75/2026/07/1784626046636-8fa0a672a335-1024x572.webp)

---

## Content

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

*Updated September 2026.*

## Key Takeaways

- RCS outbound cost per message combines provider or transport fees, carrier pass-through fees, session or per-segment billing, and one-time setup or verification costs.
- Published provider rates range from $0.0039 to $0.0083 per text segment and $0.015 to $0.022 per rich media message, with carrier fees adding another $0.0045–$0.0135 per message.
- Session-based billing becomes cheaper than per-segment billing after roughly 13 messages on AT&T and T-Mobile, and after only four messages on Verizon.
- One-time setup fees such as sender verification, brand vetting, TCR registration, and T-Mobile activation range from $250 to $500 and should be amortized across projected send volume.
- Plura AI owns its FCC-licensed carrier stack and removes the reseller markup that CPaaS providers add on every message.

[See how Plura prices RCS at carrier cost](https://www.plura.ai/plura-webchat?utm_term=rcs-outbound-cost-per-message&utm_campaign=ai_growth_agent)

## The Four Cost Components On Your RCS Invoice

### Provider Or Transport Fee

The provider or transport fee is what the platform charges to originate and deliver the message. This is the headline rate on a provider’s pricing page. Twilio publishes approximately $0.0083 per basic RCS segment, while Telnyx comes in at $0.0065 per segment.4 [Plivo sits at $0.0077 per segment](https://simplyrcs.ai/compare/vs-plivo)4, and AWS End User Messaging publishes $0.007 per segment. These rates cover transport only, and carrier fees land on a separate line.

### Carrier Pass-Through Fee

The carrier pass-through fee is what the destination carrier charges per segment or per message. Twilio’s published carrier fee table shows AT&T at $0.0045, T-Mobile at $0.0062, Verizon at $0.0045, and US Cellular at $0.0062 per RCS rich outbound message. AWS End User Messaging publishes carrier pass-through fees as a separate line item at $0.00494 per rich segment and $0.00949 per rich media message. [Verizon’s outbound A2P pass-through fee rises from $0.0045 to $0.005 per message on October 1, 2026](https://bluereacher.com/blog/verizon-october-fee-rise-and-rcs-session-billing), so budget models should reflect that change.

### Session Pricing Versus Per-Segment Billing

Per-segment billing charges for each 160-byte UTF-8 unit of text. Session-based billing charges one combined fee for all messages exchanged within a 24-hour window once a qualifying threshold is met. [Telgorithm publishes a session rate of $0.072 per 24-hour Conversational RCS session, with carrier fees passed through separately at AT&T $0.030, T-Mobile $0.060, Verizon $0.009, and US Cellular $0.060 per session](https://telgorithm.com/news/what-is-conversational-rcs-how-session-based-rcs-pricing-works).

[A session starts when an RBM agent and a user exchange four Rich or Rich Media messages within a 24-hour period, including at least one outbound brand message and at least two inbound user replies](https://usrbm.org/rbm-message-types-and-billing-paradigms). Session billing works best for high-turn, two-way conversations. AI assistants that complete interactions within a single 24-hour window are the primary fit. [On T-Mobile and AT&T, session billing beats per-message carrier fees only after roughly 13 messages in the window](https://bluereacher.com/blog/verizon-october-fee-rise-and-rcs-session-billing). [Verizon’s $0.009 session fee becomes cheaper from the fourth message](https://bluereacher.com/blog/verizon-october-fee-rise-and-rcs-session-billing).

### One-Time Setup And Verification Costs

Every U.S. RCS deployment carries fixed costs before the first message sends. These include:

- RCS sender setup fee: [$250 at SimplyRCS](https://simplyrcs.ai/learn/how-much-does-rcs-cost), $500 at AWS End User Messaging, and [$500 at Twilio](https://simplyrcs.ai/learn/rcs-providers-with-no-platform-fee).
- Annual brand vetting through Aegis: $200 per year at AWS and [$200 per year at Twilio](https://simplyrcs.ai/learn/rcs-providers-with-no-platform-fee).
- Monthly agent maintenance: $200 per month at AWS End User Messaging.
- The Campaign Registry (TCR) fees: [$4.50 brand registration, $15 campaign vetting, and $1.50 to $10 per month per campaign](https://simplyrcs.ai/learn/how-much-does-rcs-cost).
- T-Mobile one-time activation: [$500, passed through at cost by providers that itemize it](https://simplyrcs.ai/learn/rcs-providers-with-no-platform-fee).

These costs stay largely fixed regardless of send volume. They weigh more heavily on lower-volume deployments and amortize across higher-volume campaigns.

With the component structure established, the next step is to see how published provider rates compare across the market.

## Published Provider Rate Comparison

The table below reflects published per-message rates as of September 2026. Only providers that publish a U.S. rate card are included. Carrier pass-through fees are listed separately where the provider itemizes them.

| Provider | Published RCS Text Rate | Published RCS Media Rate | Source |
| --- | --- | --- | --- |
| Twilio | ~$0.0083 per segment | ~$0.0220 per message | Twilio pricing |
| Telnyx | $0.0065 per segment | $0.016 per message | Telnyx pricing |
| Plivo | [$0.0077 per segment](https://simplyrcs.ai/compare/vs-plivo) | [$0.0180 per message](https://simplyrcs.ai/compare/vs-plivo) | [Plivo pricing](https://simplyrcs.ai/compare/vs-plivo) |
| AWS End User Messaging | $0.007 per segment + $0.00494 carrier fee | $0.020 per message + $0.00949 carrier fee | AWS pricing |
| SimplyRCS | [$0.0039 per message](https://simplyrcs.ai/learn/how-much-does-rcs-cost) | [$0.0150 per message](https://simplyrcs.ai/learn/how-much-does-rcs-cost) | [SimplyRCS pricing](https://simplyrcs.ai/learn/how-much-does-rcs-cost) |
| Plura AI | Carrier-owned model, see [pricing page](https://plura.ai/pricing?utm_term=rcs-outbound-cost-per-message&utm_campaign=ai_growth_agent) | Carrier-owned model, see [pricing page](https://plura.ai/pricing?utm_term=rcs-outbound-cost-per-message&utm_campaign=ai_growth_agent) | [Plura pricing](https://plura.ai/pricing?utm_term=rcs-outbound-cost-per-message&utm_campaign=ai_growth_agent) |

Billing units differ across providers. [Telnyx, Plivo, and AWS bill rich text per 160-character segment, so a 300-character message counts as two billable units](https://simplyrcs.ai/blog/how-much-does-rcs-cost). [SimplyRCS and Twilio bill per message regardless of character count](https://simplyrcs.ai/learn/how-much-does-rcs-cost). That distinction matters when you model long transactional messages at scale.

[Get a custom RCS quote for your volume](https://www.plura.ai/plura-webchat?utm_term=rcs-outbound-cost-per-message&utm_campaign=ai_growth_agent)

## The Carrier-Ownership Variable: Why Rates Differ

Carrier ownership explains why identical RCS messages cost different amounts across providers. CPaaS resellers sit between the customer and the carrier network, route traffic through an aggregation layer, and stack a margin on top of the underlying route cost. [According to a May 2026 CPaaS Directory analysis, the effective price paid for CPaaS messaging can be 20 to 60 percent higher than the published headline rate once carrier surcharges, registration, and platform fees are added](https://cpaasdirectory.com/blog/cpaas-pricing-2026.html).3

[Providers that own their carrier infrastructure can price below resellers because there is no surcharge layer to pass through, which keeps headline and effective rates closer together](https://blog.yootelco.com/cpaas-vs-telecom-native-infrastructure-which-one-actually-delivers). This margin, sometimes called the wrapper tax, is what a CPaaS reseller adds on top of the carrier’s wholesale rate before passing the cost to the customer.

Plura AI owns its FCC-licensed carrier stack. Voice and messaging originate on Plura’s domestic infrastructure. Branded caller ID is issued at the carrier level. The platform enforces real-time DNC (Do Not Call) scrubbing, TCPA (Telephone Consumer Protection Act) litigator screening, and STIR/SHAKEN (Secure Telephone Identity Revisited/Signature-based Handling of Asserted information using toKENs) authentication on every outbound contact.1,2 For operators evaluating Plura against alternatives, the carrier-ownership variable is the single most important structural difference to verify in any RCS quote.

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

To confirm whether a provider owns its carrier access or rents it, ask directly whether the provider holds formal, operator-approved A2P (Application-to-Person) interconnect agreements or routes traffic through third-party aggregators. [Slow, inconsistent, or steadily declining delivery rates over time without any change on the sender’s end are a common symptom of aggregator dependency](https://blog.yootelco.com/cpaas-vs-telecom-native-infrastructure-which-one-actually-delivers).

## Worked Cost-Per-Campaign Example

The table below shows illustrative math at three volume tiers using Twilio’s published RCS rich outbound rate of $0.0083 per segment and AT&T’s published carrier pass-through fee of $0.0045 per message. Actual costs vary by provider, carrier mix, and message class.

| Volume | Provider Fee (at $0.0083/msg) | Carrier Pass-Through (at $0.0045/msg) | Total |
| --- | --- | --- | --- |
| 100K messages | $830 | $450 | $1,280 |
| 500K messages | $4,150 | $2,250 | $6,400 |
| 1M messages | $8,300 | $4,500 | $12,800 |

[At SimplyRCS’s published $0.0039 per message, the same 1M messages cost $3,900 in provider fees](https://simplyrcs.ai/learn/how-much-does-rcs-cost). That $4,400 difference before carrier pass-through is the carrier-ownership variable expressed in dollars. One-time setup costs such as sender verification, TCR brand registration, and T-Mobile activation add to the total regardless of volume tier and should be amortized across projected send volume when you build a budget model.

With the math in hand, the next step is knowing what to ask a vendor before you sign.

## Buyer’s Checklist For Evaluating An RCS Quote

Use these questions when you review any RCS vendor proposal. This is operator-to-operator guidance and not legal advice.

- **Is the carrier owned or rented?** Ask whether the provider holds formal, operator-approved A2P interconnect agreements or routes through third-party aggregators.
- **Is billing per-segment or session-based?** Ask whether rich text bills per 160-character segment or per message, and whether session billing is available for high-turn conversations.
- **What are the one-time verification fees?** Ask for the full list, including RCS sender setup, brand vetting, T-Mobile activation, and monthly agent maintenance.
- **What is the carrier pass-through rate and does it vary by destination carrier?** Ask for the per-carrier fee table in writing.
- **What is included in the provider fee?** Ask whether platform fees, support, AI metering, and number rentals are included or billed separately.
- **What do I owe in a month when I send nothing?** Use this as the test for any usage-based RCS quote.

[Talk with Plura about your RCS cost model](https://www.plura.ai/plura-webchat?utm_term=rcs-outbound-cost-per-message&utm_campaign=ai_growth_agent)

## Frequently Asked Questions

### How Much Does An RCS Message Cost?

For business messaging in the U.S., [published provider rates range from $0.0039 to $0.0083 per text message and $0.015 to $0.022 per rich media message](https://signalmash.com/post/rcs-business-messaging-cost-per-message), before carrier pass-through fees. As noted in the Key Takeaways, carrier fees add $0.0045 to $0.0135 per message depending on the carrier and message class. One-time setup and annual vetting fees sit outside per-message costs and should be modeled separately.

### Do RCS Messages Cost Money To Send?

RCS Business Messaging generates cost for the sending business. Consumer RCS on a personal phone is included in a mobile data or messaging plan and does not generate a separate per-message charge. A2P RCS traffic, meaning messages sent by a business to customers, is billed per message or per session by the messaging provider, with carrier pass-through fees added on top.

### Do RCS Texts Show Up On Your Phone Bill?

Consumer RCS messages do not appear as separate line items on a phone bill because they ride the data connection. Business RCS messages are billed to the sending business by its messaging provider, not to the recipient. The recipient sees no charge on their bill for receiving an RCS Business Message.

### Is RCS Better Than SMS?

RCS supports rich media, read receipts, suggested replies, and up to 3,072 characters per message, while SMS is limited to 160 characters of plain text per segment. For high-volume transactional or conversational use cases, RCS delivers more capability per message. The trade-off is a higher carrier pass-through cost and a more complex registration process. Every RCS send falls back to SMS or MMS on non-RCS devices, so SMS infrastructure remains part of the total cost model.

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

### Should My Text Messages Be RCS Or SMS?

For business messaging, RCS is the richer channel. As noted above, RCS falls back to SMS or MMS on non-RCS devices, so a 10DLC (10-digit long code) registration is still required. [As of September 2026, roughly 87 percent of U.S. smartphones can receive RCS](https://simplyrcs.ai/blog/best-rcs-business-messaging-platform-for-us-brands)2,3, which means the fallback portion of a typical U.S. send is now a smaller share of total traffic. The right mix depends on your audience’s device distribution, your message content, and whether the richer format justifies the higher carrier pass-through cost at your volume tier.

## Conclusion: Build Your RCS Cost Model

RCS outbound cost per message is the sum of four components: a provider or transport fee, a carrier pass-through fee, session-based or per-segment billing, and one-time setup and verification costs. The carrier-ownership variable explains why identical RCS messages cost different amounts across providers, because CPaaS resellers stack a margin on top of the underlying carrier rate. Platforms that own their carrier infrastructure keep that layer inside their own network. Modeling all four components at your volume tier, with the per-carrier fee table in writing, produces a defensible number for a budget meeting.

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

[Compare plans and rates side by side](https://plura.ai/pricing?utm_term=rcs-outbound-cost-per-message&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 Costs: How to Control What You Pay](https://www.plura.ai/articles/rcs-outbound-cost-reduction/?utm_term=rcs-outbound-cost-per-message&utm_campaign=ai_growth_agent)
- [RCS Business Messaging Pricing: What It Costs in 2026](https://www.plura.ai/articles/rcs-business-messaging-pricing-2026/?utm_term=rcs-outbound-cost-per-message&utm_campaign=ai_growth_agent)
- [RCS Business Messaging Pricing: What It Really Costs](https://www.plura.ai/articles/affordable-rcs-business-solutions/?utm_term=rcs-outbound-cost-per-message&utm_campaign=ai_growth_agent)
- [RCS Outbound Service: Pricing, Contracts, and Go-Live](https://www.plura.ai/articles/buy-rcs-outbound-service/?utm_term=rcs-outbound-cost-per-message&utm_campaign=ai_growth_agent)
- [RCS Outbound Delivery Rates: Benchmarks and How to Improve](https://www.plura.ai/articles/rcs-outbound-delivery-rates/?utm_term=rcs-outbound-cost-per-message&utm_campaign=ai_growth_agent)

---

## Structured Data

**@graph:**

  **FAQPage:**

  **MainEntity:**

    **Question:**

    - **Name:** How Much Does An RCS Message Cost?
      **Answer:**

      - **Text:** For business messaging in the U.S., published provider rates range from $0.0039 to $0.0083 per text message and $0.015 to $0.022 per rich media message, before carrier pass-through fees. As noted in the Key Takeaways, carrier fees add $0.0045 to $0.0135 per message depending on the carrier and message class. One-time setup and annual vetting fees sit outside per-message costs and should be modeled separately.
    **Question:**

    - **Name:** Do RCS Messages Cost Money To Send?
      **Answer:**

      - **Text:** RCS Business Messaging generates cost for the sending business. Consumer RCS on a personal phone is included in a mobile data or messaging plan and does not generate a separate per-message charge. A2P RCS traffic, meaning messages sent by a business to customers, is billed per message or per session by the messaging provider, with carrier pass-through fees added on top.
    **Question:**

    - **Name:** Do RCS Texts Show Up On Your Phone Bill?
      **Answer:**

      - **Text:** Consumer RCS messages do not appear as separate line items on a phone bill because they ride the data connection. Business RCS messages are billed to the sending business by its messaging provider, not to the recipient. The recipient sees no charge on their bill for receiving an RCS Business Message.
    **Question:**

    - **Name:** Is RCS Better Than SMS?
      **Answer:**

      - **Text:** RCS supports rich media, read receipts, suggested replies, and up to 3,072 characters per message, while SMS is limited to 160 characters of plain text per segment. For high-volume transactional or conversational use cases, RCS delivers more capability per message. The trade-off is a higher carrier pass-through cost and a more complex registration process. Every RCS send falls back to SMS or MMS on non-RCS devices, so SMS infrastructure remains part of the total cost model.
    **Question:**

    - **Name:** Should My Text Messages Be RCS Or SMS?
      **Answer:**

      - **Text:** For business messaging, RCS is the richer channel. As noted above, RCS falls back to SMS or MMS on non-RCS devices, so a 10DLC (10-digit long code) registration is still required. As of September 2026, roughly 87 percent of U.S. smartphones can receive RCS, which means the fallback portion of a typical U.S. send is now a smaller share of total traffic. The right mix depends on your audience's device distribution, your message content, and whether the richer format justifies the higher carrier pass-through cost at your volume tier.

  **BlogPosting:**

  - **Headline:** RCS Outbound Cost Per Message: 2026 U.S. Operators Guide
  - **Description:** Break down every line on your RCS invoice. Plura AI helps contact center and marketing leaders control outbound messaging costs at scale.
  - **DateModified:** 2026-09-29T07:26:11.826Z
  - **Image:** https://cdn.aigrowthmarketer.co/1779338832429-847c53c76db5.png, https://cdn.aigrowthmarketer.co/1779339360346-dcb25322efc5.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 13:30:34 GMT+0000*