Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / Why Journey Maps Miss the Voice of Customer Unstructured Feedback
Transcript
- Lucas: We talk a lot on this show about touchpoints that journey maps miss. But there's one category of hidden signal that's less about a specific moment and more about the texture of what customers are actually saying across every moment. Luna: You're talking about unstructured feedback—the open-ended comments, the support call transcripts, the social media posts that don't fit into a multiple-choice box. Lucas: Exactly. Most companies run their Net Promoter Score surveys, they track CSAT, they look at their customer effort score. All structured, all numerical, all easy to plug into a dashboard. But the journey map built on that data is missing the full story. Luna: Because the best insight often lives in a sentence a customer typed when they were frustrated, not in the four-star rating they gave. Lucas: Right. And the problem is scale. A mid-size retailer might get two thousand open-ended survey responses a month, plus thousands of support tickets and social mentions. Nobody's reading all of that. So the unstructured feedback stays in a spreadsheet, unanalyzed, while the journey map gets built from averages. Luna: So what does the structured-only map actually miss? Give me a concrete example. Lucas: Let's talk about a company I'll call Outdoor Supply Co.—a regional retailer selling camping and hiking gear. They had a standard journey map: awareness, browse, product page, add to cart, checkout, post-purchase. Their conversion rate was okay, but they couldn't figure out why they were losing people at the product page. Luna: So they looked at their structured data—page views, time on page, bounce rate—and nothing jumped out? Lucas: Exactly. The analytics said customers were spending three minutes on product pages, scrolling, looking at images. Average time. Nothing alarming. But then they ran a natural language processing analysis on the open-ended survey comments and the live-chat transcripts for people who visited a product page but didn't buy. Luna: And what did the NLP surface? Lucas: A specific phrase pattern: 'not sure which is better.' Customers were comparing two similar items—say, two different sleeping bags—and leaving because they couldn't decide. The structured data showed a product page exit. The unstructured data revealed the reason: a missing comparison tool. Luna: So the journey map had a gap at the product page that looked like a dead end, but the real problem was a missing micro-touchpoint: the comparison view. Lucas: Precisely. Outdoor Supply Co. added a side-by-side comparison feature on their top thirty most-compared product pairs. They also trained their chat agents to proactively offer comparisons when a customer asked about two items. The result: conversion on those product pages went up eight percent. Luna: Eight percent from one phrase pattern. That's the power of unstructured data. Lucas: And here's the thing—that insight was invisible in the NPS score. Their NPS was a 42, which is solid. But the comments underneath included phrases like 'wish I could compare tents side by side.' If they'd only looked at the number, they'd have never known. Luna: So the rule of thumb should be: if your journey map is built only on structured data, you're flying blind on the 'why' behind customer behavior. Lucas: Yes. And the good news is the tools to surface this have gotten much cheaper. Open-source NLP libraries, or even simple keyword clustering in a spreadsheet, can reveal the top five complaint themes in a few hours. Luna: But there has to be a barrier, otherwise every company would be doing this. What stops them? Lucas: Noise, mostly. Open-ended text is messy. People write in fragments, use slang, misspell words. You get a lot of 'it was fine'—which is a non-signal. So teams get overwhelmed and retreat to the clean numbers. Luna: Also, there's the organizational silo problem. The person building the journey map is often in product or marketing, while the unstructured feedback lives in customer support or the survey platform. They don't talk. Lucas: That's a huge one. The journey map is only as good as the inputs, and if the inputs are siloed, the map is incomplete. I'd argue that every journey mapping session should start with a read-through of fifty recent open-ended comments, just to calibrate the team's assumptions. Luna: It's like going to the source before drawing the diagram. I love that. Lucas: Honestly, if today's episode helped you think differently about how you build your journey maps, that's the link—buy me a coffee dot com slash fexingo. That's where listener support keeps this show ad-free and independent. Luna: Yeah, and if you've ever caught yourself saying 'why don't we just look at the survey comments more carefully' after one of our episodes, that's exactly the kind of moment that pays for the coffee. Lucas: Exactly. No pressure, just know that it helps. Back to the topic—one more example I think is worth unpacking. There's a SaaS company that used unstructured support tickets to find a journey map gap in their onboarding flow. Luna: What did they find? Lucas: Their structured data showed a seven-day activation rate of sixty percent—not great, but not alarming. But when they ran sentiment analysis on support chats from users who didn't activate, the dominant emotion was confusion, specifically around one feature: the data import wizard. Luna: So the journey map had 'import data' as a single step, but the unstructured feedback revealed it was actually a multi-step failure point. Lucas: Right. They redesigned the import wizard, added contextual tooltips, and the activation rate climbed to seventy-three percent in two months. Again, the journey map on its own couldn't have told them what was broken. It just showed a drop-off. Luna: That's the real value of unstructured data: it turns a red arrow on the map into a specific fix. Lucas: Exactly. And we should be clear—this isn't about replacing quantitative data with qualitative. It's about layering them. The structured data tells you where. The unstructured data tells you why. You need both to build a journey map that actually drives action. Luna: So for someone listening who wants to start today, what's the smallest practical step? Lucas: Export your last month of post-interaction survey comments. Not the ratings—just the open-ended box. Copy them into a spreadsheet, sort by length, and read the fifty longest comments. You'll spot patterns in under an hour. That's the minimum viable unstructured analysis. Luna: And if you have more resources, you can move to keyword clustering or NLP. But the barrier to entry is basically zero. Lucas: Zero. And the ROI from catching one missed touchpoint like the comparison gap can easily justify the time. Outdoor Supply Co.'s eight percent lift on that page alone was worth tens of thousands of dollars. Luna: Alright, so the challenge for listeners this week: pull the unstructured feedback, find one pattern, and see if your journey map needs an update. Lucas: That's a great homework assignment. I'll be doing the same on my side. Thanks, Luna.