Introduction

WPP IT ServiceNow is a useful case study for understanding how a large global enterprise can use ServiceNow to manage IT services, incidents, requests, self-service, automation, service desks, and operational workflows. WPP is a global communications, marketing, technology and commerce organization with a complex international operating environment. Public information from WPP and its technology partners shows that ServiceNow has been used as part of WPP’s employee IT support experience, including self-service and service-desk operations.

ServiceNow IT Service Management (ITSM) provides capabilities for incident, problem, change and service-request management on a common platform and data model.

For consultants, the interesting part is not simply knowing that WPP uses ServiceNow. The more valuable lesson is understanding how ServiceNow can support a large, distributed organization where different business units, countries, support teams and technology environments need to operate through common service-management processes.

This article explains the WPP ServiceNow context, the underlying ITSM architecture, practical implementation scenarios, integration considerations, testing strategy, and lessons that can be applied to enterprise ServiceNow projects.

Important: Publicly available information describes WPP’s ServiceNow usage and transformation at a high level. Internal configuration, tables, workflows, integrations, security roles and implementation details are not publicly documented. Therefore, configuration examples below are representative enterprise implementation patterns rather than claims about WPP’s private configuration.

What Is WPP IT ServiceNow?

WPP IT ServiceNow can be understood as the intersection of three areas:

1. Enterprise IT service management
2. Employee-facing IT support
3. Technology operations and automation

ServiceNow acts as a workflow platform through which employees can raise issues or requests, support teams can process them, automation can execute repetitive activities, and management can measure service performance.

ServiceNow describes ITSM as a platform for managing incidents, problems, changes and service requests while providing self-service and AI-supported capabilities.

In a large organization such as WPP, this becomes particularly important because the operating environment can contain:

• Multiple countries
• Multiple business units
• Different agency environments
• Distributed employees
• Multiple technology teams
• Cloud and on-premises infrastructure
• Different endpoint platforms
• Different support groups
• External service providers
• Different service-level requirements

A ServiceNow implementation therefore needs more than a ticket form.

It needs a standard operating model.

Why ServiceNow Is Important in a Large Enterprise

Consider a typical employee problem:

“My laptop cannot connect to the corporate network.”

Without a centralized ITSM platform, the employee might:

• Send an email to IT
• Contact a local support person
• Call a help desk
• Send a Teams message
• Open a ticket in another system

The support organization then has to manually determine:

• Who owns the issue?
• Is this a laptop problem?
• Is this a network problem?
• Is the employee working remotely?
• Is the issue affecting other users?
• Is there an existing incident?
• Is there a known problem?
• Does an SLA apply?

With ServiceNow, these activities can be structured into a workflow.

Employee → Service Portal → Incident → Categorization → Assignment → Diagnosis → Resolution → Closure → Reporting

ServiceNow’s current ITSM architecture is built around a shared platform, data model and workflow engine, allowing service-management processes to be connected instead of operated as isolated tools.

WPP ServiceNow: Publicly Documented Context

WPP’s technology transformation has publicly been described through its partnership with Kyndryl.

One documented component was omnichannel IT support, including support through chat, telephone, self-service and physical IT Tech Bars, with the self-service experience using ServiceNow.

The published case study also describes automation and operational improvements across WPP’s technology environment. The reported results include substantial reductions in ServiceNow ticket volumes in one transformation period, automated IT events, cloud migration and incidents resolved without human intervention. These are WPP/Kyndryl-reported case-study figures rather than independently audited benchmarks.

More recently, publicly posted WPP recruitment information describes a broader service-management platform transformation, including simplification of legacy complexity, standardization, governance, self-service, intelligent routing, workflow automation and AI-enabled service management.

This is an important architectural lesson:

Enterprise ServiceNow implementation is not a one-time configuration project. It evolves with the organization’s operating model.

Key ServiceNow Capabilities Relevant to WPP-Style IT Operations

1. Incident Management

Incident Management deals with unplanned interruptions or degradation of IT services.

Example:

An employee’s VPN stops working.

A typical incident contains:

The assignment and priority rules should be driven by defined business policies rather than individual agent judgment.

2. Service Request Management

A service request is different from an incident.

Example:

“I need Microsoft Visio installed.”

The employee is not reporting a failure. They are requesting something.

A mature implementation therefore separates:

Incident

Something is broken.

Request

I need something.

This distinction improves reporting, SLA measurement and automation.

3. Self-Service

Self-service is particularly important in large organizations.

An employee should ideally be able to:

• Search the knowledge base
• Check service status
• Request software
• Request access
• Report an incident
• Check ticket status
• Communicate with support

WPP’s publicly described transformation included self-service through ServiceNow as one of its support channels.

4. Knowledge Management

Before creating an incident, the user can be directed to a knowledge article.

For example:

Problem: VPN authentication failure

Knowledge article:

1. Confirm internet connectivity.
2. Restart VPN client.
3. Clear cached credentials.
4. Reauthenticate.
5. Contact service desk if the issue persists.

If the article solves the issue, no incident needs to be created.

That is one of the simplest ways to reduce unnecessary ticket volumes.

5. SLA Management

ServiceNow can track service commitments such as:

• Response time
• Resolution time
• Priority
• Assignment
• Business hours
• Escalation

Example:

These values are illustrative. Actual targets must come from the organization’s service-level agreements.

Real-World WPP-Style Implementation Scenarios

Scenario 1: Global Employee Service Desk

Imagine employees across India, UK, US and Australia raising IT incidents.

The implementation needs:

• Regional assignment groups
• Follow-the-sun support
• Business calendars
• Priority rules
• Escalation policies
• Multilingual support where required
• Knowledge articles
• Service-level monitoring

A request raised in India during Indian business hours may be routed to the India service desk.

When that team’s operating hours end, unresolved work can be transferred to another regional team.

This is more sophisticated than simply assigning tickets to a static support group.

Scenario 2: Laptop Provisioning

An employee joins the organization and requires:

• Laptop
• Standard software
• VPN
• Email
• Security tools
• Collaboration applications

Instead of creating six independent tickets, ServiceNow can orchestrate the request.

Request → Approval → Asset allocation → Device provisioning → Application deployment → Security validation → Employee notification

The actual provisioning activities may be executed through endpoint-management or identity platforms, while ServiceNow remains the workflow and service-management layer.

Scenario 3: Network Outage

Suppose 200 employees report that an office network is unavailable.

A poor implementation might create 200 unrelated incidents.

A mature service-management design identifies a common underlying issue.

The operational flow can become:

Monitoring alert → Major incident → Affected service identification → Employee communication → Technical remediation → Problem investigation → Closure

This is where integration between ITSM and IT operations becomes valuable.

WPP IT ServiceNow Architecture

A practical enterprise architecture can be represented as follows:

                         Employees
                            |
        -----------------------------------------
        |             |            |             |
      Portal         Chat        Phone         Mobile
        |             |            |             |
        -----------------------------------------
                            |
                    ServiceNow Platform
                            |
       -------------------------------------------
       |              |             |             |
    Incident       Request        Change        Problem
    Management     Management     Management    Management
       |              |             |             |
       -------------------------------------------
                            |
                    CMDB / Service Data
                            |
       -------------------------------------------
       |              |             |             |
     ITOM           Identity       Endpoint      Cloud
       |             Systems       Management    Platforms
       -------------------------------------------
                            |
                    Automation / APIs
                            |
       -------------------------------------------
       |              |             |             |
     Azure          AD/IAM        Oracle        Other
    Services                      Fusion        Enterprise

The exact architecture varies by organization.

The important principle is that ServiceNow should orchestrate work rather than become a replacement for every enterprise system.

ServiceNow and Enterprise Integrations

In a large environment, ServiceNow rarely operates alone.

Typical integrations include:

For Oracle environments, ServiceNow can also participate in workflows surrounding employee access, application support and enterprise service requests.

For example:

Employee joins organization

→ HR system creates worker record
→ Identity platform creates account
→ ServiceNow creates onboarding tasks
→ Application access requests are generated
→ Approvals are performed
→ Downstream systems provision access

If Oracle Fusion HCM is part of the landscape, an integration platform such as Oracle Integration Cloud Gen 3 can be used where appropriate to connect Oracle applications with external systems.

The important design principle is to define system of record ownership before building the integration.

Prerequisites for a ServiceNow Enterprise Implementation

Before configuration starts, a project team should establish the following.

Process prerequisites

• Incident process
• Request process
• Problem process
• Change process
• Major incident process
• Knowledge process
• Escalation process

Organizational prerequisites

• Support groups
• Assignment groups
• Service owners
• Process owners
• Application owners
• Approvers

Technical prerequisites

• ServiceNow instance
• Identity integration
• Email configuration
• Integration endpoints
• CMDB strategy
• Authentication mechanism
• Monitoring integrations

Governance prerequisites

• Naming standards
• Development standards
• Update-set/application strategy
• Security model
• Integration standards
• Change governance
• Data retention requirements

Step-by-Step: Building a Typical Enterprise ITSM Flow

The following example demonstrates how a consultant could build a simplified IT support process.

Step 1 – Define the Service

Start by identifying the service.

Example:

Service: Corporate VPN

Define:

• Service owner
• Support group
• Business criticality
• Availability expectations
• Knowledge articles
• Related configuration items

Do not start by creating fields and scripts.

Start with the business service.

Step 2 – Define Incident Categories

Example:

Network
   ├── VPN
   ├── Wi-Fi
   ├── LAN
   └── Internet

Hardware
   ├── Laptop
   ├── Monitor
   └── Keyboard

Software
   ├── Microsoft Office
   ├── Browser
   └── Business Application

Keep the category structure manageable.

One common implementation mistake is creating hundreds of categories that agents rarely use consistently.

Step 3 – Define Assignment Rules

Example:

IF Category = Network
AND Subcategory = VPN
THEN Assignment Group = Network Support

A more mature implementation may use service, location, configuration item or business unit as additional routing inputs.

Step 4 – Configure Priority

Priority should normally be derived from impact and urgency.

Example:

Impact = High
Urgency = High
        ↓
Priority = Critical

A documented priority matrix prevents individual agents from assigning priorities inconsistently.

Step 5 – Create Knowledge Articles

For frequently reported issues, create knowledge articles before implementing extensive automation.

Example:

VPN Password Reset

The article can guide employees through the standard process.

If self-service resolves the issue, ticket creation can be avoided.

Step 6 – Configure Notifications

Typical notifications include:

• Incident created
• Incident assigned
• Incident reassigned
• Additional information requested
• Incident resolved
• Incident closed
• SLA approaching breach
• Major incident communication

Notifications should be meaningful.

Sending too many emails can create another operational problem.

Step 7 – Configure Automation

Once the manual process is stable, automate repetitive activities.

Example:

Password reset request

Employee Request
       ↓
Identity Verification
       ↓
Approval / Policy Validation
       ↓
Identity System
       ↓
Password Reset
       ↓
ServiceNow Update
       ↓
Employee Notification

The automation layer should have logging and error handling.

Testing the ServiceNow ITSM Implementation

Testing should be scenario-based rather than limited to checking whether records can be created.

Test Case 1 – Normal Incident

Create:

VPN unavailable for one employee.

Expected result:

• Incident created
• Correct category selected
• Correct assignment group determined
• Priority calculated
• SLA attached
• Notification generated

Test Case 2 – High-Impact Incident

Create an outage affecting an entire office.

Expected result:

• High-impact classification
• Appropriate priority
• Correct support team
• Escalation triggered
• Communication workflow initiated

Test Case 3 – Service Request

Request software installation.

Expected result:

• Catalog item submitted
• Approval generated
• Fulfillment task created
• User receives status updates
• Request closes after fulfillment

Test Case 4 – Integration Failure

Simulate a downstream system failure.

For example:

ServiceNow
    ↓
REST API
    ↓
Identity Platform
    X
Authentication Failure

The expected behavior should be:

• Integration error logged
• Transaction status retained
• User receives appropriate status
• Retry mechanism executes where appropriate
• Support team can investigate the failure

Do not allow an integration failure to silently appear as a successful transaction.

Common Implementation Challenges

1. Legacy Customization

Large ServiceNow environments often accumulate customizations.

A transformation project may discover:

• Custom scripts
• Duplicate workflows
• Unused fields
• Old integrations
• Custom tables
• Duplicate catalog items
• Complex business rules

Before rebuilding everything, inventory the existing platform.

2. Too Many Assignment Groups

If every department creates its own support group, routing becomes complicated.

Instead, establish clear ownership boundaries.

Ask:

“Who is actually responsible for resolving this service?”

rather than:

“Which team historically owned this ticket?”

3. Poor CMDB Data

Automation becomes unreliable when configuration-item relationships are inaccurate.

For example:

Business Service
      ↓
Application
      ↓
Database
      ↓
Server
      ↓
Network

If those relationships are incorrect, impact analysis and automated routing can also become unreliable.

4. Excessive Customization

A common enterprise mistake is modifying the platform for every historical business process.

A cleaner approach is:

1. Understand the requirement.
2. Check standard capability.
3. Configure standard functionality.
4. Use extension points where necessary.
5. Customize only when there is a clear business reason.

Public information about WPP’s current transformation specifically emphasizes reducing legacy complexity and moving toward more standardized platform capabilities.

5. Automation Without Process Governance

Automation does not fix a poorly designed process.

For example:

Automating an incorrect approval process simply makes incorrect approvals happen faster.

First standardize the process.

Then automate it.

Best Practices for WPP-Style ServiceNow Implementations

Use a global template

Define common global processes for:

• Incident
• Request
• Problem
• Change
• Knowledge
• Major incident

Then allow controlled regional variations.

Separate global and local requirements

A global company may need:

Global

• Priority model
• Incident lifecycle
• Security standards
• Reporting definitions

Local

• Business hours
• Language
• Regulatory requirements
• Regional support groups

Do not allow every country to build an independent version of the platform.

Build reporting around business outcomes

Do not report only:

“We closed 50,000 tickets.”

Also measure:

• Mean time to resolution
• First-contact resolution
• SLA compliance
• Self-service adoption
• Reopened incidents
• Repeat incidents
• Customer satisfaction
• Automation rate
• Ticket avoidance

WPP’s publicly documented transformation provides an example of why these metrics matter: its case study connects service-management changes with ticket reduction, automation and employee experience outcomes.

Treat ServiceNow as a platform

Do not think only in terms of Incident Management.

The platform can connect:

• ITSM
• ITOM
• ITAM
• Security
• HR workflows
• Customer service
• Enterprise service management
• App development

ServiceNow currently positions its platform around shared data, workflows and AI capabilities across business functions.

WPP IT ServiceNow: Consultant Perspective

A useful lesson from the WPP example is that enterprise service management is fundamentally an operating-model problem supported by technology.

A consultant joining such a project should not begin with:

“Which ServiceNow module should we configure?”

Instead, begin with:

“How does the organization currently deliver IT services, and where are the delays, duplication and ownership gaps?”

Then map:

Business Requirement
        ↓
Service Model
        ↓
ITSM Process
        ↓
ServiceNow Configuration
        ↓
Integration
        ↓
Automation
        ↓
Reporting
        ↓
Continuous Improvement

This approach prevents the implementation from becoming a collection of unrelated workflows.

Frequently Asked Questions

1. What is WPP IT ServiceNow?

WPP IT ServiceNow refers to the use and transformation of ServiceNow-based enterprise service-management capabilities within WPP’s technology environment. Public case-study information describes ServiceNow self-service as one channel in WPP’s employee IT support model.

2. What does ServiceNow do in an IT organization?

ServiceNow can manage incidents, service requests, problems and changes while providing self-service, workflow automation, knowledge management, reporting and integrations with other enterprise systems.

3. Is WPP currently using the same ServiceNow platform described in older case studies?

Public information indicates that WPP has been undertaking a broader service-management platform transformation and has described replacing its existing ServiceNow platform with a modern service-management platform. Because the detailed implementation roadmap is not public, older case-study architecture should not automatically be assumed to represent WPP’s current production environment.

Summary

WPP provides a useful enterprise example for understanding ServiceNow ITSM at global scale. The publicly documented environment demonstrates the importance of self-service, omnichannel support, automation, service management, operational integration and continuous improvement.

For consultants, the most important takeaway is that ServiceNow implementation should not be treated as simply configuring incident forms and workflows. A successful enterprise implementation requires:

• A clearly defined service model
• Standard ITSM processes
• Strong governance
• Reliable CMDB and service data
• Controlled customization
• Well-designed integrations
• Meaningful automation
• Effective self-service
• SLA and experience measurement
• Continuous platform improvement

For organizations integrating ServiceNow with Oracle Fusion applications, the same principles apply: clearly identify the system of record, define the integration contract, use appropriate APIs or integration middleware, implement error handling, and maintain traceability across both systems.

For additional Oracle Cloud reference material, see the Oracle Cloud SaaS documentation. For Oracle Fusion Cloud Time and Labor specifically, Oracle’s current documentation includes the 26A What’s New documentation and the implementation guidance for Time and Labor. The Oracle Fusion Cloud Time and Labor implementation guide is useful when ServiceNow workflows need to interact with Oracle HCM-related processes.