IBM Travel and Hospitality France

Serre Chevalier

Customer Service Automation

Serre Chevalier needed a smarter way to answer multilingual, context-dependent visitor questions about ski-pass selection and trip planning because its earlier assistant could not keep pace with growing resort complexity and seasonal support demand.

1 second response latency, down from 6–8 seconds
1500+ conversations handled in the first month
94% of customer complaints resolved in under 48 hours
went live in approximately two and a half weeks

Reported impact

Business outcome

The new AI agent reduced response latency, improved complaint resolution, handled large volumes of visitor conversations, and created a platform the resort can extend into operational workflows beyond customer care.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

Serre Chevalier worked with IBM, Next Decision, and IBM Client Engineering to replace its older digital assistant with an agentic support experience built on IBM watsonx Orchestrate and IBM Cloud. The system is structured as cooperating agents that interpret visitor intent, retrieve the most relevant resort knowledge, and invoke supporting tools such as Python-based utilities to answer questions about ski passes, trip planning, and operational details in real time. As the deployment matured, the resort added IBM watsonx.governance for monitoring and visibility and IBM watsonx.ai for recurring data-gathering work such as daily web scraping that feeds operational workflows. Because the AI is embedded directly into the website, visitors get guided help without changing channels, while service teams spend less time on routine inquiries and can focus on the more complex issues that still require human intervention. The same orchestration model is now expanding into snow operations, HR workflows, and predictive equipment dashboards.

Data flow

Visitor questions arrive through the Serre Chevalier website, watsonx Orchestrate routes them to agents that retrieve resort knowledge and process live inputs, responses are returned in near real time, and supporting watsonx.ai automation and governance feed the operational dashboards and future expansion areas such as snow monitoring and equipment management.

Solution architecture

5 components · 4 layers
  1. Compute
    • IBM watsonx.ai Automates recurring data-gathering tasks such as daily web scraping that feed operational workflows.
  2. Serving
    • IBM Cloud Hosts the visitor-facing AI experience so it can scale during busy planning and travel periods.
  3. Orchestration
    • IBM watsonx Orchestrate Coordinates the resort’s agentic AI workflows for visitor support and emerging operational use cases.
    • IBM Client Engineering Helped align objectives, workflows, and data inputs so the agentic experience could be launched quickly.
  4. Governance
    • IBM watsonx.governance Improves visibility and monitoring across the resort’s multi-LLM setup and operations dashboards.

Architecture clues

  • Future prototypes include artificial-snow monitoring, HR process automation, and predictive-maintenance dashboards.
  • The solution is built as a coordinated set of agents rather than a traditional chatbot.
  • watsonx.ai is used for daily web-scraping routines that feed operational workflows.

Evidence from the source

“Since the start of the winter season, the AI agent has handled more than 1,500 customer conversations”
“The AI experience itself is built as a coordinated set of agents rather than a traditional chatbot.”
“The resort now uses IBM watsonx.governance to give marketing and operations teams clearer visibility through improved dashboards and multi-LLM monitoring.”
“reducing response latency from 6–8 seconds to about 1 second”
“the teams aligned early on the objectives, workflows, and data inputs the system would need to coordinate.”
Transparency Evidence & methodology 100/100 reference value · 89% 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
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • 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 provenance10/10
    The publication date comes from the source page or publisher.
  • 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. IBM

    Serre Chevalier customer story

    First-party
    https://www.ibm.com/case-studies/serre-chevalier
    Source type
    Vendor-published customer story
    Published
    Apr 6, 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.