OpenAI Software / SaaS North America

Netomi

Customer Service Automation

Enterprise AI agents needed to coordinate messy, high-volume service workflows across many backend systems while staying low-latency, policy-compliant, and predictable under real production load.

98% intent classification accuracy
Close to two million provider requests each year for one dental-insurance customer
Sub-three-second responses at scale
Traffic above 40,000 concurrent customer requests per second during major sporting events

Reported impact

Business outcome

Netomi created a blueprint for agentic enterprise systems that stay responsive under burst traffic, keep policy controls inline, and scale safely across demanding customer-service and regulated workflows.

  • Customer Experience
  • Risk Reduction
  • Scalability

Solution

Netomi built an Agentic OS that combines OpenAI GPT-4.1 and GPT-5.2 inside a governed execution layer for production-grade enterprise agents. GPT-4.1 handles low-latency tool use and fast reasoning for transactional workflows, while GPT-5.2 takes on deeper multi-step planning and complex orchestration. The runtime is designed for ambiguity: requests can span booking engines, loyalty databases, CRMs, payments, policy logic, and knowledge sources, so Netomi uses structured planning, persistence reminders, explicit tool-use expectations, and rich-media decisions to keep state across long tasks. The company also architected the platform for concurrency rather than serial pipelines, allowing it to sustain sub-three-second responses during traffic bursts such as major sporting events. Governance is intrinsic to execution, with schema validation, inline policy enforcement, PII protection, deterministic fallback, and full observability so agent behavior remains auditable in regulated settings like insurance and travel.

Data flow

Customer requests are classified and routed through the Agentic OS, which calls backend systems such as CRMs, booking engines, payments, and policy services in parallel. GPT-4.1 or GPT-5.2 then reasons over the results, while governance checks validate tools, enforce policies, mask PII, and back off to safe paths if confidence drops.

Solution architecture

3 components · 2 layers
  1. Compute
    • GPT-4.1 Provides fast, predictable tool use and low-latency reasoning for real-time workflows.
    • GPT-5.2 Handles deeper multi-step reasoning, structured planning, and long-running orchestration tasks.
  2. Orchestration
    • Agentic OS Coordinates backend systems, governance, concurrency, and execution for enterprise-grade AI agents.

Architecture clues

  • Concurrency is designed into the system instead of executing classify → retrieve → validate → call tools → generate output sequentially
  • Context-led ensemble architecture is emphasized for airline workflows
  • Governance layer includes schema validation, inline policy enforcement, PII protection, deterministic fallback, and runtime observability
  • Platform uses persistence reminders, explicit tool-use expectations, structured planning, and agent-driven rich media decisions

Evidence from the source

"DraftKings ... with traffic during major sporting events spiking above 40,000 concurrent customer requests per second"
"Netomi has sustained sub-three-second responses with 98% intent classification accuracy"
"The governance is not bolted on—it’s part of the runtime."
"Their platform pairs GPT‑4.1 for low-latency, reliable tool use with GPT‑5.2 for deeper, multi-step planning"
Transparency Evidence & methodology 96/100 reference value · 87% 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 value96/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 specificity16/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 confidence87%
  • 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
    4 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • 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. OpenAI

    Netomi customer story

    First-party
    https://openai.com/index/netomi/
    Source type
    Vendor-published customer story
    Published
    Jan 8, 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

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