Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / How Journey Maps Miss the Customer Service Chatbot Handoff
Transcript
- Lucas: So, Luna, I was looking at a customer journey map we built for a telecom client last quarter, and we had this neat little arrow that said 'escalate to human agent.' And I realized we had no idea what actually happened inside that moment. We treated it like a single step when it's really a miniature journey of its own. Luna: You mean the chatbot to human handoff? Because I feel like that's the moment I'm most likely to scream at my phone. Lucas: Exactly. And it's the touchpoint that almost every journey map just glosses over. But there's real data here. A 2025 study from a customer experience consultancy found that 78% of consumers have had to repeat their issue when moving from a bot to a human. That's nearly four out of five people. Luna: Seventy-eight percent? That's brutal. And I bet that number is even worse when the bot is really confident and then suddenly dumps you. Lucas: Right, and the emotional context matters. You're already frustrated by the problem, you've spent time typing your issue, and then you have to start over. It's like being put on hold for ten minutes and then getting disconnected. The handoff is where the relationship can really break. Luna: So why do you think journey maps keep missing it? Is it just because it's a transition, not a content moment? Lucas: Partly. Journey maps love clear, tangible steps: browse, add to cart, checkout, receive email. But a handoff is more like a relay race — you have to pass the baton smoothly, and that's a process, not a single tick. Maps also tend to be built from internal silos. The chatbot team owns the bot, the call center team owns the humans, and nobody owns the seam between them. Luna: That explains why I always get the 'let me transfer you' moment and then I'm suddenly in a queue with no idea if anyone knows why I called. Lucas: Exactly. Let's break down what actually happens in a good handoff versus a bad one. In a good handoff, the bot recognizes it's hit its limit — maybe the customer's tone shifted, or it's detected repeated requests, or the issue is simply beyond its skill set. Then it should set expectations: 'I'll connect you with a human. It'll take about two minutes.' Luna: Setting expectations matters. Because the worst thing is the silent hold, right? Lucas: Yes. And then the bot should pass along the context in a structured way. The agent sees the conversation history, the customer's account info, even the sentiment analysis. The customer shouldn't have to repeat a single thing. That's the baseline. Luna: But I've also had handoffs where the agent clearly didn't get the context and asked me to describe the problem from scratch. That's when I just give up. Lucas: And that's the cost. You're not just losing that interaction; you're losing future revenue. A study from earlier this year suggested that a single bad support experience can cost a brand up to 15% of that customer's lifetime value. And the handoff is a prime spot for that to happen. Luna: So how do you actually map this? Like, what does a proper touchpoint look like on a journey map? Lucas: You have to treat it as a multi-stage flow. Start with the trigger — what prompts the handoff? Is it a keyword, a sentiment score, or the customer asking for a human? Then the handoff itself — how is it communicated? Then the transfer — what information travels with the customer? And finally, the recovery — how does the agent re-establish rapport? Luna: And you need to measure each stage, not just the overall satisfaction. Because a bad transfer can be fixed if the agent is empathetic, but you can't fix it if you don't know it's broken. Lucas: Right. One of our clients added a post-handoff survey that asked specifically about the transfer process, and they found that even when the resolution was successful, customers who had to repeat themselves were 30% less likely to recommend the brand. Luna: That's a huge number. So what are the rules for a good handoff? Can you distill it down? Lucas: I'd say three things. First, the bot should know its limits. Don't let it flail for ten minutes before transferring. Second, the handoff should be transparent — tell the customer what's happening and why. And third, the context must be preserved seamlessly. The agent should already know the issue before they even say hello. Luna: And what about the actual language? Like, is there a best practice for what the bot says? Lucas: Good question. Instead of 'I'm sorry, I can't help you with that,' which feels like a dead end, you can say 'I want to make sure you get the best help, so I'm connecting you with a specialist who can take care of this right away.' That frames it as a solution, not a failure. Luna: I like that. It's almost like the bot is a concierge rather than a gatekeeper. Lucas: Yeah, and that mindset shift is what separates brands that get it from brands that don't. Let me give you a concrete example. There's a mid-size SaaS company we've been following — I won't name them, but they redesigned their handoff earlier this year. They used to have a very basic bot that would just say 'Transferring you now' and dump you into a queue. Luna: I'm already cringing. Lucas: They rebuilt it so the bot would ask a couple of diagnostic questions first, then say 'Great, I have what I need. Sarah will take over from here, and she already knows your issue. While you wait, here's a summary on screen.' And they saw their customer effort score drop by 12 points in a month. Luna: Twelve points is massive. But that's also a big redesign. What can a smaller company do on a budget? Lucas: You can start with something as simple as a screen share or a live text dashboard. Even having the bot say 'You're being connected to a human who can help' and then actually doing it in under a minute makes a difference. The key is to not leave the customer in limbo. Luna: And what about the agent side? Do they need special training for this? Lucas: Yes, but it's not about technical skills. It's about acknowledging the context. Agents should be trained to say something like 'I see you've been working with our chatbot about your billing issue. Let me take it from here.' That one sentence builds trust instantly. Luna: That makes sense. It's like the customer is being handed off like a baton, not a hot potato. Lucas: And that's exactly what journey maps should capture. We tend to draw happy paths, but the handoff is often where the path gets rocky. If you map it as a flow, you'll see the friction points: 'customer repeats information' should be a red flag, not a step. Luna: So for our listeners who are working on their own journey maps, what's the one thing they should look at first? Lucas: Pull your chat transcripts and look for the phrases that indicate frustration — 'are you a robot?', 'let me talk to a human', 'can I just call someone?' — and trace back to what triggered that. You'll quickly see if your bot is forcing people to the handoff unnecessarily. Luna: And if they find that, they can fix it by adding a simple escalation path earlier in the conversation. Lucas: Exactly. And you know, this whole deep dive reminds me of why I love this show. We get to take these tiny, overlooked moments and show how much they matter. And, you know, if these conversations have sparked something you've actually used at work, that's exactly why the show exists. Luna: And it's why we keep it ad-free. So if you've ever gotten value from an episode, the best way to keep that going is to buy us a coffee at buy me a coffee dot com slash fexingo. It's a small gesture, but it genuinely keeps us going. Lucas: Yeah, that's the only ask we ever make. So, back to the handoff — one more thing I want to emphasize. The best handoffs are actually invisible. The customer shouldn't even notice they've moved from bot to human, except for the fact that they're suddenly getting better service. Luna: That's a nice way to think about it. The goal is to make the transition seamless enough that nobody checks the label. Lucas: Right. And the next time you're mapping a journey, don't just draw an arrow. Zoom in, map the transfer, and measure the effort. That's where the real wins are hiding. Luna: I'm definitely going to look at our chat logs differently now. Thanks for pulling the curtain back on this one. Lucas: Anytime, Luna. And for everyone listening, if you want to see a sample handoff flow, we've put a template in the show notes. But for now, that's our journey.