TCS Media and Entertainment Malaysia

Astro

Document Processing · Marketing Personalization

Astro needed faster and more consistent metadata generation across its web and mobile platforms, but manual tagging slowed content operations, limited scale, created classification inconsistencies, and reduced the quality of the personalization signals used across its OTT experience.

20% improvement in customer satisfaction
90% reduction in manual tagging effort
An estimated ~30% YoY incremental gain by leveraging human-in-the-loop (HITL) feedback
fivefold increase in productivity

Reported impact

Business outcome

Astro automated a labor-intensive metadata function, dramatically cut manual tagging work, improved consistency and throughput across content operations, and strengthened the personalization signals that support a smoother digital entertainment experience for viewers.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

Astro partnered with TCS to turn metadata tagging into an agentic AI workflow instead of a manual media-operations task. TCS used TCS AI VX Studio as the orchestration layer, running on Amazon Bedrock with the NOVA multimodal model so autonomous AI agents could inspect web and app visuals, detect interface elements, and generate semantic metadata such as titles, genres, and categories. Product and content teams stay in the loop through a human-feedback process that corrects outputs and continuously improves prompt behavior as layouts and content formats change. The modular architecture processes assets in parallel for scale, then feeds the enriched metadata into Astro's downstream analytics and recommendation workflows, giving the broadcaster a repeatable way to tag thousands of assets while keeping the model adaptive to new UI patterns.

Data flow

Visual content from Astro's web and mobile platforms is processed by autonomous AI agents running through TCS AI VX Studio on Amazon Bedrock with the NOVA multimodal model. The agents detect UI elements and generate semantic metadata, product and content teams feed corrections back through the human-in-the-loop process, and the enriched tags flow into downstream analytics and recommendation systems.

Solution architecture

5 components · 4 layers
  1. Compute
    • Amazon Bedrock Provides the managed foundation that hosts the agentic AI workflow for metadata automation.
    • NOVA multimodal model Analyzes visual app and web content so the system can classify assets and infer metadata.
  2. Serving
    • autonomous AI agents Generate semantic metadata and adapt tagging behavior as interfaces and content evolve.
  3. Orchestration
    • TCS AI VX Studio Coordinates the media-intelligence workflow that runs content tagging and adaptive improvement loops.
  4. Governance
    • human-in-the-loop feedback Lets product and content teams validate and refine outputs so the tagging system learns continuously.

Architecture clues

  • Human-in-the-loop review continuously refines prompts and tagging accuracy.
  • Modular agents process visual data in parallel for long-term scalability.
  • The metadata output feeds downstream analytics and recommendation experiences.
  • The system analyzes web and app visuals rather than relying on manual metadata entry.

Evidence from the source

"90% reduction in content-metadata management effort"
"AI agents analyse web and app visuals, detect UI elements, and generate semantic metadata"
"Leveraging TCS AI VX Studio, Amazon Bedrock, and the NOVA multimodal model, TCS implemented an agentic AI-powered system"
"a projected two-point rise in net promoter score (NPS) and a 20% improvement in customer satisfaction"
"fivefold increase in content classification"
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
    5 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. TCS

    Astro Transforms Media Operations to Drive Seamless CX

    First-party
    https://www.tcs.com/what-we-do/services/cloud/aws/case-study/astro-transforms-media-operations-seamless-cx
    Source type
    Vendor-published customer story
    Published
    May 10, 2026
    Supports
    • Customer
    • Industry
    • 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
    • Publication date

Date evidence