Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / Why Journey Maps Miss the Context Continuity Touchpoint
Transcript
- Lucas: Here's a number that should bother anyone who builds customer journeys: according to Zendesk's 2025 CX Trends report, 72 percent of customers say that having to repeat information when they switch channels is the single most frustrating part of any service interaction. Luna: And I bet if you look at most journey maps, that moment doesn't even have a sticky note on the wall. Lucas: Exactly. We map the web visit, the chat, the phone call, the email – but we treat them as separate lanes on the same highway. The moment the customer says 'I already told you that' – that's a touchpoint. And it's invisible. Luna: So what's the official name for that? Context continuity? Cross-channel handoff? Lucas: I've seen it called 'context continuity' in the CX literature, but I prefer 'the handoff that shouldn't fail.' Most journey maps assume the customer's memory persists. But from the customer's perspective, they've just told someone their account number, explained the problem, verified their identity – and then they're transferred and asked to do it all over again. Luna: Right, it's like being stuck in a customer service version of Groundhog Day. Lucas: Let's make it concrete. Picture a telecom customer who starts a billing dispute on the website chat. The chatbot can't resolve it, so it escalates to a live agent. The customer pasted their account number and described the charge. But the chat system and the phone system use different databases – so when the agent takes over, the customer has to repeat everything. That's a context discontinuity. Luna: And that's not even a rare edge case. That's the norm for most companies. Lucas: It is. And the journey map, as drawn, shows a nice smooth arrow from Chat to Phone. It doesn't show the friction of re-entry. It doesn't show the customer's sigh. It doesn't show the drop-off risk. Luna: How big is that drop-off risk? Do we have data? Lucas: Forrester did a study a couple years back – I think 2019, but it's still cited – that found 42 percent of customers will abandon a channel switch if they have to re-explain. And 33 percent say it makes them less loyal to the brand. So this is not a minor annoyance. It's a churn trigger. Luna: That's huge. Yet I bet most marketing teams don't even have this as a line item in their journey map review. Lucas: They don't. And that's because journey maps are usually created by marketers thinking about the funnel, not by operations people thinking about continuity. The mental model is 'channels in sequence' rather than 'customer data flowing between channels.' Luna: So what does a journey map that actually accounts for context continuity look like? Can you give me an example of a company that does this well? Lucas: Amazon is the gold standard. When you contact Amazon customer service – whether through chat, phone, or email – they already know your name, your order history, and what you've recently looked at. You rarely have to repeat anything. That's because they have a unified customer profile that every channel reads from. Their journey map doesn't just have channel steps; it has a permanent data layer underneath. Luna: That makes sense. But Amazon has massive engineering resources. What about a mid-market company? Can they get close? Lucas: Yes, but it requires conscious design. One of the simplest things a journey map can add is a 'context transfer' step between any two channels that a customer might use in sequence. And then you ask: 'What data must survive this handoff so the customer doesn't have to repeat?' Usually it's identity, recent activity, and the issue description. You can start with CRM integration and chat transcripts. It's not trivial, but it's not Amazon-scale either. Luna: So the fix is partly technology, but partly just mapping the handoff as a touchpoint – naming it forces teams to ask the right questions. Lucas: Exactly. If you put a sticky note on your journey map at the point where the customer moves from web to phone, and you label it 'Ensure context is passed', suddenly it becomes a design requirement rather than an afterthought. That's the power of journey mapping – it makes the invisible visible. Luna: And we should add that this isn't just about service calls. Think about marketing: someone clicks a Facebook ad, lands on your site, adds a product to cart, then leaves. Later they come back via email and the cart is still there. That's a form of context continuity. Lucas: Great point. The same principle applies to retargeting. If the customer has to search for the product again, you've broken context. The magic is when the email knows exactly what they looked at. That's why abandoned cart emails work – they're context continuity in marketing. Luna: So maybe the missing touchpoint is broader than just service handoffs. It's any moment where the customer expects the brand to remember them. Lucas: Yes. And the cost of forgetting is real. There's a reason we keep coming back to these missed touchpoints on this show – because journey maps, as useful as they are, are inherently drawn from the company's perspective. We put ourselves in the center and draw arrows outward. But the customer's experience is seamless or it's not. And seams show up at the handoffs. Luna: I want to talk about something we don't do on this show, which is run ads. We keep these episodes ad-free because we believe the content itself is valuable enough to stand on its own. And if you feel like you've gotten value from these conversations – maybe you've even used a concept in your own marketing – the best way to support that choice is a small contribution at buy me a coffee dot com slash fexingo. It's not a requirement, it's just a way to keep the show independent and free of sponsors. Lucas: Yeah, and it really does make a difference. It means we can keep diving into the specific, practical details without having to tailor anything for an advertiser. So if you're able, throw a few dollars in the virtual tip jar. Otherwise, let's get back to the handoff problem. Luna: So we've talked about the problem and a few solutions. Let's get into the nitty-gritty of actually designing a context continuity touchpoint in a journey map. Lucas: Let's do it. I want to walk through a specific scenario: a customer starts a complaint via email, then phones in. Most companies handle this as two separate interactions. But if you map it as one journey with a handoff, you can design a protocol: the phone agent should have the email thread visible, and the customer should not have to restate the problem. Simple in theory, tough in practice. Luna: What are the barriers? Is it usually technology or culture? Lucas: Both. Technology because email systems and phone systems often don't talk to each other. Culture because teams are measured on their own channel metrics – email team cares about email resolution time, phone team cares about call handling time. No one is measured on 'seamless handoff.' So there's no incentive to share data. Luna: So the journey map itself can be an advocacy tool. If you put the handoff on the map, you can say: 'Look, this is part of the customer's experience. Who owns it? How do we measure it?' Lucas: Exactly. And once it's on the map, you can start to measure failure rates. For example, how many customers mention the previous channel when they contact you? That's a proxy for context failure. If it's high, you know you have a problem. Luna: I read a case study about a bank that did exactly that. They found that 15 percent of phone calls started with the phrase 'I already emailed about this.' That became their baseline. They implemented a screen pop that showed the customer's recent interactions, and that number dropped to 4 percent. Lucas: That's a beautiful example. And that 15 percent might seem small, but think about the cumulative frustration. If you're a customer and you experience that every time you call, you start to look for another bank. Luna: So the key takeaway for today: when you draw your next journey map, don't just draw arrows from one channel to the next. Draw a dotted line above each arrow and label it 'context transfer.' Force the team to define what information travels and how. Lucas: And if you can't define it, you've found a gap. That's the touchpoint that's missing. It's not a click, it's not a page view – it's a moment of expectation. And brands that consistently meet that expectation earn a loyalty that's hard to copy. Luna: Alright, next time we'll tackle another one of these blind spots. Until then, happy mapping.