In-house Manufacturing global Company newsroom

Lenovo

Customer Service Automation

Lenovo needed to handle customer support at very large scale across its global device support operation, where routine issues created cost and complexity and human-led resolutions costing $30 to $50 could delay simple fixes, consume expert capacity, and add unnecessary work.

$30 to $50
10%
10%
180 markets

Reported impact

Business outcome

Lenovo's connected AI agents shifted support earlier in the journey, resolving more issues before escalation, reducing human-assisted support demand, accelerating repair and issue resolution, improving customer satisfaction, and lowering support costs.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

Lenovo used its own global support organization as a live deployment for a connected multi-agent AI support model. It first unified support knowledge and device-context data in a knowledge management platform so agents could work from trusted, relevant context rather than isolated scripts. Lenovo Machines Fix Machines Agent monitors device health, detects emerging issues, and resolves eligible problems proactively before human intervention is needed. When an incident requires repair, Lenovo Smart Repair Agent processes the request, diagnoses the issue, creates tickets, generates work orders, and dispatches them to field-service teams. For customer conversations, Lenovo Intelligent Voice Agent gathers issue details, answers questions, and troubleshoots through natural-sounding voice interactions, then transfers the customer and case context to the right specialist when escalation is needed. Lenovo complemented the agents with redesigned workflows, human oversight, and privacy, data-governance, and supplier controls for operation across global markets.

Data flow

Device-context data and support knowledge are brought into a unified knowledge management platform. Lenovo Machines Fix Machines Agent uses that context to detect and resolve issues proactively; if repair is needed, Lenovo Smart Repair Agent diagnoses the case and pushes tickets and work orders to field-service teams; if conversation is still required, Lenovo Intelligent Voice Agent interacts with the customer and passes the case context to a human specialist for escalation.

Solution architecture

3 components · 3 layers
  1. Serving
    • Lenovo Intelligent Voice Agent Handles conversational support, collects issue information, troubleshoots by voice, and transfers cases with context to specialists.
  2. Orchestration
    • Lenovo Smart Repair Agent Processes repair requests, diagnoses issues, creates tickets and work orders, and dispatches work to field-service teams.
  3. Uncategorized
    • Lenovo Machines Fix Machines Agent Monitors device health, identifies emerging issues, and automatically resolves problems before human intervention where possible.

Architecture clues

  • Global support operation spanning more than 75 contact centers, 23,000 technicians, and 180 markets.
  • Lenovo established privacy, data-governance, and supplier controls for customer-facing AI across markets.
  • Lenovo spent more than two years learning how to deploy and operate the agents across a complex support environment.
  • The operating model preserves human oversight for complex cases.

Evidence from the source

"Customer issues are resolved 25% faster, while customer satisfaction has improved by 10% and support costs have fallen by 10%."
"Half of repair orders are now completely touchless, contributing to a more than 90% reduction in time to repair."
"Lenovo Intelligent Voice Agent collects information, answers questions and troubleshoots through natural-sounding voice interaction."
"Lenovo Machines Fix Machines Agent monitors device health, identifies emerging issues and automatically resolves them wherever possible."
"Lenovo Smart Repair Agent processes the request, diagnoses the issue and can automatically create tickets, generate work orders and dispatch them to field-service teams."
"Lenovo first brought together support knowledge and device-context data through a unified knowledge management platform."
"The company handles more than 500 million support tickets each year through a global operation spanning more than 75 contact centers, 23,000 technicians and 180 markets."
"The connected agents now support more than 98% of incoming requests and have contributed to a 75% reduction in human-assisted support volume."
"Today, it addresses 23% of potential support issues before human intervention is required—often before customers realize anything is wrong."
"With a typical human-led resolution costing $30 to $50, applying the same model to simple, commonly encountered issues can delay resolution, consume expert capacity and create unnecessary work for employees."
Transparency Evidence & methodology 100/100 reference value · 94% 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
    7 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence94%
  • Source authority25/25
    The deployment is described by the adopting organization or a government source.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    10 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. Lenovo

    Lenovo customer story

    First-party
    https://news.lenovo.com/customer-support-issues-25-faster-with-connected-ai-agents/
    Source type
    Customer-published story
    Published
    Aug 27, 2026
    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 Aug 27, 2026 · Lenovo · 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.