Snowflake Travel and Hospitality Yorkshire, England

Jet2

Customer Service Automation

analyze thousands of long customer-service calls at reasonable cost so the business could understand intent, sentiment, and service pain points at scale.

2,000 Calls analyzed daily for customer intent
deploy its use case in just three months

Reported impact

Business outcome

Jet2 deployed its first LLM use case in three months, analyzes about 2,000 calls a day for intent, and found a lower-cost way to maintain high-quality sentiment classification at scale.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement

Solution

Jet2 uses Snowflake and Cortex AI on Snowflake to analyze thousands of long customer-service calls at reasonable cost so the business could understand intent, sentiment, and service pain points at scale. Thousands of daily call transcripts from Jet2 contact centers are stored and analyzed in Snowflake to reveal customer intent, preferences, and pain points. Cortex AI supports the core summarization and classification workflow, and Jet2 maintains an LLMOps framework to tune performance and hold down cost as prompts and classifications evolve. Analysts and service leaders use the outputs to improve customer service, and the same framework is being extended to other communications and self-service insight use cases across the company. Keeping ingestion, storage, transformation, and governed access on one platform reduces handoffs, improves concurrency, and makes it easier to reuse trusted data across teams and applications. Jet2 deployed its first LLM use case in three months,...

Data flow

contact-center call transcripts flow into Snowflake and Cortex AI; curated data and model outputs are then served to analysts, service leaders, and future messaging-channel workflows.

Solution architecture

2 components · 2 layers
  1. Compute
    • Cortex AI Provides in-platform AI functions used for summarization, classification, generation, or model-assisted analysis.
  2. Storage
    • Snowflake Provides the centralized data platform that stores governed datasets and serves analytics or AI workloads.

Architecture clues

  • Combines manual classifications with an adapted Mistral model for cost-effective sentiment analysis.
  • Fine-tunes LLM behavior in Cortex AI and tracks model quality with an LLMOps framework.
  • Runs on Snowflake on AWS.

Evidence from the source

2,000 Calls analyzed daily for customer intent
I don’t think we could have gone down the LLM route at all without Cortex
With no prior experience in LLMs, Jet2 was able to deploy its use case in just three months using Cortex AI
using Cortex AI, Jet2 has been making the most of large language models to analyze customer intent and sentiment across thousands of call transcripts
Transparency Evidence & methodology 75/100 reference value · 77% 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 value75/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 impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence77%
  • 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 provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/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. Snowflake

    Jet2 customer story

    First-party
    https://www.snowflake.com/en/customers/all-customers/case-study/jet2/
    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 Jul 18, 2025 · 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 Jul 9, 2026 · Snowflake · 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.