IBM Telecommunications Italy

WINDTRE

Customer Service Automation · IT Operations Automation

WINDTRE needed to automate and accelerate claims handling for telecom service issues because high report volumes, stateful operational complexity, and repetitive service-desk tasks were slowing response times and consuming staff effort.

10,000+ reports handled per month with AI and automation
10X faster response time
40%–60% of reports are non-service desk related
over 200,000 reports handled in an automated manner

Reported impact

Business outcome

WINDTRE automated a large portion of complaints handling, dramatically improved response time, reduced repetitive desk work, and created a foundation for expanding AI and analytics into infrastructure-incident management.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

WINDTRE and IBM built an “Intelligent Automation” platform on IBM Cloud to analyze, enrich, route, and resolve service complaints with minimal human effort. IBM Consulting designed and manages the solution, using watsonx Assistant to classify incoming reports, Watson Knowledge Studio to build domain-specific annotators, and Watson Natural Language Understanding to extract relevant facts from unstructured ticket text. Once the AI layer completes the analysis, the ticket is enriched with information pulled from WINDTRE’s internal systems and passed to robotic process automation components—a dispatcher that queues work and performer robots that execute the resolution actions. Because the RPA runs on cloud virtual machines, WINDTRE can scale multiple robots in parallel while dashboards continuously track volume, performance, and benefits. The result is a claims-management workflow that blends NLP, AI classification, ticket enrichment, and RPA so the service desk can focus on higher-value problems while routine issues are resolved or routed automatically.

Data flow

Customer reports are classified by watsonx Assistant, enriched with information from WINDTRE systems using Knowledge Studio and NLU outputs, then passed to dispatcher and performer robots on IBM Cloud so issues are resolved, partially resolved, or routed to the right team automatically.

Solution architecture

5 components · 3 layers
  1. Compute
    • IBM Watson Knowledge Studio Creates the machine-learning and rules-based annotators used to train the solution on WINDTRE’s domain topics.
    • IBM Watson Natural Language Understanding Extracts relevant information from complaint text so tickets can be enriched and routed accurately.
  2. Serving
    • IBM Cloud Hosts the virtual machines and cloud services used to scale the intelligent automation stack securely.
    • IBM watsonx Assistant Classifies complaint reports and initiates the automated claims workflow.
  3. Orchestration
    • IBM Consulting Designed, developed, and manages the end-to-end claims automation solution for WINDTRE.

Architecture clues

  • Dedicated dashboards continuously monitor performance, volume, and expected benefits.
  • Robotics run on virtual machines in the cloud for secure scale-out.
  • The RPA layer has a dispatcher component and performer robots.

Evidence from the source

“The agreement between the two companies ... is based on the combination of AI services available on IBM Cloud and automation systems.”
“The response time is 10 times faster than before”
“The watsonx Assistant product classifies reports”
“Watson Knowledge Studio creates machine-learning and rules-based annotators”
“over 10,000 reports per month ... are handled”
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
    2 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
    5 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. IBM

    WINDTRE customer story

    First-party
    https://www.ibm.com/case-studies/windtre
    Source type
    Vendor-published customer story
    Published
    Apr 3, 2024
    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

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.