OpenAI Travel and Hospitality Global

Omio

IT Operations Automation · Marketing Personalization

Omio needed to move beyond travel search interfaces and accelerate internal product delivery so customers could discover and book multimodal journeys conversationally while teams built and operated faster.

3,000+ transportation providers connected through AI-powered travel experiences
47 countries covered across Omio’s global transportation network
Accelerated projects from roughly one quarter to one month
Reduced new-product development effort to approximately 20% of previous levels

Reported impact

Business outcome

Omio created one of the earliest conversational travel experiences, accelerated engineering output, reduced product-development effort, and began shifting both customer discovery and internal work toward AI-native operating models.

  • Customer Experience
  • Productivity Improvement
  • Speed to Market

Solution

Omio connected OpenAI models directly to its transportation inventory and booking systems to turn trip planning into a conversational commerce experience. Early ChatGPT integrations let travelers ask natural-language questions such as which route is fastest or whether a flight or train is better, and the answers are grounded in live inventory and pricing across Omio’s network of more than 3,000 providers in 47 countries. The company later expanded this into a dedicated ChatGPT experience connected to its global transportation network so AI can surface real, bookable journeys instead of static advice. Internally, Omio rolled out ChatGPT across the business and then embedded Codex deeply into engineering, from research and planning to testing, code review, monitoring, and maintenance. It is also building custom connectors that pull internal systems and workflows into AI tools so employees can move from information retrieval into execution as the company becomes AI-native.

Data flow

Traveler questions are sent through ChatGPT and OpenAI APIs connected to Omio’s live transportation inventory, pricing, and booking systems so the system can return verified journeys. Internally, product tasks and system context move through ChatGPT, Codex, and custom connectors that tie AI tools to Omio’s data and workflows.

Solution architecture

4 components · 3 layers
  1. Compute
    • OpenAI API Connects Omio’s live transportation inventory and pricing data to AI-powered travel experiences.
  2. Serving
    • ChatGPT Provides the conversational interface travelers use to ask for trip options and employees use for internal experimentation.
    • Dedicated ChatGPT experience Packages Omio’s conversational travel workflow into an AI-native booking and discovery experience.
  3. Orchestration
    • Codex Supports engineering work across research, planning, coding, testing, reviews, monitoring, and maintenance.

Architecture clues

  • ChatGPT was connected directly to live transportation inventory and pricing
  • Codex is used across the full software development lifecycle
  • Custom integrations and connectors bring internal systems and data directly into AI-powered tools
  • Omio treats conversational travel as an interface layer over real-world transportation systems

Evidence from the source

"Reduced product development effort to approximately 20% of previous levels"
"Today, every engineer uses Codex throughout the software development lifecycle"
"connecting OpenAI models directly to Omio’s transportation inventory and booking systems"
"helping users discover real, bookable journeys through conversation"
Transparency Evidence & methodology 90/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 value90/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 impact15/25
    1 metric 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

    Omio customer story

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