When a message leaves your platform, most people assume it travels in a straight line to the subscriber’s device. It doesn’t. It moves through a network of hubs, hops, and handoffs — across aggregators, carriers, and industry bodies. By the time it reaches someone’s phone, that message has passed through a supply chain that most subscribers have never had to think about.
For years, that complexity stayed behind the scenes. Your job was to send the message. The underlying infrastructure, routing, and relationships were someone else’s problem.
That was true, until it wasn’t.
What “direct carrier relationships” actually means in practice
In my role at Bandwidth, I work across the messaging ecosystem — with carriers, enterprises, industry organizations, and technology providers. And one of the things I say often, because I believe it, is that messaging is fundamentally built on relationships. Technology matters. But so does who picks up the phone when something goes wrong.
Direct carrier connections aren’t a marketing term. They’re operational access. When something breaks, we don’t wait for an intermediary to surface the issue and relay it back to us. We’re already in conversation with the carrier. When a policy shifts or a new filtering behavior shows up in a network, we hear it from the carrier directly — not from a forum thread two weeks later. When a new product is being designed, we’re part of the conversation before it’s announced.
I spent more than 15 years at Sprint before joining Bandwidth, and the difference between direct and intermediated communication is not subtle. Firsthand information changes how fast you can act. It also changes the quality of what you can offer to the customers who depend on you.
RCS, and what it looks like to be in the room
Rich Communication Services (RCS) has been discussed in this industry since 2011 or 2012. It is only now reaching real brand adoption. That timeline tells you something important about how messaging infrastructure actually works: three major carriers, each making decisions about their own networks, not always sharing information with each other, each with its own policies and rollout cadence. The fragmentation is real, and it creates genuine complexity for anyone trying to build on top of it.
Today, with RCS finally in the market, there are still things being worked out. The billing model remains an open question. What the rules look like at scale. How the product gets operationalized. Those conversations are happening right now, and we’re in them. For our customers, that means they’re not navigating the ambiguity alone or learning about changes through a support ticket.
That’s not something we built overnight. It’s the result of years of showing up to the right industry conversations and building the relationships that make those conversations possible.
The Civic Engagement Ensemble, and what real access looks like
One of the things I’m most proud of is what we do with our carrier and industry relationships on behalf of our customers.
In April, we brought a group of customers to Raleigh for our Civic Engagement Ensemble. We gave them the chance to sit down, in person, with AT&T, CTIA, TCR, and Campaign Verify—not to listen to a panel, but to ask questions directly. To have the conversations that usually don’t happen for customers at their scale.
That kind of access is rare. And it’s only possible because of the relationships we’ve built over time.
The larger a messaging company gets, the more layers form between their customers and the industry infrastructure. Acquisitions, integrations, and organizational complexity all add distance. We’ve stayed close enough to the carriers and the industry bodies that we can close that distance for our customers when it matters.
For brands and customers, that matters in a specific, practical way. When your customers run into a campaign approval issue, a short code question, or a filtering problem they can’t explain, you need a partner who can get answers from the source. Not a ticket queue, but a live conversation with someone who has a real relationship with the carrier or the governing body involved.
Trusting the infrastructure behind your product
I get asked sometimes whether our platform customers need to understand all of this. My honest answer is: not all of it. You shouldn’t have to be a carrier relations expert to build a great messaging product. But you do need a partner who is. Someone who can tell you what’s coming before it hits, escalates when something goes sideways, and gets you into conversations you’d otherwise never be part of.
What I tell customers is this: trust that we are going to bat for you at every step of the chain. With carriers, with industry organizations, with aggregator partners. You don’t have to be in every conversation. But you should know that someone you trust is.
That trust has to be earned through years of building the right relationships and then putting those relationships to work when customers need them. RCS, A2P 10DLC, toll-free verification, short code approval—all of it is more navigable when the company moving your messages is an integral part of how those systems are being built and governed.
The infrastructure between your platform matters more than most product owners realize. So the question becomes: Who’s managing it on your behalf, and are they actually in the room with the full chain of decision makers.
Stephanie Lashley is VP of Messaging Strategic Alliances & Infrastructure at Bandwidth, where she leads the carrier relationships and platform partnerships that shape how enterprise A2P messaging gets built, registered, and delivered at scale. With over two decades in telecom, including her formative years at Sprint, she has been a hands-on architect of the 10DLC ecosystem and a consistent voice in global messaging governance through her work with the Mobile Ecosystem Forum. She speaks and writes at the intersection of infrastructure trust, RCS adoption, and the real-world compliance complexity that platforms and ISVs are navigating as the messaging landscape evolves.
