NVIDIA Telecommunications Global

Amdocs

Customer Service Automation · IT Operations Automation · Sales Automation

Amdocs needed to help telecom providers automate complex customer and network workflows with domain-specific AI while lowering inference cost and latency enough for near-real-time production use.

Near-real-time responses for end users
Reduced query latency by approximately 80 percent
Reduced token consumption by as much as 60 percent for data preprocessing
Reduced token consumption by up to 40 percent for inferencing

Reported impact

Business outcome

With NVIDIA NIM microservices and the surrounding telecom AI stack, Amdocs reduced token use by as much as 60 percent in preprocessing and up to 40 percent in inferencing, while cutting query latency by about 80 percent so end users receive near-real-time responses across commerce, care, and operations.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement

Solution

Amdocs built its amAIz platform on NVIDIA infrastructure to create telecom-specific generative AI agents for sales, billing, care, and network operations. NVIDIA DGX Cloud and NVIDIA AI Enterprise provide the training and enterprise AI foundation for commercially available and domain-adapted LLMs, while NVIDIA NIM microservices expose optimized inference endpoints and support frameworks such as NVIDIA TensorRT-LLM, vLLM, and SGLang. Amdocs also built an LLMOps pipeline around the NVIDIA AI Blueprint for building data flywheels, combining NVIDIA NeMo microservices for fine-tuning, evaluation, and guardrailing with NVIDIA NIM for deployment. On top of that stack, Amdocs uses NVIDIA Nemotron and Llama Nemotron to power amAIz agents that can autonomously handle multistep telecom journeys and plug into AI factories as reusable production services.

Data flow

Telecom workflow context enters amAIz, DGX Cloud and NeMo-based data-flywheel pipelines adapt and guardrail domain models, NIM serves the resulting models and agents through optimized inference frameworks, and the agents return actions or responses for sales, billing, care, and network operations.

Solution architecture

7 components · 4 layers
  1. Compute
    • NVIDIA DGX Cloud Provides the training environment for commercially available and domain-adapted telecom LLMs.
  2. Serving
    • amAIz Serves as Amdocs’ domain-specific generative AI platform and agent layer for telecom workflows.
    • NVIDIA NIM Delivers the inference microservices that deploy and serve telecom AI agents with lower cost and latency.
    • NVIDIA Nemotron Provides reasoning-capable open models for advanced AI agents.
    • Llama Nemotron Powers amAIz agents that complete multistep telecom journeys across sales, billing, and care.
  3. Orchestration
    • NVIDIA AI Enterprise Supplies the enterprise software foundation that lets amAIz integrate with AI factories and production telecom environments.
  4. Governance
    • NVIDIA NeMo microservices Handle fine-tuning, evaluation, and guardrailing in Amdocs’ LLMOps data-flywheel pipeline.

Architecture clues

  • Amdocs built its LLMOps pipeline on the NVIDIA AI Blueprint for building data flywheels.
  • NVIDIA NeMo microservices are used for fine-tuning, evaluation, and guardrailing before deployment through NIM.
  • The universal LLM NIM microservice supports NVIDIA TensorRT-LLM, vLLM, and SGLang.

Evidence from the source

Amdocs built a robust LLMOps pipeline based on the NVIDIA AI Blueprint for building data flywheels; NVIDIA NeMo™ microservices for streamlined fine-tuning, evaluation, and guardrailing; and NVIDIA NIM™ microservices.
Amdocs is using NVIDIA DGX™ Cloud and NVIDIA AI Enterprise software to develop and deliver solutions based on commercially available large language models (LLMs) and domain-adapted models.
Amdocs reduced the number of tokens consumed for deployed use cases—by as much as 60 percent for data preprocessing and by up to 40 percent for inferencing.
The collaboration has successfully reduced query latency by approximately 80 percent, ensuring that end users experience near-real-time responses.
They’re also using NVIDIA NIM™, a set of easy-to-use inference microservices designed to accelerate the deployment of generative AI across enterprises.
Transparency Evidence & methodology 100/100 reference value · 79% 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
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • 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 provenance0/10
    The publication date has no documented provenance.
  • 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. NVIDIA

    Amdocs customer story

    First-party
    https://www.nvidia.com/en-us/case-studies/amdocs-builds-generative-ai-agents-for-telecom/
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Sep 25, 2024 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Oct 16, 2025 · NVIDIA · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.