Customer Service Role-Play: A Practical Coaching Session
The Happy Customer Channel ·
A customer service role-play works best when the team practices one difficult decision, observes what the employee actually does, and tries the conversation again after feedback. Rehearsing a perfect script can miss the judgment required when a customer’s situation changes.
In Alvaro D’Amico and Peter Muir — customer care, Peter Muir introduces LAURA, and Alvaro D’Amico discusses listening, human communication, and taking ownership of the customer’s problem. The practical tool below is THCC’s editorial application of that discussion; it is not a checklist the guest delivered word for word.
Choose a realistic decision, not an exaggerated argument
Start with a situation the team encounters: a missed update, an unavailable request, or a customer who has already explained the problem to someone else. State what the employee knows, what remains uncertain, and which actions are permitted. Do not use identifiable customer records as practice material.
Keep the first exercise narrow. A fictional customer can be frustrated about an unexplained delay without becoming abusive. The learning objective might be to uncover the practical impact and agree on a reliable next update.
Use this practice scenario
A customer was promised an update yesterday and received none. They need to know whether a service visit will happen before they leave town. The agent can check the current schedule and arrange a supervisor review, but cannot promise an unconfirmed appointment.
One colleague plays the customer, another the agent, and a third observes. Give the customer a genuine constraint to reveal when asked. That encourages discovery rather than a performance in which everyone already knows the answer.
Observe behaviors you can discuss
Did the agent allow the customer to explain the situation?
Did they acknowledge the missed commitment specifically?
Did they check what the delay means for the customer?
Did they distinguish a confirmed fact from a proposed next step?
Did they take responsibility for an update without promising unavailable service?
Use the framework as a coaching aid. The employee does not need to recite its letters or use a prescribed emotional phrase. An observer should be able to point to the moment the agent understood the issue and the action that followed.
Debrief, then repeat the difficult moment
Ask the agent what they understood, the customer what remained unclear, and the observer which behavior helped. Select one change for the second attempt. Repeating that moment gives the employee a chance to apply the feedback immediately.
If the exercise exposes an unclear approval rule or unavailable information, record an operating action for the supervisor. Training should not be used to compensate indefinitely for a process employees cannot execute.
Should a role-play be scored?
A short behavior checklist can make feedback consistent. Use it to identify a next practice step, and keep the discussion specific. A total score alone tells an employee little about what to change in the next customer conversation.
EP. 119 — Chad Van Horn | The Debt Trap, Fresh Starts, and Life Inside Squid Game
Bankruptcy attorney and Squid Game: The Challenge contestant Chad Van Horn joins Dan Arriola for a conversation about financial pressure, the people behind a difficult first call, and the experience of competing as player 286. The episode moves between his work with clients, building a law firm, and returning to everyday life after the show.
A customer experience theme connects those different settings: what happens when someone feels overwhelmed and cannot see the next step? Chad describes hearing the story behind a client’s situation before explaining the path ahead. His account gives leaders a concrete starting point for thinking about listening, clarity, and the way a service is experienced.
Questions about Chad Van Horn and Episode 119
Who is Chad Van Horn?
Chad Van Horn is the bankruptcy attorney who joins Dan in this interview. He is also player 286 from Squid Game: The Challenge. The discussion covers his work with clients, marketing a law firm, his time on the show, and his connections to sports podcasting.
What does he say about a financial fresh start?
At 01:15, Chad challenges the idea that bankruptcy necessarily represents the end of someone’s story. He describes the pressure people can be under by the time they contact his team. Watch his explanation in the full interview for its original context; this article focuses on the conversation and its customer experience implications.
Which part should customer experience teams watch first?
Start at 16:07, when Dan asks about a caller who cannot see a way forward. Chad talks about hearing what happened, learning about the person’s family, and explaining what comes next. The Squid Game discussion starts at 21:13, and his account of returning to everyday life begins at 26:08.
Editorial note: The customer experience frameworks and team exercises below are The Happy Customer Channel’s interpretation of the interview. They are not quotations from Chad or a method he presents as a named framework.
What This Episode Covers
Chad’s perspective on financial setbacks and fresh starts
The debt pressure discussed around credit cards, buy now/pay later, and sports betting
Listening to the person behind a difficult customer conversation
Building a law firm through digital marketing
Applying for Squid Game: The Challenge and competing as player 286
Relationships inside the game and the transition back to normal life
The challenge of keeping his experience confidential after returning home
Key Insights
The first conversation can change how someone sees the problem
Chad opens the interview by describing people who arrive after trying multiple ways to manage a financial problem. In his account, they may feel exhausted and believe their options have narrowed. He explains why he sees his team’s work as helping people understand that another chapter may be possible.
For a service team, our interpretation is that the customer’s understanding of the situation matters alongside the process itself. An explanation can be technically detailed while still leaving the person unsure about what to do. The first useful question is whether the conversation makes the situation easier to understand.
Listen for the situation behind the request
At 16:07, Dan asks what happens when a caller is in a difficult headspace. Chad describes conversations in which people open up about what happened and discuss their families. The exchange gives attention to the person making the call, not only the service they are asking about.
A practical application for customer experience teams is to leave room for that context. A customer may begin with a short request while the concern behind it is more complicated. Listening can help the team understand which explanation is useful and which question still needs to be answered.
Clarity is part of the service
Chad’s description moves from hearing someone’s story to explaining a path ahead. That sequence is useful to examine in other service environments: understand the concern, then make the next step understandable.
Our takeaway is to review the handoff between explanation and action. Does the customer know what happens after the call? Is it clear who will follow up? Can the customer describe the action they need to take? Those are editorial prompts for applying this part of the discussion, not promises about the outcome of any particular case.
A familiar public identity can lead to a more personal conversation
The interview introduces Chad as both an attorney and a reality-show contestant. At 21:13, he explains how he became involved in Squid Game: The Challenge, including the initial application and the casting response. He also discusses relationships formed during the experience.
The episode gives viewers more context than a player number alone. For brands and leaders, the useful storytelling lesson is to make room for the person behind a recognizable role. A title or public appearance can start someone’s interest; the conversation can help them understand the person’s experience in more depth.
The transition back deserves attention too
At 26:08, Chad describes returning from the show and finding the flow of normal information difficult to take in. He talks about slowing down and about the support provided to participants. Later, at 37:59, he describes keeping the experience confidential for months.
Our leadership application is to think about what follows an intense period of work. A major event or demanding project may end on the calendar while the person is still adjusting. The interview offers a reason to ask what support, pace, and communication are useful during that transition.
Framework
Listen, Explain, Confirm
This is our simple way to apply the customer experience discussion to a team conversation:
Listen: identify the concern the person is trying to resolve, including context that changes how you should respond.
Explain: describe the next step in terms the customer can understand, including who does what.
Confirm: ask a useful follow-up question to check whether the person understands what happens next.
Review one recent customer call against those three steps. Look for a specific moment where the explanation reduced uncertainty, or where another question would have helped. The point is to make the exercise concrete enough to improve a real interaction.
Review the First Conversation, Not Just the Completed Transaction
A team may know whether a request was processed without knowing how the customer experienced the explanation. Our suggested review is to examine both. Choose one completed interaction and identify the original concern, the explanation given, and the next step communicated. If one part is unclear, use it as a coaching opportunity.
Key Takeaways
The first conversation can influence whether someone sees a path ahead.
Listening helps reveal context that a short service request may leave out.
A clear next step is a useful part of the customer experience.
A public identity can be the starting point for a more personal story.
The period after an intense experience deserves attention as well.
Team exercises should stay connected to actual interactions and specific improvements.
Who This Is For
This episode is especially relevant for:
Customer experience leaders reviewing difficult first conversations
Service teams helping people navigate unfamiliar processes
Founders thinking about the people behind their brand
Managers considering the transition after demanding projects
Viewers interested in Chad’s experience on Squid Game: The Challenge
Watch the Full Episode
Watch the player at the top of this page for Chad Van Horn’s full conversation with Dan Arriola. Episode 119 covers the debt trap, his approach to client conversations, life as player 286, and returning home after Squid Game: The Challenge.
FAQ
What is the main customer experience lesson?
Our main takeaway is to connect listening with a clear explanation of the next step. Chad’s account at 16:07 gives a concrete example of hearing someone’s situation before discussing the path ahead.
Does the episode cover Chad’s time on Squid Game?
Yes. The discussion begins at 21:13 and includes applying for the show, his experience as player 286, relationships formed there, and the transition back to everyday life.
How can a team apply the discussion?
Use the editorial Listen, Explain, Confirm exercise above to review one recent interaction. Check whether the team understood the customer’s concern and whether the customer was given an understandable next step.
Are you letting analytics dictate your customer journey, or real-world decisions? Every wasted step is a wasted dollar—and customers don’t forgive wasted time. Too many brands are optimizing customer journey maps for optics, not for what moves the needle. The result? Friction, wasted investment, and another lost customer. Today, we’re talking about optimizing customer journey with ruthless focus on real decisions. This isn’t theory. It’s the hard reality of retention, growth, and trust.
Stop Optimizing for the Wrong Things
Let’s cut to the chase. You’re not in business to produce the prettiest journey map in the room. You’re in business to keep customers, drive growth, and, above all, earn trust. But here’s where most customer experience teams go sideways—they obsess over vanity metrics, surface-level touchpoints, and perfect flows. I’ve seen it a hundred times. Busywork gets rewarded. Real results? Not so much.
Sound familiar? Maybe you’re tracking NPS as your North Star. Or stuck fine-tuning checkout screens that don’t even matter to your churn problem. Meanwhile, the real decision moments—where customers actually choose to stay, upgrade, or leave—get glossed over. That’s what ruins retention faster than any website bug.
If you optimize for what looks good, not what matters, you will fail. It’s a common trap, and it’s usually caused by a lack of operational standards. Want proof? Go deeper into why most journey mapping fails in real-world CX: CX Strategy Fails Without Operating Standards.
Use the 3D Framework for Real-World Journey Optimization
Here’s the fix. You need a framework built on what really counts—the moments where decisions get made. I call it the “3D” approach. It’s simple. It’s brutal. It works.
Discover: Start by pinpointing the actual decision moments. Where do customers choose: to buy, renew, refer you, or escalate a complaint? If you’re not clear on this, you’re already losing. Look at real data: churn events, escalations, upsell misses, renewal dips. Talk to frontline staff. Dig into customer conversations. Forget about endless touchpoint mapping that doesn’t translate to a binary decision.
Diagnose: Now dive deep. For each decision moment, ask: “What forces drive the choice?” Is it complicated onboarding? Unclear pricing? Support friction? Don’t guess. Use lost customer interviews, survey dropoffs, call logs. Find what’s really influencing action or inaction.
Design: Only now do you rebuild. Focus every process, bit of technology, and internal script directly on optimizing those exact decision points. Cut the fluff. If most churn happens during onboarding, put 90% of your firepower there. If renewals dip at pricing time, overhaul that moment first. And don’t just watch overall journey satisfaction—measure conversion, churn, speed at each critical choice.
Here’s the key: optimizing customer journey isn’t about adding more. Sometimes “less” is the move. Strip away distractions. Keep customers locked into what matters. Real journey optimization means saying “no” to wasted steps and “yes” to decisions that fuel your bottom line.
Leadership Discipline and Trust: The Real Outcome
When leaders get disciplined about optimizing customer journey around real decisions, everybody wins. Customers notice. They feel heard, not handled. Trust grows, and loyalty follows. But this takes focus. Most operators throw budget and bodies at every minor feedback blip, then wonder why nothing sticks. The reality? Customers reward ruthless prioritization—and spot when you’re just checking boxes.
Want higher retention, more referrals, and a business that outlasts the fads? Make optimization a daily leadership discipline. Lead teams to confront every assumption. Measure what actually moves the customer to act. And cut the rest.
This is what we live for at The Happy Customer Channel. Operator-level CX. No fluff. No buzzwords. Only what delivers real business results and repeat loyalty.
Final Thoughts
Optimizing customer journey is not an annual project. It’s not about the tech stack or the prettiest chart. It’s a relentless discipline. Get clear on what decisions matter. Build around them. Customers will see it, feel it, and reward you. Don’t coast. Don’t compromise. Focus on real decisions or fall behind—those are your choices.
Want more real-world CX strategies that cut through the noise? Subscribe to our newsletter for weekly, no-fluff guidance direct to your inbox.
Common Questions
How do I identify the “real decisions” that shape my customer journey?
Listen—don’t waste time with guesswork or copying someone else’s map. Start by digging into your churn data, your complaint logs, and every point where customers drop or escalate. Look for the moments they hit pause or call you out. Get input from your frontline people; they see the real story. Forget mapping every click—go after the big decisions. If a stage doesn’t change the customer’s fate, you can safely ignore it.
Does optimizing the customer journey always mean adding more touchpoints or technology?
Here’s the reality: More isn’t better. I’ve watched companies burn millions layering on tech and channels that just muddy the experience. Sometimes, optimizing means cutting out the clutter—removing friction, not adding features. Double down where customers actually struggle to decide, and ruthlessly trim the rest. Less noise, more signal. Simple wins.
How do I measure the impact of customer journey changes?
Don’t hide behind vanity metrics. At the end of the day, you need to tie every change back to a hard outcome—conversion, reduced churn at a specific step, or a faster resolution on escalations. NPS is fine, but it won’t save your renewal numbers if you’re ignoring actual behaviors. Measure the before and after at decision points, not just overall satisfaction. That’s how operators prove ROI.
What if my team disagrees on what the “real decision moments” are?
Get everyone in a room—seriously. Bring support, sales, ops, the actual frontline. Lay out the data. Don’t settle for opinions. What I’ve seen work best is mapping customer pain, then testing your hypotheses. Validate with customer calls and lost deal reviews. When people see undeniable data, the debate cools fast. Cross-functional buy-in wins every time.
