Eight Hours, Two Carriers, One Lesson Every Revenue Leader Needs to Hear

Eight Hours, Two Carriers, One Lesson Every Revenue Leader Needs to Hear

Ever been locked out of an account because you couldn't receive a two-factor authentication code?

Now imagine you're 76 years old, hard of hearing, and have no idea what two-factor authentication even means.

That was my mother-in-law last week. And what happened over the next eight hours turned into one of the clearest case studies I've ever personally experienced in what separates a customer-obsessed organization from one that just thinks it is.

The Setup

My mother-in-law is 76. She's hard of hearing, not particularly tech savvy, and in the middle of a major life transition. She's moving into our home. When she lost her mobile phone, she needed a replacement. We also decided it made more sense to move her onto our family plan at T-Mobile rather than keep her on a separate Verizon plan she'd been on for years.

Simple enough, right?

I spent part of the morning researching what the process would look like: how to port a number, what information we'd need, what to expect. We had a plan. We were prepared. And for the first part of the day, things went exactly as expected.

What I didn't plan for was that what should be an easy process would become almost impossible, simply because her phone was gone. Lost. Which meant that when it came time to authorize the number port, the step where the carrier sends a two-factor authentication code to verify identity, there was no phone to receive it. No device. No code. No automatic approval.

We were standing in the carrier's store, in-person with government-issued photo ID, ready to prove exactly who she was. We had live, in-person, 1-factor authentication. There isn’t any better authentication than a living, breathing body, in the company store, speaking directly to the company employee, with multiple forms of government issued picture identification. In any rational system, that should be enough. It wasn’t.

What followed was a demonstration of what happens when a company's systems and people are built only for the expected case.

Stop One: The T-Mobile Store

We started at T-Mobile. The associate we worked with, John, was excellent from the start. He understood the situation quickly, walked us through the options clearly, and got us set up with a new phone and a new line that would actually save her money compared to what she'd been paying.

John didn't miss a beat. He politely and clearly explained that we'd still need to go to Verizon to get her account number and set up a transfer PIN before the port could go through. (We had expected this from our earlier planning.) He told us once we had this, he would be happy to help us complete the process. He even told us what time his shift ended, and said any of his colleagues would happily handle the final step if we needed to come back after his shift, and then he sent us on our way with a clear action plan.

It took maybe 30 minutes. Professional, warm, efficient. Exactly what you'd want.

Stop Two: The Verizon Retail Store

We looked up the nearest Verizon location and found one a block and a half away. We walked over.

First problem: it was a Verizon authorized retailer, not a corporate-owned store. There was no indication on the website of this, nor was there any reason for us to expect this would make a difference. The associate there was polite and tried to help, but his hands were tied. He put us on the phone with Verizon's support line, where we explained the situation: lost phone, can't receive 2FA, in person with ID, need a workaround.

The agent on the phone told us there was nothing that could be done remotely and that we needed to go to a corporate-owned store in person.

So we found one. About a 10-minute drive away.

Stop Three: The Verizon Corporate Store

This is where things progressed from annoying, to genuinely difficult.

The associate at the corporate store, I'll call him Kevin, understood the situation. He wasn't confused about what we needed. What he made clear, fairly quickly and in a tone that communicated he was done engaging with the problem, was that there was nothing he could do and that he had no intention of trying to find out a way to help us.

His suggestions: we could buy her a new phone through Verizon, so they could send a 2FA message. We explained we were leaving Verizon. He reiterated that without the phone, there was nothing he could do.

He then directed us to get back on a call with Verizon's support center. Yes, back to the same people who told us to come to the company store in person.

Frustrated, but still looking to solve the problem, I asked Kevin to help us deal with the support center staff, since when we tried this on our own earlier, we got nowhere. Kevin reluctantly agreed to get us started on the phone, but he made it clear that the call was our problem to manage, not his.

I asked him directly to stay on the call with us and act as an advocate - to help us explain the situation and navigate toward whoever could actually resolve it. He was physically present for part of the call, but he wasn't engaged. He walked away multiple times. When he was there, he wasn't helping move things forward. He had handed us the phone and checked out.

What he would not do, under any circumstances, was take ownership of the outcome. He told us in fairly plain terms that he wasn't going to do anything outside the defined process because he didn't want to risk his job. The way he said it made clear that if we kept pushing, we were going to find ourselves being asked to leave the store.

I get that frontline associates have real constraints. I wasn't asking him to break rules. I was asking him to give a damn. Had he simply said "this is an unusual situation, I know our processes can be a challenge, let me do everything I can to help, but it might take some time," the whole experience would have been different. Instead what we got was a wall with a name tag. 

The Phone Calls

We dialed directly from the corporate store, using their landline, and we got on the phone with Verizon's call center. Multiple agents. Each one heard the situation, each one cycled through the same limited set of responses. Several of them kept suggesting they send a two-factor authentication code to the lost handset. We explained, repeatedly, that the handset was lost. That was the entire problem. We were stuck in an infinite loop of apathy and incompetence.

After more than 35 minutes on the phone, the call dropped.

We called back. Got a different agent. And this one was different.

She listened. She actually understood. She said she thought there was a workaround and she was going to find it. The solution turned out to be straightforward: Kevin would verify our ID in person at the store, log it in the customer record, and once that was documented she could authorize the automatic porting of the number, without requiring the 2FA step.

It worked. It took about 15 minutes once she was on the line.

Someone had built that process. It existed in their system. It was designed for exactly this situation. But in all the hours we had spent cycling through stores and agents before reaching her, not one person had known it was there. Not one person had been motivated enough to look for it.

I asked every single person I dealt with at Verizon - the retail associate, Kevin, the call center agents - to please flag this experience and escalate it internally so it could be addressed and so the next person wouldn't go through the same thing. Every one of them said they would. I am completely certain that not one of them did.

Stop 4: Back to T-Mobile

We returned to the T-Mobile store several hours after our first visit. It was past 4:30. John's shift had ended.

We ran into him on the sidewalk outside, heading home.

He recognized us immediately. Stopped. Asked how it went. Pointed us back inside and told us his colleague could take care of us.

We walked in. His colleague looked up and said: "Oh yes, we saw you earlier with John. The hard part's done. Let's just get this wrapped up. Is there anything else we can help with?"

Five minutes. Done. Genuine warmth about it.

A man who was off the clock, walking home after his shift, stopped to check on a customer he had met once that morning. That is not something you can train in a day. That comes from somewhere deeper in how an organization treats its people and what it signals about what matters.

What This Means for Revenue Leaders

I want to be clear: I'm not writing this to pile on Verizon or to give T-Mobile a trophy. I am certain there are stories out there with a similar arc, but the company names are reversed.

I'm writing this because I work with B2B sales and revenue teams on CRM adoption, process design, and the human layer that makes or breaks both. And this experience was a live demonstration of every single thing I talk about with clients.

The technology at Verizon wasn't the problem. They almost certainly have a sophisticated CRM, ticketing system, and authentication infrastructure. The workaround that eventually solved our problem was built into their system. Someone designed it. It was there.

The process wasn't entirely the problem either. Processes exist for good reasons. You can't have every associate making judgment calls on security and account access without guardrails.

What failed was the intersection of process, people, and culture. And that intersection is where revenue is won and lost every single day.

A few questions worth sitting with if you lead a customer-facing or revenue team:

1. Do your people own outcomes, or just tasks? There is a massive difference between someone who executes a process and someone who takes responsibility for the result. One of them stops when they hit the edge of the defined flow. The other keeps going.

2. When your team encounters a situation that doesn't fit the script, what do they do? Do they look for a path through, or do they hand it back to the customer and move on?

3.Are your people empowered to escalate? Not just permitted, but actually empowered. Is escalating a broken process or an unusual situation seen as part of the job, or as something that creates risk for the person doing it?

4. Are broken processes actually getting flagged and fixed? If your team encounters a gap and quietly moves on, that gap will cost you again. And again. You need a mechanism and a culture that treats identifying process failures as a contribution, not a complaint.

5. Could a customer without a patient, knowledgeable advocate navigate your systems alone? My mother-in-law is 76, hard of hearing, and doesn't understand why any of this is as complicated as it is. Without someone in her corner who understood the landscape and refused to give up, she would have been lost. She would have been crying. That is not a customer problem. That is an organizational design and execution problem.

6. What signals are you sending your people about what matters? John stopped on a sidewalk after his shift because somewhere along the way T-Mobile created an environment where that felt natural. Kevin communicated through his every interaction that customer outcomes were not his responsibility. Both of those behaviors were shaped by their organizations, whether intentionally or not.

One More Thing for Anyone Who Sells Both B2B and B2C

I want to name something that often gets missed in conversations about customer experience.

This is a consumer story. But Verizon, T-Mobile, and every company like them (banks, insurance companies, property management firms, real estate companies, etc.) that sell to both individuals and businesses need to understand that the line between those two worlds is thinner than most revenue leaders assume.

The person standing in a Verizon store trying to sort out a phone problem could easily be the VP of Operations at a mid-size company that's about to go out for bids on a new corporate mobile contract. The experience they have as a consumer absolutely colors the recommendation they make in a boardroom. I know mine did.

And it goes the other way too. You never know who the customer in front of you today is in their professional life. The woman who couldn't navigate your 2FA process might have a son-in-law who consults with companies on technology adoption, customer experience, and revenue generation. He might write about it. He might tell people.

If your consumer and business customer experiences are siloed - meaning different teams, different standards, different cultures - you have a real problem. A bad consumer experience is a B2B risk. Revenue leaders at companies that touch both markets need to own both, not just the side that shows up in their quarterly targets.

The Bottom Line

Verizon didn't lose my mother-in-law as a customer because of bad technology. They didn't lose her because of pricing. They lost her because when a situation arose that didn't fit neatly into their defined process, nobody in their organization felt responsible for making it right. And nobody flagged it afterward so it could be prevented next time.

That's not a training issue. That's a culture and organizational issue. And culture, whether you frame it that way or not, is a revenue issue.

The good news: this is fixable. The organizations that figure out how to build people who own outcomes rather than just tasks, who create safe pathways for escalation and process improvement, and who make customers feel like someone actually gives a damn, well, those organizations grow. The ones that don't keep cycling through the same broken loops, losing customers quietly, one unresolved edge case at a time.

T-Mobile won a customer that day. Not because their technology was better. Because their people were better. And their people were better because someone, somewhere in that organization, decided that was what mattered.

Jason Whitehead works with B2B sales and revenue teams on CRM adoption, AI adoption, and process design, with a focus on the human layer that makes technology investments actually pay off. Connect with him on LinkedIn or learn more at jasonwhitehead.me.