Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / The One Touchpoint Most Journey Maps Overlook
Transcript
- Lucas: So here's something I've been stewing on. We've done — what, seventy-three episodes now on customer journey maps — and almost every single one focuses on the path to purchase, the moments of delight, the retention loops. But there's one touchpoint that I think we've all been trained to overlook. Luna: I'm intrigued. Which one? Lucas: The first time a customer actually tries to get help. Not the chatbot that pops up when they're browsing. Not the FAQ page. The moment they hit that 'contact us' button or call the support line. That handoff from self-service to live help. Luna: Oh, that's interesting. Because most maps treat support as a post-purchase afterthought, if they map it at all. Lucas: Exactly. And I think it's a massive blind spot. I was looking at data from a mid-market SaaS company — they sell project management software to teams of about fifty to two hundred people. Their journey map was beautiful. They had the awareness phase, the trial signup, the onboarding sequence, the upgrade moment. But when I asked about the support journey, it was basically blank. Luna: So what happened when a customer actually needed help? Lucas: They had a knowledge base, a chatbot that could handle maybe five common questions, and then a ticket form that routed to a shared inbox. The problem was, the journey map assumed that most issues got resolved in the knowledge base. But the data told a different story. About thirty percent of customers who started in the knowledge base ended up submitting a ticket anyway. And of those, about fifteen percent abandoned the process entirely before getting an answer. Luna: So they were losing customers in the gap between self-service and human help. Lucas: Right. And that gap is exactly what the journey map missed. The map had a nice smooth line from 'trial' to 'paid subscription.' It didn't show the frustrating detour where a customer spends ten minutes searching for an answer, then another five minutes filling out a form, and then waits twenty-four hours for a reply. That's not a detour — that's a dead end for a lot of people. Luna: Yeah, I've definitely been that customer. It's the reason I switched from one CRM to another a few years ago. The product was fine, but every time I had a question, I felt like I was jumping through hoops. Lucas: That's the thing — the support handoff is a loyalty moment, but it's usually designed by the support team, not by the journey mapping team. The map stops at conversion, and support is left to figure out the rest. Luna: So how do you map it properly? What does that touchpoint actually look like from the customer's perspective? Lucas: Well, the first thing is to break it into micro-moments. There's the trigger — the customer has a problem. Then the search — they try the knowledge base or the chatbot. Then the escalation — they decide they need a human. Then the wait — they're in the queue. And then the resolution itself. Each of those micro-moments has its own emotional arc. Luna: And each one is a potential drop-off point. If the waiting time is too long, or the chatbot is frustrating, or the ticket form asks too many questions — you lose them. Lucas: Exactly. The SaaS company I mentioned — when they actually mapped that journey, they found that the biggest drop-off was after the chatbot failed. The chatbot would ask the customer to rephrase their question three times, and then say 'I'm sorry, I don't understand. Please submit a ticket.' And a lot of customers just left at that point. Luna: So the chatbot was actually driving churn, not reducing it. Lucas: Precisely. They redesigned the chatbot to hand off to a human after the first failed attempt. And that one change reduced support abandonment by almost twenty percent. Luna: That's a huge improvement from just mapping a few extra steps. Lucas: Absolutely. And I think there's a broader lesson here. If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. It's a small gesture that keeps us independent and lets us keep digging into these specific gaps that most coverage ignores. Luna: Yeah, it really does make a difference. And it means we can keep going deep on one angle instead of trying to cover everything shallowly. So back to the support handoff — you mentioned consumer electronics too? Lucas: Right. There's a well-known brand — let's call them a smart home device maker. They had a similar blind spot. Their journey map went from 'unboxing' to 'setup' to 'daily use.' But they didn't map what happened when a device malfunctioned. And that was the moment that mattered most for loyalty. Luna: So the customer's first experience with a problem became the defining memory of the brand. Lucas: Exactly. They found that customers who had a smooth support experience were actually more loyal than customers who never had a problem at all. But the ones who hit friction — long hold times, being transferred multiple times — those customers were highly likely to switch brands at the next upgrade cycle. Luna: So the support handoff isn't just a service issue — it's a retention and lifetime value issue. Lucas: Hundred percent. And yet most journey maps treat it as an operational detail rather than a strategic one. I think the real opportunity is to treat the first support interaction as a key conversion event, just like signing up for a trial or making a first purchase. Luna: How would that change the way you design it? Lucas: Well, for one, you'd measure the same metrics: completion rate, time to resolution, customer satisfaction. But you'd also look at downstream behavior. Do customers who have a good support experience upgrade faster? Refer more friends? You start to see support as a growth driver, not a cost center. Luna: What about the emotional side? Because when I need help, I'm usually already frustrated. Lucas: Yeah, that's a great point. The emotional state at the start of the support journey is negative — you're trying to solve a problem. So the map should capture that emotional arc: from frustration to relief. And every delay or repetition in the handoff deepens the frustration. Luna: So the ideal handoff would be almost invisible. You ask a question, and the system already knows who you are and what you need. Lucas: Right. Some companies are doing that with context-aware routing. If you're in the middle of using a specific feature, the support system knows that and routes you to a specialist for that feature. No need to explain everything from scratch. Luna: That's a long way from 'please enter your account number and describe your issue in detail.' Lucas: It is. And the companies that have mapped that handoff are seeing the payoff. I think the big takeaway for anyone building journey maps is: don't stop at the purchase. Follow the customer all the way through the first time they need help. That's where the real relationship is forged or broken. Luna: So the next time I'm building a journey map, I'm going to add a new lane just for support. Lucas: Do it. And maybe even start there. Because if you can fix that handoff, you're solving for the moment when the customer is most vulnerable — and most likely to remember what you did. Luna: Yeah, that's a good way to put it. Thanks for that, Lucas. Lucas: Thanks, Luna. And thanks to everyone listening. We'll be back next week with another journey map gap you probably haven't considered.