ServiceNow Real Estate and Construction La Defense, Paris, France

Loxam

IT Operations Automation

Loxam needed an integrated employee-service and IT service management environment that could replace siloed systems across multiple countries, speed up support responses, and simplify HR and IT processes for staff.

1 Portal for eight countries
300% Decrease in app development budget
72 Hours to complete process that once took weeks

Reported impact

Business outcome

Loxam created a single employee-service portal for eight countries, reduced key process times from weeks to 72 hours, simplified HR and IT support workflows, and cut application redesign costs while giving staff a more consistent multilingual support experience.

  • Cost Reduction
  • Productivity Improvement

Solution

Loxam standardized employee support on ServiceNow IT Service Management to replace siloed country-specific tools with one multilingual portal spanning eight countries. The ITSM portal became the front door for incidents, employee requests, HR content, and lifecycle workflows such as onboarding, offboarding, and transfers, so staff no longer navigate separate systems. Performance Analytics gives the central support organization incident traceability and KPI measurement, while Dynamic Translation lets employees submit and receive support in their own language. Virtual Agent adds natural-language guidance so users can resolve or route issues through automated conversational flows instead of waiting on manual handoffs. The same platform now coordinates IT and broader business workflows, turning ServiceNow into a one-stop employee-service layer that accelerates resolution and lowers the cost of redesigning supporting applications.

Data flow

Employees enter the ITSM portal for incidents, HR content, onboarding, offboarding, transfers, and other business requests. Dynamic Translation localizes those interactions, Virtual Agent guides the user through automated conversational steps, and the resulting cases flow through centralized support workflows while Performance Analytics tracks traceability and KPI performance across countries.

Solution architecture

4 components · 2 layers
  1. Serving
    • Performance Analytics Measures KPIs and incident traceability so the central support team can monitor and improve service performance.
    • Dynamic Translation Lets employees communicate with support teams in their own language through the portal.
    • Virtual Agent Guides users through requests and issue resolution with natural-language interactions.
  2. Orchestration
    • IT Service Management Provides the shared portal and workflow layer for incidents, employee requests, and staff lifecycle processes across multiple countries.

Architecture clues

  • Dynamic Translation allows users to communicate and receive support in their mother tongue.
  • Performance Analytics supplies incident traceability and KPI measurement for the central support function.
  • The ITSM portal is the single point of access for staff across eight countries.
  • The same platform handles incidents, employee requests, onboarding, offboarding, transfers, and other business workflows.

Evidence from the source

"Key processes that once took weeks can now be completed in just 72 hours, and Loxam has been able to cut its app redesign budget by 300%."
"The Dynamic Translation capability allows users across multiple countries to communicate easily and receive support in their mother tongue, while the Virtual Agent guides them through the process using natural language."
"The ITSM portal now provides a single point of access for staff across eight countries, replacing siloed systems and slow service responses."
"The ServiceNow platform provides a simplified digitized experience for employees. It's a one-stop-shop for HR content and helps us simplify processes."
"The result is a platform that can not only manage incidents and employee requests, but also staff onboarding, offboarding and transfers, and IT and other business workflows."
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
    2 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

    Loxam customer story

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