Streamlining Customer Support Processes

Over the last year, I’ve seen many people fall into the same trap: They launch an AI-powered agent (chatbot, assistant, support tool, etc.)… But only track surface-level KPIs — like response time or number of users. That’s not enough. To create AI systems that actually deliver value, we need 𝗵𝗼𝗹𝗶𝘀𝘁𝗶𝗰, 𝗵𝘂𝗺𝗮𝗻-𝗰𝗲𝗻𝘁𝗿𝗶𝗰 𝗺𝗲𝘁𝗿𝗶𝗰𝘀 that reflect: • User trust • Task success • Business impact • Experience quality    This infographic highlights 15 𝘦𝘴𝘴𝘦𝘯𝘵𝘪𝘢𝘭 dimensions to consider: ↳ 𝗥𝗲𝘀𝗽𝗼𝗻𝘀𝗲 𝗔𝗰𝗰𝘂𝗿𝗮𝗰𝘆 — Are your AI answers actually useful and correct? ↳ 𝗧𝗮𝘀𝗸 𝗖𝗼𝗺𝗽𝗹𝗲𝘁𝗶𝗼𝗻 𝗥𝗮𝘁𝗲 — Can the agent complete full workflows, not just answer trivia? ↳ 𝗟𝗮𝘁𝗲𝗻𝗰𝘆 — Response speed still matters, especially in production. ↳ 𝗨𝘀𝗲𝗿 𝗘𝗻𝗴𝗮𝗴𝗲𝗺𝗲𝗻𝘁 — How often are users returning or interacting meaningfully? ↳ 𝗦𝘂𝗰𝗰𝗲𝘀𝘀 𝗥𝗮𝘁𝗲 — Did the user achieve their goal? This is your north star. ↳ 𝗘𝗿𝗿𝗼𝗿 𝗥𝗮𝘁𝗲 — Irrelevant or wrong responses? That’s friction. ↳ 𝗦𝗲𝘀𝘀𝗶𝗼𝗻 𝗗𝘂𝗿𝗮𝘁𝗶𝗼𝗻 — Longer isn’t always better — it depends on the goal. ↳ 𝗨𝘀𝗲𝗿 𝗥𝗲𝘁𝗲𝗻𝘁𝗶𝗼𝗻 — Are users coming back 𝘢𝘧𝘵𝘦𝘳 the first experience? ↳ 𝗖𝗼𝘀𝘁 𝗽𝗲𝗿 𝗜𝗻𝘁𝗲𝗿𝗮𝗰𝘁𝗶𝗼𝗻 — Especially critical at scale. Budget-wise agents win. ↳ 𝗖𝗼𝗻𝘃𝗲𝗿𝘀𝗮𝘁𝗶𝗼𝗻 𝗗𝗲𝗽𝘁𝗵 — Can the agent handle follow-ups and multi-turn dialogue? ↳ 𝗨𝘀𝗲𝗿 𝗦𝗮𝘁𝗶𝘀𝗳𝗮𝗰𝘁𝗶𝗼𝗻 𝗦𝗰𝗼𝗿𝗲 — Feedback from actual users is gold. ↳ 𝗖𝗼𝗻𝘁𝗲𝘅𝘁𝘂𝗮𝗹 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 — Can your AI 𝘳𝘦𝘮𝘦𝘮𝘣𝘦𝘳 𝘢𝘯𝘥 𝘳𝘦𝘧𝘦𝘳 to earlier inputs? ↳ 𝗦𝗰𝗮𝗹𝗮𝗯𝗶𝗹𝗶𝘁𝘆 — Can it handle volume 𝘸𝘪𝘵𝘩𝘰𝘶𝘵 degrading performance? ↳ 𝗞𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗥𝗲𝘁𝗿𝗶𝗲𝘃𝗮𝗹 𝗘𝗳𝗳𝗶𝗰𝗶𝗲𝗻𝗰𝘆 — This is key for RAG-based agents. ↳ 𝗔𝗱𝗮𝗽𝘁𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗦𝗰𝗼𝗿𝗲 — Is your AI learning and improving over time? If you're building or managing AI agents — bookmark this. Whether it's a support bot, GenAI assistant, or a multi-agent system — these are the metrics that will shape real-world success. 𝗗𝗶𝗱 𝗜 𝗺𝗶𝘀𝘀 𝗮𝗻𝘆 𝗰𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝗼𝗻𝗲𝘀 𝘆𝗼𝘂 𝘂𝘀𝗲 𝗶𝗻 𝘆𝗼𝘂𝗿 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀? Let’s make this list even stronger — drop your thoughts 👇

I was in a call this morning with a respected industry thought leader, and we ended up talking about one of the biggest internal challenges in Customer Success: when things go wrong for a customer, where does the blame live? Is it in Sales for setting the wrong expectation? Is it in Product for missing or broken functionality? Is it in Operations or Accounting for a confusing billing experience? There are plenty of targets, and many CS pros will instinctively point at teams across the org. And honestly, those things do matter — misalignment across functions is one of the most common structural blockers CS organizations face today. But the harder question (the one we often avoid) is this: When something isn’t working for a customer, have we looked in the mirror to see if we played a part in allowing that to happen? Customer Success has the unique privilege of representing the entire company to the customer. We build trust, advocate for outcomes, carry the company flag, and influence how the customer perceives every interaction. And with that privilege comes responsibility: the responsibility to look at ourselves first when issues arise. Not to absorb blame unnecessarily, but to approach every problem with the humility that leads with: 👉 Did we set clear enough expectations? 👉 Did we fully and accurately translate the customer’s needs internally? 👉 Did we communicate with enough context and impact to influence action? 👉 Did we partner with a spirit of collaboration rather than blame? Too often, issues become a game of “whose fault is this?” instead of “what can we learn and fix together?” When CS approaches our role as truth-teller, integrator, and co-owner of outcomes, including our own part in the narrative, the organization becomes better equipped to solve the real problem. Here are three action steps to help us get this right: 🔹 1. Self-Reflect before escalating Before sending that “Urgent Customer Issue” email, ask yourself: Did I fully understand the customer context? Did I include potential solutions or recommendations alongside the issue? 🔹 2. Translate with context, not frustration CS isn’t just reporting facts, we’re bridging perspectives. Partner feedback needs to land in a way that adds clarity and urgency, not just noise. 🔹 3. Lead with humility and accountability Admit when we could’ve done something differently. Highlight wins when the team solves something cross-functionally. Model curiosity and shared ownership rather than pointing fingers. Privilege without responsibility is entitlement. Responsibility without humility is defensiveness. When CS leads with both, we not only protect customer value, we build internal credibility and influence. Let’s keep raising the bar. 👊 #CustomerSuccess #Leadership #CrossFunctionalAlignment #Humility #ServeWell #GrowthMindset #BetterEveryDay #CSLeadership #CreatetheFuture

So, how much did being genuinely nice to our customers earn us this quarter? Now imagine asking this question to your CFO. Today we are well aware and sometimes even obsessed with metrics: NPS, CSAT, churn rates…all perfectly calculated. But translating the warmth of customer happiness into cold, hard financial results? Well, that's not so simple. After all, it is not easy to connect a ‘smiling support rep’ to ‘higher EBIT’. However, the truth bomb here - Top CX performers consistently outperform their competitors. But the magic they create is not just in making customers smile. It is about connecting every delighted customer with revenue, retention, and even willingness to pay a little extra. The question for us to answer is - Are we connecting dots, or just coloring the margins? As business leaders, are we digging deep enough? What would happen if CX was tagged to every financial review, not just a customary part of the annual presentation? You could be walking into your next review, armed with not just satisfaction scores, but a clear graph of what those scores added to the bottom line. If you think ROI from customer experience is not just fairy dust, then here are 4 metrics to add gravitas to your next board meeting: ☘️ C - Customer Retention Track repeat purchase rate/ renewal rate. Know how many customers come back. Even a 5% increase in retention can boost profits considerably. ☘️ T - Ticket Size Happier customers spend more. We all do that. Measure if your CX improvements lead to higher average order value. ☘️ S - Share of Voice Delighted customers talk. Track organic referrals, online reviews and social media mentions. Don't forget - word of mouth reduces marketing costs. ☘️ S - Service Cost Zero-effort experiences reduce complaints and rework. When customers don't need to call back, your cost to serve drops. Measure cost per support ticket and first contact resolution rate. These may not happen in a day, but start somewhere. One step of transition a day leads to transformation over a quarter or a year. Let’s get past the vanity metrics and start making CX pay its own bills. About time no? #cx #customerexperience #serviceexcellence

The best support teams have the worst CSAT scores. Wait, what?! 🤯 I was talking to a SaaS support leader recently, and their C-level exec hit them with the classic question: 💬 “What is good support? In numbers.” And of course, the usual suspects come up: ✅ CSAT above 90% ✅ First Response Time under 2 minutes ✅ First Contact Resolution as high as possible But here’s the thing. None of these actually tell you if support is “good.” Because what if… 👉 Your CSAT is high, but customers churn anyway? 👉 Your First Response Time is fast, but your team is just closing tickets quickly, not solving real problems? 👉 Your FCR is high, but it’s because customers only ask easy questions, avoiding your team for complex issues? Good support isn’t just fast. It’s meaningful. Here’s how I’d measure real quality in support: 🔹 % of support interactions that lead to product improvements 🔹 Churn rate for users who engage with support vs. those who don’t 🔹 Revenue expansion from accounts that interacted with support 🔹 % of issues proactively solved before they even reach a human When we think about support as a business driver, the way we measure success completely changes. So let’s challenge the old way of thinking: What’s one support metric you think is completely overrated? 👇

By the time a customer asks to speak with senior management, the original mistake is often no longer the main problem. A delayed delivery, an incorrect product, a missed commitment, or a breakdown in communication can happen in any business. Customers understand that mistakes are possible, even when dealing with a premium or luxury brand. What they find much harder to accept is indifference. The situation becomes serious when the customer has already explained the issue several times, followed up repeatedly, received conflicting answers, or been transferred between departments without anyone taking responsibility. At that point, the customer is no longer frustrated only by what went wrong. They are reacting to how the business made them feel while they were trying to resolve it. This is why service recovery cannot depend entirely on senior management. If every meaningful complaint must reach the top before someone is willing to act, the business does not have an escalation process. It has an ownership problem. Frontline employees need enough authority to solve reasonable problems, managers need to remain accessible when support is required, and every person involved must understand that passing the customer to someone else does not remove responsibility. The strongest service recovery is usually not dramatic. It begins when one person listens carefully, acknowledges what happened, explains what will be done, and remains accountable until it is resolved. Customers can forgive a mistake when they see genuine ownership. What damages trust is being made to feel that nobody cares enough to solve it. When a complaint reaches senior management in your business, do you investigate only the original mistake, or do you also examine everything the customer experienced afterward? #CustomerExperience #ServiceRecovery #RetailLeadership #LuxuryRetail

Have you ever watched your team solve a customer's problem perfectly, only to have that customer still escalate? It's one of the most frustrating experiences in customer service, and I see it happening more often than ever. Here's what I've discovered after two decades of studying these interactions: Customers don't escalate because problems go unsolved. They escalate because their emotions go unaddressed. Think about it - AI now handles the straightforward questions, which means your team is left with calls where the real issue isn't the policy or the fee. It's what those things mean to the customer in that moment. And that meaning is almost always emotional. I've identified four psychological shifts that can change everything: First, customers escalate when experiences feel unfair, not when solutions are wrong. The human brain treats unfairness as a threat. Even if you give customers exactly what they want, they'll still escalate if the process felt dismissive or out of their control. Second, explaining policies actually intensifies emotions. To a distressed customer, policy language sounds like "no, you're stuck, we don't care." It validates their fear that nothing can change, and trapped people escalate. Third, customers calm down when their future becomes predictable. Uncertainty is emotional gasoline. Your team can lower intensity simply by showing what happens next in a clear, confidence-building way. Fourth, angry customers aren't fighting your employee - they're fighting for their dignity. They're protecting their identity as responsible adults who deserve respect. A customer whose dignity feels intact will accept solutions that a belittled customer will reject outright. Today's customer interactions aren't service calls - they're human distress calls. Your employees need psychological skills to navigate what AI cannot touch: the emotional complexity of human beings under stress. The teams that understand this distinction are seeing dramatic decreases in escalations, not because they're solving more problems, but because they're addressing what customers actually need - psychology, clarity, predictability, and dignity. Need more help navigating challenging conversations with customers? Check out my de-escalation training for customer service professionals: https://lnkd.in/gcBtX7ND

I watched one of my CSM sit in complete silence after his first escalation last week. The fire was technically out. The bug was fixed. The "official" apology was sent. But for him, the Escalation Hangover was just beginning. If you’ve been in Customer Success long enough, you know the symptoms. You start replaying every call. You scan for every missed signal. You start asking yourself: “Could I have prevented this? Do they even trust me anymore? Am I actually good at this?” The truth is, most escalations aren't even about the CSM. They come from product gaps, messy implementations, or internal misalignment. But as the CSM, you’re the face of the recovery and that is a heavy place to stand. If you’re feeling the weight of a fire right now, here is what I told him: Facing an escalation doesn't mean you're bad at your job. It usually means you were close enough to the customer to be the person they trusted with their frustration. The real work starts now. And it isn't about pretending everything is fine. It's about rebuilding belief through three specific moves: 1. Name the mess clearly: Trust dies when you try to minimize the issue. Don't spin it. Say it: “You’re right to be frustrated. This caused a real disruption, and we should have caught it earlier.” You have to own the friction before you can remove it. 2. Prove the system learned: A resolution just answers “Is it fixed today?” A recovery answers, “Why won't it break tomorrow?” The customer doesn't just want a patch; they want proof that your internal process has evolved. Tell them exactly what changed in your communication rhythm or your internal checks so they don't have to stay on guard. 3. Lean into "Boring" Consistency: You don't win back trust with one hero call. You win it back during the quiet, boring weeks that follow. It’s the update that arrives exactly when you promised. It’s the risk you flag two weeks before it becomes a problem. It’s being visible when things are calm, not just when the building is on fire. Escalations are uncomfortable, messy, and sometimes completely unfair. They can shake even the most experienced person. But remember: You don't build deep partnerships when things are easy. You build them in the recovery. You didn’t just fix a bug; you just proved you’re the person who stays in the room when it gets hot. Stop looking for the exit and start looking at the foundation, it’s usually stronger after the fire.

He delivered perfect metrics. She fumbled through a messy slide deck. He got fired. She got promoted. Because she spoke in dollars. Board meeting. Twelve minutes in. Director of Customer Success presents glowing NPS scores. Zero questions from the executives. Next slide: Engineering shows server uptime at 99.97%. Polite nods around the table. Then Marketing presents one number: Customer acquisition cost dropped 23% to just $3,000. Suddenly everyone's awake. Questions for thirty minutes straight. Additional budget approved on the spot. Here's what I learned watching from the back of that room: Numbers without dollar signs are just statistics. Numbers with dollar signs are how businesses make decisions. Last quarter, somewhere out there in the corporate world, a Head of Support rewrote her quarterly review. Version 1 (what she originally wrote): "Response times improved 15% this quarter. Customer satisfaction jumped to 4.8 stars. Team morale is at an all-time high." Version 2 (what got her promoted): "Faster response times retained $890K in at-risk accounts. Higher satisfaction converted $1.1M in expansion opportunities. Improved team retention saved $200K in recruiting, hiring, and training costs." Same achievements. Completely different reception. Her original presentation got polite applause. Her rewrite received accolades. Operational metrics → Financial impact Team performance → Business outcomes Customer feelings → Revenue protection "We reduced bugs by 60%" becomes "Prevented $400K in churn from technical issues." "Users love the new interface" becomes "UI improvements drove $153k in expansion” "Training improved team skills" becomes "Skills development cut support costs $150K annually." Every metric in your company connects to money. Your job is drawing those lines clearly. Because executives don't fund good feelings. They fund good business.

AI in Customer Support isn’t new. I’ve been rethinking how we actually use it. Customer Support is moving past basic "faster replies" and learning to implement Claude as a core part of our workflow. The goal? Shifting from reactive firefighting to structured, scalable systems. It’s a work in progress, but here is the blueprint we’re using to turn Claude into a true CX reasoning engine: 1️⃣ It’s not about speed. It’s about structure. Yes, you can draft replies faster. But the real value comes from setting it up properly: → align it with your tone and guidelines → connect it to your knowledge base → define clear boundaries (what it can and can’t say) → train it to understand context, not just keywords That’s how you get consistent, reliable output across the team. 2️⃣ It helps move Support from reactive → proactive Used well, it’s not just answering tickets. It’s helping you: → detect sentiment and urgency → identify recurring friction points → surface gaps in self-service → spot early churn signals That’s where Support starts influencing the whole customer experience. 3️⃣ It fits into your existing workflows (not replaces them) The most effective setups I’ve seen are simple: → Claude + Zendesk → ticket analysis → Claude + Zapier → automate workflows → Claude + Gong→ review calls → Claude + Intercom → inbox support → Claude + n8n → workflow automation → Claude + Notion → knowledge management No complex rebuilds. Just better use of what you already have. 4️⃣ The quality of output = quality of input Small things make a big difference: → assign a role (support agent, CX lead, analyst) → provide context (customer, goal, constraints) → iterate with examples (good vs bad responses) Without this, you get generic answers. With it, you get something your team can actually use. From a leadership perspective, this isn’t about “adding AI.” It’s about designing how your Support team operates at scale. Because the goal isn’t to answer more tickets. It’s to build a system where fewer things break, and when they do, the experience still feels consistent. If you’re already using AI in Support, what’s actually working for you? 👇

Most companies try to avoid escalations. we have a CSM who LOVES them She gets all the angry accounts, and asks for more - why though? Fires. Broken moments. “We might leave.” She’s saved a lot of them. What's curious is that 3–4 months later they all expand. Her NRR beats accounts that have been “healthy” the whole time. Why? She doesn’t stop at fixing the issue. She rebuilds trust. Most teams: • apologize • resolve • move on She: • owns it end-to-end • brings the customer into the process • proves it won’t happen again That’s the difference between recovery and full recovery. There’s a concept called the 𝘀𝗲𝗿𝘃𝗶𝗰𝗲 𝗿𝗲𝗰𝗼𝘃𝗲𝗿𝘆 𝗽𝗮𝗿𝗮𝗱𝗼𝘅 But it only works if trust goes above baseline, not back to it. If accounts get “saved” but never expand, you didn’t recover. The best measurement of an account being healthy again after a negative event is: Did the account expand afterwards. If it doesn't, you're sitting on a future churn