William Dudley RCS, SMS

The Messaging Paradox: Why 98% Open Rates are Being Strangled by 20th-Century Vetting

Futuristic data processing device emitting streams of binary code in a data center A futuristic device displaying streams of digital data in a server room

We are living in a bizarre era of business messaging. On one hand, the “Year of RCS” is finally here, and on the other, 10DLC has become the backbone of American A2P. The data is clear: 89% of U.S. consumers have now signed up for texts from at least one business, and open rates still hover at a staggering 98%.

But there’s a massive “but.”

While the consumer is ready, the industry is choking. We are applying 2023 guidelines to 2026 realities. The FCC’s new “One-to-One Consent” rule (which went live in January 2026) has effectively killed the “lead generator loophole,” but in its wake, it has created a vetting vacuum for complex business models.

The RCS Logjam: A Bottleneck of Our Own Making

While the industry heralds the arrival of RCS as the “gold standard” of engagement, the reality on the ground is a different story. According to recent industry reports, the average lead time for a brand to go from registration to “live” on RCS has ballooned. We aren’t just talking about a few extra days; we are seeing weeks—sometimes months—of administrative purgatory.

Analysts have noted that this “bottlenecking” is the single greatest threat to RCS adoption, as brands lose momentum and ROI while waiting for manual approvals that don’t scale. We have the technology for rich, verified messaging, but we are currently managing the gate with a clipboard and a red pen.

The “Message Drift” Dilemma: Why Static Registrations Fail Dynamic Brands

In the current ecosystem, a brand registers a campaign with five sample messages. Those samples are frozen in time, acting as “Approved” guardrails. But in the real world—especially in the service and marketing industries—messaging “drifts.”

A service notification might morph from a simple arrival alert to include a follow-up feedback link or a seasonal maintenance reminder. A marketing team might decide on a Wednesday that they need a specific push for the upcoming weekend. Under the current regime, adding these new messages requires a full re-submission or a prayer that the “drift” isn’t flagged during a carrier audit.

We need a “Dynamic Addendum” Standard. Instead of a “once-and-done” registration, we should be discussing a framework that allows for Verified Appendages: the ability to add new sample messages to an existing, approved registration in real-time.

Addressing the Exploits: How We Keep the Bad Actors Out

To maintain the KYC integrity of 10DLC and RCS, we must acknowledge how bad actors might try to game this flexibility. We have to solve for:

  • The “Trojan Horse”: Registering a clean transactional campaign and slowly “drifting” it into prohibited content (e.g., gambling or debt relief).
  • The “Midnight Blast”: Adding a spam message on Friday night to send a million-message blast before auditors return on Monday.

The Safeguards: The Four Pillars of Dynamic Compliance

To allow for flexibility without sacrificing security, the Verified Platform tier must implement four specific technical safeguards:

  1. Semantic Intent Guardrails: Every “added” message is programmatically compared against the Original Approved Use Case. If a campaign approved for “Transactional Alerts” suddenly includes marketing keywords (e.g., “Sale” or “Discount”), the system triggers an immediate “Hard Stop” for manual re-vetting.
  2. The Velocity & Volume Lock: Any newly added “Appendage” message should be subject to a temporary throughput cap for the first 24–48 hours. This prevents the “Midnight Blast” by ensuring no new message can go to high volume until the system has analyzed initial delivery data.
  3. The “Reputation Ledger”: If an added message triggers a “STOP” or “Report Junk” rate significantly higher than the campaign’s historical baseline, the message is automatically revoked and the campaign is suspended. Brands must “own” their drift.
  4. Hash-Verified Appendages: Every added sample is “Hashed” (digitally fingerprinted) in the Registry. During a carrier audit, the live traffic must be a 95%+ semantic match to the registered hash, ensuring a brand can’t “bait and switch” their content.

By implementing these safeguards, we move from a system of “Gotchas” and “Policy Violations” to a system of Collaborative Compliance. If a brand maintains a low complaint rate and high deliverability, they earn the “Flexibility Credit” to move at the speed of business.

One Framework, Two Channels: Bridging the 10DLC and RCS Gap

The beauty of this “Dynamic Addendum” logic is that it isn’t limited to 10DLC. In fact, it is the missing link for the widespread adoption of RCS Business Messaging.

RCS is designed for rich, interactive experiences—carousels, high-res video, and suggested reply buttons. However, because the vetting process is currently so labor-intensive, many agencies are hesitant to move their most time-sensitive “Event” traffic to the channel.

Imagine this scenario: An agency is planning a major brand activation for a Saturday festival. On Tuesday, a new sponsorship deal is signed, requiring a change to the RCS Carousel—adding a new image, a new “Buy Now” button, and updated branding. Under the current manual-approval regime, that change is a gamble. If the vetting takes 72 hours, the campaign is dead on arrival.

The Solution: Unified Dynamic Vetting If we apply the “Four Pillars” of dynamic compliance to RCS, we unlock the true potential of the channel:

  • Verified Rich-Media Appendages: Just as we hash text for 10DLC, we can verify the intent of an RCS carousel update. If the call-to-action buttons and destination URLs remain consistent with the approved “Retail” or “Event” use case, the update should be approved programmatically.
  • Solving the RCS “Long Tail” Delay: By shifting the focus from “Approve every button change” to “Verify the Platform and the Workflow,” we eliminate the administrative backlog that currently keeps RCS in “early adopter” purgatory.

If a brand is already “Verified” on 10DLC and has a proven reputation ledger, that trust should be portable. The industry shouldn’t make a brand prove they are a “good actor” twice just because they want to upgrade from a 160-character text to a Rich Card. If a brand has spent three years maintaining a clean reputation ledger on 10DLC, that ‘social capital’ should be the key that unlocks faster onboarding for RCS. We should be rewarding good behavior with speed.

Whether it’s a Wednesday update for a Saturday 10DLC blast or a last-minute carousel tweak for an RCS event, the requirement is the same: Vetting must move at the speed of the message.

The New Realities: Three Standards the Industry Needs Now

The current “manual review” process is geared toward a single brand with a single website. But the most vital messaging ecosystems—CRMs, B2B2C platforms, and service industries—don’t fit that mold.

1. The B2B2C “Platform Delegated” Standard

  • The Reality: In platforms like Salesforce, HubSpot, or ShowingTime, thousands of individual sub-brands (agents, franchises) are the ones communicating.
  • The Problem: Vetting 50,000 individual agents with unique screenshots is an operational nightmare.
  • The Proposed Standard: A “Verified Platform” tier. If a major CRM can prove a mandatory, standardized opt-in workflow, the industry should vet the Workflow rather than the screenshot.
  • The “Dynamic Addendum”: This tier should allow platforms to submit “Verified Appendages”—new sample messages added to an existing registration in real-time. If a brand maintains low complaints, they earn the flexibility to update messaging without a 14-day wait.

2. The “Documented Offline” Consent Protocol

  • The Reality: Consent for service notifications often happens via a signed physical work order, a verbal agreement on a recorded call, or an in-person POS interaction.
  • The Problem: Carriers still hunt for “URLs” in registrations. No website often means a rejected campaign.
  • The Proposed Standard: Recognition of Non-Digital Metadata. Allow the submission of “Verification Logs” (e.g., Recorded Call ID #123 or Work Order #ABC) as proof of consent.

3. The ISP/Utility “Implicit Essential” Tier

  • The Reality: There is a difference between a pizza coupon and a notice that “Your Water Will Be Shut Off in 2 Hours.”
  • The Problem: High-utility messages are getting caught in “purgatory” because they lack marketing-grade opt-in documentation.
  • The Proposed Standard: Create a “Utility/Essential” path. These entities have pre-existing service contracts. The standard should shift from “Prior Express Written Consent” to “Prior Express Consent” with a focus on Service Continuity.

Moving Beyond “Policy Violation”

Messaging is no longer just a marketing tool; it’s an operational necessity. When a campaign is rejected, a “Policy Violation” notice is a failure of the system, not the brand. We need transparent remediation—real-world, interpreted examples of what does work for B2B2C and offline consent—to be baked into the standards themselves.

The CTIA last updated its principles in 2023. In the three years since, the “One-to-One” rule changed the game and RCS became the default for the world’s largest OS. It’s time our compliance standards caught up to the technology we’ve built. Let’s stop holding the industry back with old rules. We don’t need more ‘Policy Violation’ notices; we need industry standards  and a vetting framework that understand how business actually happens in 2026