Baidu AI Cloud Consumer Goods China Translated from Chinese

vivo

Customer Service Automation

vivo wanted its BlueLM-powered phone assistant to answer general questions while also retrieving current and authoritative information without forcing users to open browsers or other apps.

Reported impact

Business outcome

vivo upgraded its assistant from a general-purpose model interface to a real-time service surface that saves users time, improves accuracy and strengthens the brand's AI-phone positioning.

  • Customer Experience
  • Productivity Improvement

Solution

vivo integrated Baidu AI Cloud's Qianfan platforms into the BlueLM and BlueLM Assistant stack so its phone assistant could mix model reasoning with fresh web knowledge. The core architectural change was the introduction of a retrieval-augmented generation path connected to Baidu Search. When users ask about weather, stocks, exchange rates, policy changes, travel or current affairs, BlueLM Assistant can invoke Baidu Search-sourced retrieval components rather than relying only on a static device model. The result is a hybrid design in which vivo keeps its own BlueLM device-side experience and assistant persona, while Baidu provides model services and the RAG pathway that grounds answers on recent information with source traceability. The same collaboration also explores a broader phone-agent ecosystem, positioning the assistant as a front door for more specialized mobile intelligence rather than only a chat interface.

Data flow

Phone-assistant questions are routed through BlueLM Assistant; when a topic needs timely information, RAG with Baidu Search retrieves fresh results, which the model stack summarizes and returns inside the phone assistant without forcing a browser handoff.

Solution architecture

4 components · 3 layers
  1. Compute
    • Qianfan ModelBuilder Supports the large-model integration and optimization work behind BlueLM Assistant.
  2. Serving
    • RAG with Baidu Search Retrieves current, sourceable information for time-sensitive assistant questions.
    • BlueLM Assistant Provides the user-facing intelligent-assistant experience on vivo phones.
  3. Orchestration
    • Qianfan Application Platform Packages the application workflows that connect assistant requests to model services.

Architecture clues

  • The assistant delivers results without requiring users to switch into a browser
  • The collaboration also explores broader mobile-agent ecosystems
  • The design explicitly uses RAG components connected to Baidu Search

Evidence from the source

The challenge was enabling BlueLM Assistant to fetch the latest internet information while preserving general Q&A abilities (original: 首先面临的主要挑战是如何让“蓝心小V”在保持通用问答的基础上,实现实时获取互联网最新资讯和权威内容的能力).
The solution improves retrieval for weather, stocks, exchange rates, policy, travel and current events without requiring users to open a browser (original: 针对天气、股票、汇率、政策、出行、时事新闻等领域迅速、准确地为用户提供所需信息,无需跳转浏览器).
vivo used Qianfan together with the RAG with Baidu Search components to connect to Baidu Search-sourced real-time content (original: 通过RAG with Baidu Search系列组件接入与百度搜索同源的实时联网内容).
Transparency Evidence & methodology 75/100 reference value · 82% 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 value75/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 impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence82%
  • 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 evidence15/20
    3 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 specificity8/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

    vivo customer story

    First-party
    https://cloud.baidu.com/customer/case/vivo.html
    Source type
    Vendor-published customer story
    Published
    May 14, 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 May 14, 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.