<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[Customer XO]]></title><description><![CDATA[A community for customer-obsessed brand leaders.]]></description><link>https://www.customerxo.com</link><image><url>https://substackcdn.com/image/fetch/$s_!EyA1!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc7120278-2917-48b7-9a9b-0971820154fc_301x301.png</url><title>Customer XO</title><link>https://www.customerxo.com</link></image><generator>Substack</generator><lastBuildDate>Fri, 10 Apr 2026 01:11:40 GMT</lastBuildDate><atom:link href="https://www.customerxo.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Jaime Lee]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[customerxo@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[customerxo@substack.com]]></itunes:email><itunes:name><![CDATA[Customer XO]]></itunes:name></itunes:owner><itunes:author><![CDATA[Customer XO]]></itunes:author><googleplay:owner><![CDATA[customerxo@substack.com]]></googleplay:owner><googleplay:email><![CDATA[customerxo@substack.com]]></googleplay:email><googleplay:author><![CDATA[Customer XO]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[When Customers Start Gamifying Your Policies]]></title><description><![CDATA[What Taylor Johnson taught us about the new face of fraud &#8212; and why the biggest risks for modern brands now show up in returns, refunds, and customer support, not just at checkout.]]></description><link>https://www.customerxo.com/p/when-customers-start-gamifying-your</link><guid isPermaLink="false">https://www.customerxo.com/p/when-customers-start-gamifying-your</guid><dc:creator><![CDATA[Customer XO]]></dc:creator><pubDate>Fri, 20 Mar 2026 14:34:00 GMT</pubDate><enclosure url="https://substackcdn.com/image/youtube/w_728,c_limit/yJ_M7PAxvRY" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><strong>Customer XO exists for customer-obsessed brand leaders.<br></strong><br>Not to add more noise. Not to turn merchant stories into marketing. But to elevate the voices of the people actually in it every day. The operators, CX leaders, and teams who see how customer experience really works when it&#8217;s under pressure.</p><p>Because the truth is, some of the most important conversations in commerce are happening inside support queues, warehouse escalations, return workflows, and those &#8220;something feels off here&#8221; Slack threads.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.customerxo.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>That&#8217;s what this show is for.<br>Merchants learning from merchants.<br>Real stories, real tradeoffs, real pattern recognition.</p><p>And in this episode, Taylor Johnson brings exactly that.</p><p>Taylor, a CX leader at Nathan James, walks through what a lot of brands are quietly living through right now: fraud doesn&#8217;t always show up looking dramatic. More often, it looks like a normal customer, a friendly policy, a believable claim, and a team trying to do right by people at scale.</p><p>That&#8217;s what makes it so hard to catch. And that&#8217;s what made this conversation so good.</p><div id="youtube2-yJ_M7PAxvRY" class="youtube-wrap" data-attrs="{&quot;videoId&quot;:&quot;yJ_M7PAxvRY&quot;,&quot;startTime&quot;:null,&quot;endTime&quot;:null}" data-component-name="Youtube2ToDOM"><div class="youtube-inner"><iframe src="https://www.youtube-nocookie.com/embed/yJ_M7PAxvRY?rel=0&amp;autoplay=0&amp;showinfo=0&amp;enablejsapi=0" frameborder="0" loading="lazy" gesture="media" allow="autoplay; fullscreen" allowautoplay="true" allowfullscreen="true" width="728" height="409"></iframe></div></div><h2>Fraud doesn&#8217;t always start at checkout anymore</h2><p>One of the clearest themes from Taylor&#8217;s stories is that the old mental model of fraud is outdated.</p><p>It&#8217;s easy to picture stolen cards, suspicious orders, or obvious red flags at checkout. But Taylor&#8217;s experience points somewhere else: the real mess often starts <em>after</em> the purchase, inside the customer journey itself.</p><p>A return gets refunded too early.<br>A replacement gets approved off a fake invoice.<br>A support agent sees a damaged-product photo that looks legit &#8212; until someone realizes they&#8217;ve seen it before.</p><p>These aren&#8217;t edge cases in some abstract risk model. These are operational realities. And they land squarely on CX teams.</p><p>As Taylor put it, friendly policies are exactly where brands have to be careful, because that&#8217;s where they get exploited.</p><p>That tension sits at the heart of modern CX leadership: how do you make things easy for good customers <strong>without creating a roadmap for bad actors</strong>?</p><h2>The triangulation fraud story that says it all</h2><p>Taylor shared one of the wildest cases from earlier in her career: a triangulation fraud scheme involving a high-value supplement product.</p><p>The setup was deceptively simple. A fraudster listed the product on a third-party marketplace at a discount. A real customer bought it, thinking they found a deal. Then the fraudster took that money, went to the brand&#8217;s site, bought the product with a stolen credit card, and shipped it directly to the legitimate customer.</p><p>Three parties. One order. Total chaos.</p><p>The customer who received the item was happy.<br>The actual cardholder was confused and angry.<br>And the brand was left trying to untangle a transaction that didn&#8217;t make sense from any one angle.</p><p>That&#8217;s the part Taylor captures so well: fraud like this hides in the gaps between systems. The product gets fulfilled. The end customer got what they expected. The chargeback comes from someone whose name and address don&#8217;t match the shipped order. Support is trying to help, but the data doesn&#8217;t line up.</p><p>Her description of the investigation felt familiar to anyone who&#8217;s ever had to chase a fraud pattern across siloed teams and incomplete information. Weeks, maybe months, of back-and-forth before the pattern finally surfaced.</p><p>And the cost wasn&#8217;t just financial. It was time, logistics, support energy, and operational distraction. The kind of cost that rarely shows up neatly in a dashboard, but every operator feels.</p><h2>The empty box problem is really a policy problem</h2><p>One of Taylor&#8217;s best examples came from Nathan James and it perfectly illustrates how modern fraud can look almost boring on the surface.</p><p>Nathan James had a customer-friendly return workflow: once a return shipment showed its first in-transit scan, the refund was issued. For legitimate customers, that&#8217;s a great experience. Fast, easy, trust-building.</p><p>Until the warehouse reached out and said: we received two empty boxes.</p><p>The customer had returned &#8220;bookcases&#8221; that weren&#8217;t bookcases at all &#8212; just empty packages. But because the refund was triggered by the scan, the money was already gone.</p><p>What makes this story resonate is that Taylor doesn&#8217;t frame it as a failure of customer care. She frames it as the exact challenge brands face when they build with good intentions. The friendliest experiences are often the ones most vulnerable to abuse if they aren&#8217;t paired with the right guardrails.</p><p>That is such an important CX lesson.</p><p>Most merchants are not struggling because they don&#8217;t care about customers. They&#8217;re struggling because they <em>do</em> care, and bad actors know how to weaponize that.</p><h2>Documentation fraud is getting easier to fake &#8212; and harder to spot</h2><p>Another story Taylor shared will sound painfully familiar to marketplace brands.</p><p>Customers would claim they bought a Nathan James product on Amazon and that it arrived damaged. They&#8217;d send over what looked like proof of purchase and photos of the issue. A replacement would go out.</p><p>Except sometimes the Amazon invoice was fake. And the damage photo had been pulled from someone else&#8217;s review.</p><p>The detail that makes Taylor&#8217;s telling so strong is how human the detection process was. This wasn&#8217;t some dramatic moment powered by a perfect system. It was an agent noticing that the spacing on an invoice looked a little off. A font felt wrong. Something didn&#8217;t match the dozens of real invoices they&#8217;d seen before.</p><p>That instinct matters.</p><p>In a world increasingly full of AI-generated content, edited photos, fake documents, and polished impersonation, so much still comes down to the pattern recognition of frontline teams. The people doing the work every day are often the first ones to spot when something is templated, repeated, or just subtly wrong.</p><p>Taylor&#8217;s story is a reminder that great CX teams aren&#8217;t just service teams. They&#8217;re intelligence teams.</p><h2>Serial policy abusers thrive when teams can&#8217;t see the full picture</h2><p>One of the most practical parts of the episode is Taylor&#8217;s point about policy abusers.</p><p>Sometimes it&#8217;s not a sophisticated fraud ring. Sometimes it&#8217;s just a customer who learns that a brand is generous, responsive, and low-friction &#8212; and decides to keep pushing.</p><p>A claim gets resolved easily once, so they come back with another. Then another. Sometimes with the same image. Sometimes with a slightly different story. On a large support team, those interactions may land with different agents each time, which makes abuse much harder to detect in the moment.</p><p>Taylor&#8217;s takeaway here is simple and sharp: teams need a consolidated view of customer history.</p><p>That sounds obvious, but in practice it&#8217;s still a huge operational gap for a lot of brands. If agents can&#8217;t quickly see prior refunds, prior exceptions, prior claims, and prior supporting evidence, then every new ticket gets treated like a standalone situation. And that&#8217;s exactly the environment where repeat abuse flourishes.</p><p>This is where CX leadership gets really strategic. It&#8217;s no longer just about coaching tone or speed. It&#8217;s about helping teams make better decisions with better context.</p><h2>Taylor&#8217;s perspective feels so grounded because it is</h2><p>What makes Taylor such a compelling guest is that she doesn&#8217;t talk about fraud as a theory. She talks about it as an operator.</p><p>You can hear it in the way she describes the tradeoffs. Nathan James offers a 100-day return window and covers return shipping. That&#8217;s not accidental. It reflects a genuine belief in taking care of customers.</p><p>But she&#8217;s equally honest that brands have to keep an eye on the people trying to take advantage of those policies. Not with paranoia. With clarity.</p><p>That balance is what good merchants understand better than anyone else. Most brands don&#8217;t want to become suspicious, rigid, or punitive. They want to stay generous without being naive. They want to trust customers without turning trust into an open loophole.</p><p>Taylor&#8217;s stories live right in that middle ground, which is why they feel so useful.</p><h2>The big takeaway: post-purchase is where the real complexity lives now</h2><p>If there&#8217;s one idea that hangs over the entire episode, it&#8217;s this: post-purchase fraud and abuse is becoming the more difficult problem.</p><p>Traditional payment fraud has become more manageable for many brands. But returns abuse, refund manipulation, fake damage claims, invoice fraud, and policy exploitation are much murkier. They&#8217;re subjective. They&#8217;re operational. They require context. And they usually hit the teams already carrying the emotional and logistical weight of the customer relationship.</p><p>That&#8217;s why Customer XO matters.</p><p>Because these stories deserve more airtime.<br>Because the people closest to the customer often have the clearest read on where commerce is actually headed.<br>And because merchant wisdom &#8212; the real kind, earned through weird edge cases and hard calls &#8212; is still one of the most valuable resources in this industry.</p><p>Taylor brought that wisdom in full.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.customerxo.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Why Customer Support Is The New Fraud Battlefield]]></title><description><![CDATA[Customer fraud is evolving fast, and today&#8217;s most costly customer fraud often hides inside everyday support interactions.]]></description><link>https://www.customerxo.com/p/why-customer-support-is-the-new-fraud-d1e</link><guid isPermaLink="false">https://www.customerxo.com/p/why-customer-support-is-the-new-fraud-d1e</guid><dc:creator><![CDATA[Customer XO]]></dc:creator><pubDate>Fri, 20 Mar 2026 10:00:00 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/191582826/5ba0a194e365f4acb6171ec93c04f936.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>Customer fraud is evolving fast, and today&#8217;s most costly customer fraud often hides inside everyday support interactions. In this episode, Jordan and Alex Shamir sit down with Taylor Johnson, Director of CX at Nathan James, to unpack real customer fraud stories that reveal how brands are being exploited after the purchase. From triangulation fraud to fake Amazon invoices and return policy abuse, this conversation delivers practical insight into the customer fraud patterns every e-commerce and CX leader needs to understand.</p><p>Taylor shares firsthand experiences navigating complex fraud schemes that stretched across marketplaces, payment methods, and customer support workflows. Together, the group explores why modern customer fraud increasingly targets policies designed to delight customers, how operational blind spots create opportunity for abuse, and what brands can do to protect revenue without damaging customer experience. If you work in ecommerce, CX, risk, or operations, this episode offers a behind-the-scenes look at how fraud actually unfolds and what leading teams are doing to stay ahead.</p><p><strong>In this episode, you will learn:</strong></p><ul><li><p>How triangulation fraud works and why brands can become unintended fulfillment partners</p></li><li><p>The hidden risk behind refund-upon-scan return policies</p></li><li><p>How fake Amazon invoices and stolen product photos lead to replacement fraud</p></li><li><p>Why policy abuse is growing faster than traditional payment fraud</p></li><li><p>The operational and financial ripple effects of post-purchase fraud schemes</p></li><li><p>Signals CX teams can use to detect suspicious behavior earlier</p></li><li><p>How centralized customer history and tooling help prevent repeat abuse</p></li><li><p>Why customer support is becoming the frontline of fraud prevention</p></li></ul><p>Don&#8217;t risk letting friendly policies become costly vulnerabilities. Learn how to recognize modern customer fraud patterns and build defenses before they impact your business.</p>]]></content:encoded></item><item><title><![CDATA[The Show for Customer Experience Leaders]]></title><description><![CDATA[Ecommerce has made buying easier than ever, but it has also made customer expectations relentless.]]></description><link>https://www.customerxo.com/p/the-show-for-customer-experience-0e2</link><guid isPermaLink="false">https://www.customerxo.com/p/the-show-for-customer-experience-0e2</guid><dc:creator><![CDATA[Customer XO]]></dc:creator><pubDate>Fri, 06 Mar 2026 11:00:00 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/191582827/49c5e490594c4385185400532f9ead92.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>Ecommerce has made buying easier than ever, but it has also made customer expectations relentless. Teams are expected to protect revenue, prevent fraud, reduce refunds, manage returns, and still deliver a seamless experience that keeps customers coming back.</p><p>Customer XO confronts that pressure head-on.</p><p>Hosted by Jordan Shamir and Alex Shamir, each episode explores how customer experience and fraud strategy shape the financial health of modern ecommerce brands. Drawing from real operator experience, Jordan and Alex break down the shifts that protect margins, reduce unnecessary loss, and turn customer trust into long-term revenue.</p><p>This show is built for ecommerce operators, CX leaders, and digital executives who carry revenue responsibility and know that experience is directly tied to growth. Customer XO delivers the conversations, lessons, and hard-earned insights that help teams protect profit while building loyalty that lasts.</p>]]></content:encoded></item></channel></rss>