Alibaba Cloud Travel and Hospitality China Translated from Chinese

Hello Group (哈啰集团)

Customer Service Automation · Sales Automation

Hello Group was handling more than 500,000 service complaints a day across complex mobility transactions, but liability assignment was not accurate enough and customer-service operations were expensive. The company also wanted stronger pre-sales guidance for rental transactions so a large-model agent could improve GMV rather than only automate reactive support.

500,000+ complaints per day
customer-service operating cost reduced 30%+
liability-decision accuracy reached 87%+
rental-car GMV improved 5%

Reported impact

Business outcome

Hello Group turned the transaction robot into a full-chain service and growth lever. The Alibaba Cloud implementation reduced customer- service operating cost by more than 30%, improved rental-car GMV by 5% in guided sales scenarios, and lifted liability-decision accuracy to 87%+, which reduced complaints while improving the user experience across complex mobility transactions.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement
  • Revenue Growth

Solution

Hello Group built a transaction robot on Alibaba Cloud Bailian using a portfolio of Qwen-Plus, Qwen-Turbo, and Qwen2-7B-Instruct models. The robot spans pre-sales, in-sales, and after-sales steps of the mobility transaction chain, combining user-intent recognition, multi-turn conversation, intelligent Q&A, and liability handling into one business-facing service. To make the system practical inside production workflows, the team introduced RAG, chain-of-thought, and tool-calling patterns so the agent can retrieve policy or scenario context, reason across transaction states, and take guided actions in support and sales flows. Instead of treating the LLM as a sidecar chatbot, Hello embedded the agent directly into the transaction process, using different Qwen models for responsiveness and capability tradeoffs. That design turned the robot into both a service-efficiency layer and a revenue-oriented guide for rental scenarios.

Data flow

User requests from pre-sales, order-processing, and after-sales scenarios are routed into the Bailian agent layer, where the appropriate Qwen model is selected. RAG and tool-calling components retrieve policy or order context, the agent reasons over the transaction state, and the output is returned as guidance, liability decisions, or customer-service responses embedded in the business workflow.

Solution architecture

4 components · 2 layers
  1. Compute
    • Qwen-Plus Handles higher-complexity reasoning tasks inside the transaction robot.
    • Qwen-Turbo Supports lower-latency conversation and response steps across the transaction chain.
    • Qwen2-7B-Instruct Provides additional model capacity for specialized transaction-robot tasks.
  2. Orchestration
    • Bailian Hosts and orchestrates the model portfolio and agent-building workflow for the transaction robot.

Architecture clues

  • Multiple Qwen models are used together so different transaction tasks can balance cost, latency, and reasoning depth.
  • RAG, chain-of-thought, and tool-calling are part of the production agent design rather than offline experimentation.
  • The agent is embedded directly into pre-sales, in-sales, and after-sales steps instead of being limited to a standalone chatbot.
  • The system targets both service-cost reduction and GMV growth in the same architecture.

Evidence from the source

Hello combined Qwen-Plus, Qwen-Turbo, and Qwen2-7B-Instruct with RAG, COT, and TOOL techniques to build the agent and upgrade every link of the transaction robot. (original: 哈啰基于千问的 Qwen-Plus、Qwen-Turbo、Qwen2-7B-Instruct 等模型组合... 同时引入 RAG、COT、TOOL 等技术构建 Agent。)
Hello faced more than 500,000 complaints a day and complex order-processing flows, which drove up service cost and exposed inaccurate liability assignment. (original: 哈啰集团在出行领域客诉量每日高达 50 万+ 单,同时订单处理流程复杂,且判责准确率不高,导致客服人工运营成本较高。)
The resulting system reduced customer-service operating cost by more than 30%, raised rental GMV by 5%, and pushed liability accuracy above 87%. (original: 哈啰出行客服运营成本降低 30%+... 租车 GMV 提升 5%... 判责准确率高达 87%+。)
The team wanted a large-model transaction robot that would run through the whole chain from pre-sales to after-sales. (original: 客户希望开发一款基于大模型的交易机器人,贯穿在业务交易的售前售中售后各个环节。)
Transparency Evidence & methodology 100/100 reference value · 95% 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 confidence95%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency10/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. Alibaba Cloud

    哈啰集团基于阿里云百炼打造大模型交易机器人_互联网_阿里云客户案例

    First-party
    https://www.aliyun.com/customer-stories/internet-2024-hellobike
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Region
    • Company size
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • Published on source page Sep 13, 2024 · Alibaba Cloud · First-party
    Open date source
Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.