ServiceNow Financial Services Australia

RACQ

IT Operations Automation

RACQ support depended on calls, emails, and brittle scripts, which slowed access provisioning, reduced self-service, and made onboarding work harder to govern.

166% Increase in self-service rate
400% Faster to provision account access
90% Of new hires with account access on day one

Reported impact

Business outcome

RACQ sped account provisioning by 400%, raised self-service from 30% to 80%, and ensured 90% of new hires had account access on day one.

  • Customer Experience
  • Productivity Improvement

Solution

RACQ support depended on calls, emails, and brittle scripts, which slowed access provisioning, reduced self-service, and made onboarding work harder to govern. RACQ implemented a ServiceNow-centered stack built around IT Service Management, Workflow Data Fabric, Virtual Agent, and Knowledge Base. Key components included IT Service Management standardizes incidents and requests; Workflow Data Fabric connects operational data and automation context; Virtual Agent handles conversational self-service; Knowledge Base stores reusable support content. The stack also connected PowerShell so the workflows could reuse existing records, documents, and collaboration channels instead of forcing teams back into manual handoffs. Requests enter through Virtual Agent, and uses context from Knowledge Base and PowerShell before IT Service Management and Workflow Data Fabric routes or fulfills the work. The same record of work is then exposed back to agents and end users through the platform.

Data flow

Requests enter through Virtual Agent, and uses context from Knowledge Base and PowerShell before IT Service Management and Workflow Data Fabric routes or fulfills the work. The same record of work is then exposed back to agents and end users through the platform.

Solution architecture

4 components · 3 layers
  1. Storage
    • Knowledge Base Stores reusable knowledge content that search and assistants reference during support.
  2. Serving
    • Virtual Agent Handles conversational self-service and ticket deflection for users.
  3. Orchestration
    • IT Service Management Standardizes incident, request, and fulfillment workflows on the platform.
    • Workflow Data Fabric Connects operational data across systems and powers automation with shared context.

Architecture clues

  • Knowledge content is reused as a source for self-service or AI-assisted answers.
  • Workflow Data Fabric is used as the shared context layer across multiple systems and workflows.

Evidence from the source

Automation drives consistency and service gains at RACQ 400% Faster to provision account access 166% Increase in self-service rate 90% Of new hires with account access on day one A drive for better staff and member experiences The Royal Automobile Club for Queensland (RACQ) is a member-based organization owned by over 1.7 million members
By using these capabilities, RACQ improved faster self-service
Zero-touch resolution for some requests also became possible, with users automatically added or removed from the Active Directory
“Now, with ServiceNow ITSM as a single interface between technology and business, we’ve managed to pivot to an 80% self-service rate.” Through continuous discussion and interactions with stakeholders, Matt and his team have also improved the way users log tickets, encouraging more employees to use the self-service portal as the first point of contact
“With manager input, a new hire would have a laptop and basic system access 90% of the time on their first day.” Another prior challenge for Matt and his team was having to review PowerShell scripts every six months to improve automation
Transparency Evidence & methodology 100/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 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
    3 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

    RACQ customer story

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