OpenAI Retail Global

Choco

Customer Service Automation · Document Processing

Choco needed to turn unstructured food orders arriving through email, SMS, images, documents, and phone calls into accurate ERP orders without forcing distributors to expand manual order-entry teams.

2x productivity gains
Maintains error rates below 1–5%
Processes over 8.8 million orders annually
Supports 24/7 order intake

Reported impact

Business outcome

Choco now processes millions of orders with materially less manual entry, higher team productivity, low configurable error rates, and 24/7 intake, letting distributors scale order operations without adding headcount at the same pace as volume.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

Choco rebuilt its food-distribution platform around OpenAI APIs so order capture could move from workflow support to execution. OrderAgent ingests multimodal inputs including emails, SMS messages, images, and documents, then uses transcription, extraction, structured outputs, function calling, and customer-specific context from prior ordering behavior to convert them into ERP-ready orders. VoiceAgent extends the same model to phone ordering through the Realtime API with sub-second latency, enabling distributors to accept spoken orders after hours while maintaining continuity with the rest of the ordering stack. Choco also built evaluation infrastructure with ground-truth datasets, continuous monitoring, and A/B testing so the system can decide when to trigger an optional Autopilot mode and when to keep humans in the loop. The result is a context-aware operational agent that can resolve ambiguity at order capture instead of relying on staff to translate every incoming request by hand.

Data flow

Orders arrive as emails, texts, images, documents, or phone calls and are routed through OrderAgent or VoiceAgent. OpenAI models transcribe, extract, and resolve ambiguous items against customer-specific history and catalogs, then produce ERP-ready orders; Autopilot can finalize confident cases while low-confidence cases go to human review.

Solution architecture

5 components · 3 layers
  1. Compute
    • OpenAI APIs Provide the speech, extraction, embeddings, and function-calling capabilities at the core of Choco's platform.
    • Realtime API Powers sub-second voice interactions for always-on phone ordering.
  2. Serving
    • OrderAgent Converts multimodal customer order inputs into structured, ERP-ready orders.
    • VoiceAgent Lets customers place orders naturally over the phone with low-latency AI conversations.
  3. Governance
    • Autopilot Automatically processes orders when confidence thresholds are met while leaving edge cases for human review.

Architecture clues

  • Ground-truth datasets, continuous monitoring, and A/B testing govern rollout
  • Inference layers resolve ambiguity against customer ordering history and catalog context
  • Multimodal order capture handles email, SMS, images, documents, and phone calls
  • Realtime API powers after-hours phone ordering with sub-second latency

Evidence from the source

"Enables 2x productivity gains"
"OrderAgent ... processes multimodal inputs—including emails, SMS, images, and documents—and converts them into structured, ERP-ready orders."
"Processes over 8.8 million orders annually"
"VoiceAgent, powered by OpenAI’s Realtime API"
Transparency Evidence & methodology 100/100 reference value · 92% confidence · 2 sources

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 confidence92%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency9/10
    2 source references 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

    Choco customer story

    First-party
    https://openai.com/index/choco/
    Source type
    Vendor-published customer story
    Published
    Apr 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
  2. Built In

    Choco

    Third-party structured profile
    https://builtin.com/company/choco

    The Built In page's structured data sets 'numberOfEmployees' to 447, and the profile also shows '447 Total Employees.'

    Source type
    structured profile
    Supports
    • Company size

Date evidence

  • Published on source page Apr 27, 2026 · OpenAI · First-party
    Open date source
Not separately sourced Industry, Region. Treat these normalized attributes as lower-confidence until a dedicated source is added.