Streamlining Customer Queries Using AI

I have been working with AI in customer support for a while now. And lately, one thing is becoming clear. This space is getting crowded. Every vendor claims their AI is the magic wand. Just plug it in, and your support problems disappear. But the reality is different. AI isn’t magic. It’s a strategy. It has to be planned, adapted, and rolled out based on: 🔹 Your goals 🔹 Your current challenges 🔹 And your team’s capacity Most support leaders we speak with aren’t confused about the tech. They are confused about where to use it. That’s the real challenge. So we created a simple matrix to help teams make better AI decisions. It’s built on just two questions: 1. What’s the risk if AI gets this wrong 2. How complex is the task When you map support work using this lens, things get clearer: - Use AI fully for low risk, repetitive tasks like tagging, triaging, or summarising. - Use AI as a helper for pattern based tasks like routing, recommending actions, or drafting replies. - Keep humans in control for high risk, complex issues like escalations, complaints, or anything tied to revenue.   And here’s the other mindset shift: Don’t think of support AI as one giant bot. Think of it as a system of specialised agents: 🔹 Analyzers – Understand queries, profiles, logs 🔹 Orchestrators – Manage workflows, routing 🔹 Reasoners – Diagnose problems 🔹 Recommenders – Suggest next steps 🔹 Responders – Write or send replies Each agent plays a specific role, just like your support team does. Done right, AI doesn’t replace humans. It supports them, speeds them up, and helps them focus where it matters most. This approach is also being recognised by the front-runners in the space. At a recent ServiceNow event I attended, many speakers echoed the same thought: AI is not one size fits all. It must be tailored to each organisation’s structure, systems, and bandwidth.   Let’s stop using AI for the sake of it. Let’s start using it where it actually makes a difference.   If you are building or evaluating AI for support and want to walk through the matrix, Feel free to drop me a message.  Always happy to exchange notes.

Two weeks ago I said AI Agents are handling 95% of our sales and support and I replaced $300k of salaries with a $99/mo Delphi clone. 25+ founders DM’d me… “HOW?” Here’s the 6 things you MUST do if you want to run your entire customer-facing business with AI: 1. Create a truly excellent knowledge base. Your AI is only as good as the content you feed it. If you’re starting from zero, aim for one post per day. Answer a support question by writing a post, reply with the post. After 6mo you have 180 posts. 2. Have Robb’s CustomGPT edit the posts to be consumed by AI. Robb created a GPT (link below) that tweaks posts according to Intercom’s guidance for creating content for Fin. The content is still legible to humans, but optimized for AI. 3. Eliminate recursive loops - because pissed off customers won’t buy If your AI can’t answer a question but sends the customer to an email address which is answered by the same AI, you are in trouble. Fin’s guidance feature can set up rules to escalate appropriately, eliminate loops, and keep customers happy. 4. Look at every single question every single day (yes, EVERY DAY). Every morning Robb looks at every Fin response and I look at every Delphi response. If they aren’t as good as they could possibly be, we either revise the response, or Robb creates a support doc to properly handle the question. 5. Make sure you have FAQs, Troubleshooting, and Changelogs. FAQs are an AI’s dream. Bonus points if you create FAQ’s written exactly how your customers ask the question. We have a main FAQ, and FAQs for each sub section of our support docs. Detailed troubleshooting gives the AI the ability to handle technical questions. Fin can solve 95% of script install issues because of our Troubleshooting section. Changelogs allow the AI to stay on top of what’s changed in the app to give context to questins about features and UI as it changes. 6. Measure your AI’s performance and keep it improving. When we started using Fin over 1y ago, we were at 25% positive resolutions. Now we’re above 70%. You can actively monitor positive resolutions, sentiment, and CSAT to make sure your AI keeps improving and delivering your customers an increasingly positive experience. TAKEAWAY: Every Founder wants to replace entire teams with AI. But nobody wants to do the actual work to make it happen. Everybody expects to flip a switch and have perfect customer service. The reality? You need to treat your AI like your best employee. Train it daily. Give it the resources it needs. Hold it accountable for results. Here’s the truth that the LinkedIn clickbait won't tell you… The KEY to successfully running entire business units with AI? Your AI is only as good as the content you feed it. P.S. Want Robb's CustomGPT? We just launched 6-part video series on how RB2B trained its agents well enough to disappear for a week and let AI run the entire business. Access it + get all our AI tools: https://www.rb2b.com/ai

Support teams face constant pressure to resolve cases faster without overloading engineering. For one Glean customer, valuable resources were tied up in avoidable tickets, MTTR (mean time to resolution) hovered at nearly two days, and agents spent hours manually triaging cases. Their goal: boost self-solves, improve MTTR, and reduce R&D reliance – without adding more tools. So they embedded Glean in Zendesk, giving agents prompts to quickly gather knowledge across all company data. In triage, agents use Glean to find similar tickets, summarize runbooks and past Jira investigations, and compile clear updates for customers or well-packaged escalations. That streamlined process now drives faster resolutions, smoother knowledge transfer, and consistent workflows—leading to: • 34% increase in self-solves with more future automation planned - this is incredible progress • 24% faster MTTR (1.9 → 1.5 days) • 2–4 hours saved per week for 85% of users (13–26 business days/year) • Reduced R&D involvement in lower-tier tickets By streamlining resolutions, knowledge transfer, and process consistency, the team achieved remarkable results – proof of what’s possible when AI is embedded into everyday workflows. Stories like this are energizing – showing how teams are using Glean to reimagine what they can accomplish.