Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / Why Journey Maps Miss the In-App Feedback Prompt
Transcript
- Lucas: You know that pop-up that asks you to rate your experience right after you just tried to find a product? That's the in-app feedback prompt, and most journey maps completely ignore it. But it's actually a goldmine for understanding emotional state. Luna: Wait, do you mean the ones that appear right when you're in the middle of something? Because I usually just swipe them away. Lucas: Exactly. They feel like an interruption, but that's exactly why they matter. The way a user responds in that moment tells you something about friction, delight, or indifference. The problem is, most teams map the 'happy path' and skip these ambient feedback loops. Luna: But aren't they just measuring user annoyance? I mean, who gives a five-star rating after a buffering video? Lucas: That's the thing—they shouldn't be asking after a buffering video. A streaming service I worked with saw a 40 percent drop in feedback quality when they prompted users after a buffering incident versus after a completed watch. The timing is everything. Luna: So the prompt itself isn't the problem, it's where you place it in the journey. That makes sense. But if we're mapping the journey, why don't we ever see this touchpoint on the map? Lucas: Two reasons. First, it's often owned by the product team, not marketing or CX. It sits in a silo. Second, mapmakers think of it as a measurement tool, not an experience touchpoint. But for the user, that pop-up is part of their interaction with your brand. Luna: Speaking of value, this episode has already reshaped how I think about those little pop-ups. If it did the same for you, and you want to keep these conversations ad-free, you know where to find us. Lucas: Honestly, if today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. Every bit helps us stay independent. Luna: Yeah. Now back to that streaming service — what did they do differently after they figured out the timing issue? Lucas: They moved the prompt to appear after a user had watched at least 80 percent of a video or completed a search with a click. The response rate stayed the same, but the average rating dropped, which actually helped them identify real problems. Luna: So they got more honest data. That's valuable. Lucas: Right. And then they could link that feedback to specific moments in the journey. If someone gave a low rating after a search, they knew the search wasn't working. It became a diagnostic tool. Luna: But isn't there a risk of survey fatigue? How many times can you ask before users just tune out? Lucas: Great point. The best practice is to limit prompts to once per session and to vary the touchpoint. Don't always ask after search. Sometimes ask after a purchase, sometimes after reading an article. Keep it fresh. Luna: And what about the design of the prompt itself? Should it be a star rating, a smiley face, or an open text box? Lucas: Star ratings are quick but shallow. Smiley faces are good for emotional sentiment. Open text gives richer insight but low completion. I'd suggest a two-step: a quick emoji, then if they're neutral or negative, offer a short text field. That balances volume and depth. Luna: That aligns with something I read from a UX researcher at a major retailer. They found that negative feedback in open text was ten times more actionable than any star rating. Lucas: Exactly. And that data gets lost if you're not mapping the feedback prompt as a touchpoint. It's not just a metric, it's an interaction that shapes the user's perception of your brand. Luna: So how do you convince a team to add it to their journey map? Lucas: Start by showing the cost of ignoring it. If a user gets a poorly timed prompt and gives a one-star rating, that data might trigger a false alarm or, worse, lead to a bad business decision. Put the prompt on the map, annotate the timing, and treat it like any other critical touchpoint. Luna: I like that. It forces the team to think about when and why a user would be receptive. Lucas: And it opens up a conversation about other interstitial touchpoints we ignore — like loading screens, error messages, even the 'back' button. Those all convey emotional signals. Luna: So maybe the real takeaway is that journey maps shouldn't just track the steps you want users to take, but also the ones they have to take. Lucas: That's a great way to put it. The in-app feedback prompt is just one example, but it's a reminder that every interaction, even the ones we consider overhead, reveals how the user feels about your product. Luna: And if you can capture that feeling at the right moment, you can actually improve the journey instead of just measuring it. Lucas: Exactly. So next time you see that pop-up, don't just swipe it away. Think about where it fits in your own journey — and what it's telling you.