Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / Why Journey Maps Miss the In-Store QR Code Touchpoint
Transcript
- Lucas: So you walk into a coffee shop, order a latte, and you notice the receipt has a QR code that says 'tell us how we did.' Do you scan it? Luna: Honestly? Rarely. Unless I had a really good or really bad experience. Lucas: Right, and that's exactly the pattern most brands see. But here's the thing — that QR code is a touchpoint. It sits right at the intersection of physical and digital, and yet I've reviewed dozens of customer journey maps, and I can count on one hand the number that include it as a formal node. Luna: So journey maps are missing the QR code. Why does that matter? Lucas: Because it's one of the only places where you can directly measure the bridge between an in-person interaction and an online behaviour. When a customer scans a QR code, you know exactly which location, which product, and which moment drove them to act. That's gold for attribution. Luna: And yet it's invisible in most maps. What's a concrete example? Lucas: Let's talk about a fast-casual chain — let's call them Green Bowl, a fictionalised version of a real brand I consulted with. They have about 200 locations across the US. They were getting maybe 50 online survey responses a week, which is nothing when you're serving tens of thousands of customers daily. Luna: So they weren't hearing from most people. Classic blind spot. Lucas: Exactly. So they redesigned their takeout bag. On the side, they printed a QR code with the text 'Scan for a free cookie on your next visit.' That incentive changed everything. Within six weeks, they were getting over two thousand survey responses per week. Their Net Promoter Score jumped twelve points. Luna: Twelve points is huge. And the journey map they had at the time — did it include the bag? Lucas: Not initially. Their map ended at 'customer receives order.' That was it. The bag was just packaging. They hadn't considered that the bag itself is a communication channel, and that the QR code turns it into an interactive touchpoint. Luna: So the journey didn't end at handoff. It continued onto the kitchen counter at home. Lucas: Right. And that's the key insight. The QR code extends the journey into the customer's own environment. It's not a passive element. It's an invitation to continue the relationship. Luna: But not all QR codes are created equal. I've scanned codes that led to a page that wasn't mobile-optimized, or a broken link. That's a terrible experience. Lucas: That's exactly the risk. If the QR code leads to a dead end, you've just created a negative touchpoint instead of a positive one. That's why mapping it matters — so you can design for the full experience, not just the scan. Luna: Before we go further, I have to say — this kind of conversation is exactly why we keep this show ad-free. We don't want a sponsor telling us what examples to use or how long to make the episode. It's a choice we've made from day one. Lucas: Yeah, and it's not something we take for granted. Running a podcast without ad revenue means the show is supported entirely by listeners who find value in it. If you're one of those people and you want to help us keep it that way, there's a link — it's buy me a coffee dot com slash fexingo. Luna: And it genuinely makes a difference. Every contribution helps cover hosting costs and keeps us free to dig into topics like this one without any outside pressure. Now back to the QR code — Lucas, you mentioned link rot. What other pitfalls should journey mappers watch for? Lucas: A big one is not tracking the scan itself. Many brands put a QR code on a poster or a receipt, but they never set up a proper analytics tag. So they can't tell how many people scanned, at what time of day, or from which location. It's a data void. Luna: So the journey map should include a data node. Not just 'customer scans,' but 'customer triggers an event that we capture.' Lucas: Exactly. And another pitfall is the incentive mismatch. Green Bowl used a cookie — a low-cost, high-appeal reward. But I've seen hotels offer a $5 discount on a future stay for scanning a QR code in the room. That's too much friction — the customer has to remember the code, book again, and apply the discount. The conversion rate was under one percent. Luna: Compare that to a cookie you get right away. Instant gratification works. Lucas: Right. And that's a principle that should be baked into the journey map. Every QR code touchpoint should have a clear, immediate value proposition. If the customer can't see the benefit in two seconds, they won't scan. Luna: Are there industries where QR codes are more naturally integrated into the journey map? Lucas: Restaurants and retail are the obvious ones. But I'm seeing more in healthcare, too. A clinic I visited recently had a QR code on the check-in kiosk that let you fill out your intake forms on your phone instead of on a clipboard. That's a touchpoint that reduces friction and improves data accuracy. Luna: Did their journey map include that? Probably not if they're like most organizations. Lucas: I asked the office manager. She said, 'We just put the code there because the vendor suggested it.' No one had mapped the patient journey to see where it fit. They were missing the chance to measure how many patients used it, how long it saved them, and whether it affected satisfaction scores. Luna: So it's not just about adding the QR code. It's about positioning it at the right stage of the journey and connecting it to a metric. Lucas: Bingo. And that's where the journey map becomes a strategic tool instead of just a poster on the wall. If you map the QR code as a formal node, you're forced to ask: what happens before the scan? What happens during? What happens after? And how do we measure each step? Luna: Let's talk about the 'after' for a second. Once someone scans, what should the experience be? Lucas: Ideally, it's a seamless extension of the brand. If it's a survey, it should be short — three questions max. If it's a loyalty sign-up, pre-fill whatever you can from the scan data. And always, always thank them and deliver the reward immediately. Luna: So the journey map should have a branch: 'scanned' leads to one path, 'did not scan' leads to another. And you can optimize both. Lucas: Exactly. And for the non-scanners, you might add a second touchpoint later — like an email reminder if you have their address, or a text message with the same offer. But that requires capturing their contact info, which is another design challenge. Luna: Capture contact info from a QR code scan — that's a privacy conversation. How do you handle that without creeping people out? Lucas: You have to be transparent. 'Scan to get a free cookie — we'll ask for your email so we can send you a reminder.' That's a fair trade. But if you just grab their data without explaining why, you'll erode trust fast. Luna: And trust is hard to rebuild once it's broken. So the journey map should include a trust checkpoint, too. Lucas: I like that framing. Actually, I think every journey map that includes a QR code should have a 'privacy note' node — a moment where the brand communicates what data is being collected and why. It doesn't have to be long. A single line on the landing page works. Luna: Okay, so we've covered the missing touchpoint, the incentive design, the analytics, and the privacy aspect. What's the one takeaway you want listeners to remember? Lucas: Next time you build or revise a customer journey map, walk through the physical handoff points — the bag, the receipt, the table tent, the product packaging — and ask: is there a QR code here? If not, should there be? And if there is, is it mapped as a full node with before, during, and after stages? Because that tiny square might be the most actionable touchpoint you're ignoring. Luna: Good way to put it. I know I'll be rethinking my own maps after this.