Artificial Intelligence 16 min read

Architecture and Evolution of the 58 Intelligent Q&A Chatbot System

This article details the design, iterative development, and performance optimizations of 58's AI‑driven intelligent Q&A chatbot, covering its overall three‑layer architecture, the QABot, TaskBot, and answer‑recommendation modules, as well as dynamic strategy adjustment, caching mechanisms, and real‑world deployment results.

58 Tech
58 Tech
58 Tech
Architecture and Evolution of the 58 Intelligent Q&A Chatbot System

Background

58.com, a leading Chinese lifestyle service platform, generates massive Q&A data from interactions between users, merchants, and customer service agents. To improve communication efficiency, the 58 AI Lab built an intelligent Q&A robot that combines natural language processing, deep learning, semantic understanding, and intelligent recommendation to accurately recognize user intent and provide automated answers.

Overall Architecture

The system adopts a three‑layer design: an access layer, a logic layer, and a data layer. The access layer handles template, gateway, Q&A management, and business‑opportunity services. The logic layer, built on micro‑services, includes NLU, rule‑matching, retrieval, prediction, ranking, and dialogue‑management services. The data layer stores Q&A, operational, and knowledge‑base data, supporting model training and real‑time updates via annotation and integration platforms.

QABot

QABot provides business‑specific question answering by leveraging deep‑learning models, rule‑based matching, and retrieval. User queries are processed through NLU, rule matching, retrieval (BM25), and prediction (BI‑LSTM+DSSM) services, then merged and ranked to produce a single answer, a list, a chit‑chat response, or a fallback.

To meet growing traffic, the original serial processing pipeline was parallelized: rule matching, retrieval, and prediction run concurrently, and their results are fused according to priority, reducing overall latency to the longest‑running sub‑service.

Performance optimizations also include multi‑level caching (in‑memory loading, WMB message‑bus synchronization, and LRU eviction) to ensure millisecond‑level data freshness for knowledge‑base updates.

TaskBot

TaskBot enables multi‑turn dialogues for complex business scenarios and proactive business‑opportunity guidance. Its architecture consists of a data layer (NLU metadata, multi‑turn Q&A store, dialogue scripts) and a logic layer (dialogue state tracking, policy selection, and natural language generation). The system integrates NLU, knowledge‑graph disambiguation, and configurable strategy boxes to allow plug‑and‑play workflow adjustments.

Answer Recommendation

The recommendation module offers input suggestions, "you may also ask", and scene‑based ranking to guide users and reduce input errors. Initially it used BM25 for recall; later it incorporated a full recommendation pipeline (recall → ranking) with algorithms such as TF‑IDF, DSSM, XGBoost, and DeepFM, all experimentable via the ABTest platform.

Dynamic Strategy Adjustment

All services are wrapped in a plug‑in strategy box architecture, allowing AB testing of multiple models and policies simultaneously. This enables rapid iteration, continuous performance improvement, and easy customization for different business lines and scenarios.

Conclusion

The iterative evolution of the intelligent Q&A robot exemplifies a "small steps, fast iteration" development philosophy. By progressively launching QABot, TaskBot, and recommendation services and then optimizing performance, caching, and strategy configurability, the system now achieves near‑human accuracy and conversion rates in customer‑service and merchant‑assistant scenarios.

architectureAINLPChatbotquestion answering
58 Tech
Written by

58 Tech

Official tech channel of 58, a platform for tech innovation, sharing, and communication.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.