ServiceNow Retail Germany

ROSSMANN

Customer Service Automation · IT Operations Automation

ROSSMANN store managers had to leave the sales floor, call headquarters, and work issues through siloed HR, IT, and store-operations systems, turning each support case into a slow manual handoff.

1,500 person-hours have already been returned to the business
10,000 hours annually as more branches and knowledge connect to the platform
50% Reduction in labor costs
6 AI agents live

Reported impact

Business outcome

ROSSMANN cut AI-handled case work from nine minutes of human labor to under five seconds, reached 98% routing accuracy, reduced labor costs by 50%, and projected €20-30 million in annual operating savings as more stores come onto the platform.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement

Solution

ROSSMANN consolidated store support on ServiceNow by building a mobile experience on Retail Operations and then layering AI Agents over the case workflow. Every store associate can open the app, submit an issue by text or voice in their own language, attach photos, and follow status without phoning headquarters or switching channels. For damaged deliveries, the AI agent inspects the image, identifies the product, asks for missing information such as delivery date, and pulls guidance from the knowledge base before preparing a complete case for the right team. Simpler requests, including login issues, can be handled end to end by the AI agent itself. That architecture replaced separate HR, IT, and store-operations support paths with one digital backbone that classifies, prioritizes, routes, and closes work in seconds instead of minutes.

Data flow

A store associate submits a text, voice, or photo report through Retail Operations. AI Agents classify the issue, ask for missing details, and use the knowledge base to prepare or resolve the case before routing any remaining work to the correct headquarters team.

Solution architecture

3 components · 3 layers
  1. Compute
    • AI Agents Analyze text, voice, and images, request missing details, route cases, and autonomously resolve simple support issues.
  2. Storage
    • knowledge base Supplies the guidance that AI agents use to prepare cases and improve routing accuracy.
  3. Serving
    • Retail Operations Powers the mobile store-support app where associates submit and track cases.

Architecture clues

  • Six AI agents are already live on the platform.
  • The frontline app accepts text, voice, and photo inputs in associates' own languages.
  • Ticket routing and prioritization improved from 56-60% accuracy to above 94% within two weeks by adjusting knowledge articles.

Evidence from the source

A single manual case averaged nine minutes of human labor across departments.
Accuracy in routing tickets to the right teams has now climbed to 98%
The AI agent scans the image, identifies the product, and classifies the issue
What could once take up to nine minutes of back-and-forth now takes less than five seconds.
the equivalent of €20-30 million annually.
Transparency Evidence & methodology 95/100 reference value · 79% 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 value95/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/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
    4 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • 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 provenance0/10
    The publication date has no documented provenance.
  • 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. ServiceNow

    ROSSMANN customer story

    First-party
    https://www.servicenow.com/customers/rossmann.html
    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

  • Sitemap last modified Jul 30, 2026 · ServiceNow · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
  • Unverified extracted date Jul 30, 2026 · ServiceNow · Unknown Legacy extracted date without source-page confirmation.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.