Customer Service Full-Process Agent Loop

Our client, a leading SaaS platform in Southeast Asia, handles 500,000+ customer service conversations monthly across web chat, mobile app, email, and social messaging channels. Their support operation was caught in a permanent state of catch-up.

First-line agents, many of them newly hired and still learning the product, provided inconsistent answers to the same question depending on who was online. Complex issues required multiple escalation handoffs — L1 to L2 to engineering — each handoff adding hours and losing context. The knowledge base, maintained manually, was perpetually outdated as the product shipped new features faster than the documentation team could update articles.

The client had cycled through three generations of chatbot vendors. Each hit the same operational walls.

• 1.The Dead-End Conversation Problem: Chatbots could answer simple FAQs but couldn't do anything. 'How do I reset my password?' worked. 'Reset my password and send me the confirmation' did not. The bot couldn't execute actions — it could only point to help articles.
• 2.The Escalation Black Hole: When the chatbot failed, the escalation to a human agent lost all context. The customer had to re-explain their issue from scratch. The human agent had no visibility into what the bot had already tried.
• 3.The Misclassification Tax: The existing system classified tickets by keyword matching, resulting in a 30%+ misclassification rate. Billing questions landed in technical support. Feature requests were routed to the bug team. Each misroute added hours to resolution time.
• 4.The Flat Cost Problem: Every conversation — whether a simple 'what are your hours?' or a complex multi-step account migration — consumed the same AI resources at the same cost. At 500,000 conversations per month, this was economically broken.