Baidu AI Cloud Media and Entertainment China Translated from Chinese

37 Interactive Entertainment

Customer Service Automation

37 Interactive Entertainment's legacy intelligent customer service stack struggled to understand gaming slang and fast-changing subculture knowledge, forcing agents to search fragmented knowledge bases manually and miss service-level targets.

Complex-issue diversion accuracy increased 2.4x.
New customer service hires previously needed hundreds of hours of specialized training.
Response delays caused by retrieval mistakes reached 2300+ minutes per month.
SLA attainment increased 38.3 percentage points to 99.3%.

Reported impact

Business outcome

The rebuilt assistant delivered more human-like answers, reduced manual escalations on unclear player requests, and lifted SLA attainment from 61% to 99.3% while improving complex-issue diversion accuracy.

  • Customer Experience
  • Productivity Improvement

Solution

37 Interactive Entertainment rebuilt its game-support stack on Baidu AI Cloud using large models and retrieval-augmented generation. Qianfan ModelBuilder was used to tune prompts and semantic understanding for gaming slang and subculture terms, while Qianfan AppBuilder orchestrated RAG flows that combined the existing service knowledge base with player behavior data and a dynamic knowledge graph. Baidu AI Cloud Keyue Intelligent Customer Service became the frontline support layer, binding common intents such as password recovery or event-rule questions to standard prompt templates for fast answers. More complex issues, including bug and recharge cases, triggered multi-turn dialogues to collect device and scenario details before the system called technical-team interfaces to create tickets. Unresolved conversations were clustered and reviewed so prompts, constraints, and tone controls could be updated continuously.

Data flow

Player questions enter Baidu AI Cloud Keyue, where Qianfan AppBuilder routes them through RAG workflows that retrieve the customer-service knowledge base, player behavior data, and the dynamic knowledge graph. Qianfan ModelBuilder-backed prompts then generate answers, while complex issues trigger multi-turn clarification and ticket creation through technical-team interfaces.

Solution architecture

3 components · 3 layers
  1. Compute
    • Qianfan ModelBuilder Provides the large-model and prompt-iteration environment used to improve semantic understanding for gaming-specific language and workflows.
  2. Serving
    • Baidu AI Cloud Keyue Intelligent Customer Service Runs the frontline game-support experience that answers common requests and escalates complex cases to downstream teams.
  3. Orchestration
    • Qianfan AppBuilder Orchestrates the RAG customer-service flows that combine prompts, knowledge retrieval, and multi-turn issue handling.

Architecture clues

  • Complex issues trigger multi-turn dialogue and technical-team ticket creation
  • Dynamic knowledge graph combines customer-service knowledge with player behavior data
  • High-frequency intents are bound to prompt templates for near-instant responses
  • RAG-based intelligent customer service system
  • Unresolved-session clustering is used to revise prompts and constraints

Evidence from the source

37 Interactive Entertainment rebuilt its intelligent customer service system with Baidu AI Cloud large models plus RAG technology (original: 三七互娱基于百度智能云大模型+RAG技术重构智能客服系统).
Complex-issue diversion accuracy increased by 2.4x and SLA attainment rose to 99.3% (original: 实现游戏垂直领域语义理解准确率从62.3%提升至行业领先水平,SLA达成率跃升38.3个百分点至99.3%).
High-frequency questions are bound to prompt templates for second-level responses, while complex issues trigger multi-turn dialogues and technical-team ticket interfaces (original: 将高频问题…与提示词模板绑定,实现秒级响应;对复杂问题…再调用技术团队接口生成工单).
Service SLA attainment improved from 61% to 99.3% (original: 服务SLA达成率从61%提升至99.3%).
The model combines customer-service domain knowledge with player behavior data to build a dynamically updated knowledge graph (original: 将游戏客服领域的专业知识…与玩家行为数据结合,构建动态更新的知识图谱).
The system adds empathy constraints such as 'player-centered' and 'friendly tone' so AI responses balance professionalism and affinity (original: 通过添加“以玩家为中心”“语气友好”等提示词约束,平衡AI回答的专业性与亲和力).
Transparency Evidence & methodology 100/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    4 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    6 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Baidu AI Cloud

    37 Interactive Entertainment customer story

    First-party
    https://cloud.baidu.com/customer/case/sanqihuyu.html
    Source type
    Vendor-published customer story
    Published
    Jun 17, 2025
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Jun 17, 2025 · Baidu AI Cloud · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.

Related

Similar use cases

See all like this