Getting Started with Banking Service Management in Financial Services Operations

Nick Daigneau · 2 hours ago

Objective

Understand the value of Banking Service Management with Financial Services Operations and how the FSO data model helps banks clearly identify who they serve (customers, households, bankers), what financial products or services require support, and why customers are contacting the bank. This article also outlines key considerations for new Banking FSO implementations, including required plugins, deployment best practices, and essential enablement resources to help set your program up for success. Use this foundation to prepare for deeper functional and architectural deep dives in subsequent articles.

Overview

Banking Service Management is the foundation for delivering digitized, frictionless banking experiences on the ServiceNow platform. It provides the data architecture, workflow patterns, and pre-built capabilities that enable financial institutions to modernize their front, middle, and back-office operations on a single platform.

What is Banking Service Management?

Banking Service Management within FSO is a purpose-built solution built on top of Customer Service Management (CSM), extended with banking-specific capabilities, UX components, personas, data models, and workflows optimized for financial institutions.

Why Banking Service Management?

Benefit	Description
Unified customer service	Drive end-to-end resolutions across cards, payments, deposits, treasury, and more – connecting front, middle, and back offices with visibility and seamless handoffs
AI powered workflows	Powered by an AI-native platform and unified data, Generative / Agentic AI is embedded directly into workflows, accelerating resolutions and reducing operational costs
Omnichannel experiences	Provide consistent, personalized service across every channel – self-service, call center, or branch. Unify contact center workspaces with turnkey CCaaS integrations
Pre-built for banking	Go live in record time with pre-configured banking data models, integrations, workflows, and more
Low-code extensibility	Easy to operate, change, and maintain on a unified data architecture and code base leading to lower TCO. Adapt workflows, UI, integrations, and AI with declarative tools based on unique needs
Embedded compliance	Maintain consistent, auditable procedures across customer onboarding, service, and operations

Foundational Data Models: The Who, What, Why & How

Understanding the foundational data models is critical before beginning implementation. These models answer some fundamental questions: Who are we serving? What are the services or products they need help with? Why are they contacting us and how do we resolve their requests?

The "Who" – Customer & Service Relationships

Customer Data Foundations (CDF)

Customer Data Foundations answers the question: Who are we servicing externally? CDF provides the data structures to represent your customers based on your business model:

Accounts – Business customers in B2B relationships
Contacts – Individuals associated with business accounts (B2B)
Consumers – Individual customers in B2C relationships
Households – Groups of related consumers (B2C)

Learn more: Customer Data Management

Service Model Foundations (SMF)

Service Model Foundations extends beyond the customer to answer: Who else is involved in serving customers? SMF defines the broader ecosystem of people and organizations involved in service delivery:

Who can serve customers besides the contact center?

Service organizations – Any internal or external entity involved in providing a service in the support value chain (e.g. Branches, Regional locations, Areas)
Outsourced service providers – Business Process Outsourcer (BPOs) or vendors contracted to handle specific service functions
B2B2C and B2B2B relationships – Serving customers or businesses through an intermediary business partner
Partner Relationship Management (PRM) – Channel partners who help sell or distribute banking products, such as mortgage brokers or fintech resellers

In banking, SMF is particularly relevant for the customer facing personas such as the branch representatives, bankers, and advisors, including relationship managers, and wealth advisors who support customers outside the traditional contact center model.

Who do you serve internally that may have a customer impact?

Internal/External Locations – Physical sites like branches, offices, ATM locations, or service centers that require support and may affect customer experience
Organization members (B2E) – Employees who submit requests (e.g., a branch manager requesting system access or a loan officer raising a request on behalf of a customer) that ultimately affect customer service delivery

Learn more: Service Model Foundation Overview

The "What" – Products & Services

FSO Core Data Model

The FSO Core data model answers: What products and services do customers need support with? This banking-specific data model provides the foundation for representing the products customers hold, the services they consume, and the transactions they perform.

Financial Product Models – Define the catalog of banking products your institution offers (checking accounts, savings accounts, credit cards, loans, etc.). These serve as templates that describe product features, terms, and configurations
Financial Accounts – Represent the specific instances of products that customers hold. A Financial Account links a customer to a product and captures account-specific details like account numbers, balances, status, and ownership
Financial Services – Represent specific banking services enabled on a financial account, such as Remote Check Deposit (RDC) and Wire Transfer. These are particularly relevant for Treasury Management and commercial banking operations
Financial Transactions – Capture transaction-level data associated with financial accounts, providing agents with context when resolving disputes, inquiries, or fraud cases

Together, these components extend the platform's Sold Product model with banking-specific attributes, enabling agents to see the full picture of what a customer has and what they need help with.

Learn more: FSO Core Banking Tables | FSO Core Data Model

The "Why" and "How" – Case Management

Why Are Customers Contacting Us?

This is where Case Types and Service Definitions come into play. They categorize and define the reasons customers reach out:

Case Types – Extended case tables that represent specific categories of customer requests. FSO Banking applications ship with pre-built case types (e.g., Card Dispute, Payment Inquiry, Loan Servicing Request) that include banking-specific fields, workflows, and business logic. Case Types allow you to tailor the data model, UI, and process for each type of work
Service Definitions – Define the specific services available within each FSO application. Service Definitions connect the "what" (the service a customer needs) to the "how" (the case type and workflow used to fulfill it). They drive intake experiences like record producers and help categorize work for reporting and routing

Learn more: Case Types in FSO | Service Definitions in FSO

How Do We Resolve These Requests?

Resolution encompasses how work flows from intake to completion. This includes case and task management, process automation, AI-assisted resolution, and continuous improvement through analytics. There's much more to resolution than can be covered here – see the Implementation Planning: Key Considerations section below for a deeper look at Intake & Routing, Case Management & Work Execution, User Experience, and more.

Implementation Planning: Key Considerations

Before diving into configuration, consider these key areas. For more details on what areas to review, why you should be reviewing those areas, & how to get required inputs from the customer, see this article: FSO Solution Design Assessment (Coming Soon)

Intake & Routing: How are requests getting entered and assigned?
Case Management & Work Execution: How is work managed and resolved?
User Experience & People: How do users and customers engage with the system?
Security & Access: How do we control who can see and do what?
Architecture & Data Model: How do we structure data and integrate with existing systems?

Plugin Reference

Below is a reference list of key FSO Banking plugins for each of our applications. Install based on your implementation scope:

Application	App ID	Description
Dispute Rules Content Pack for Mastercard	sn_bom_mcard_cp	Embed auto-updated rules in your dispute processes.
Dispute Rules Content Pack for Nacha	sn_bom_nacha_cp	Compliance-ready toolkit for ACH dispute resolution
Dispute Rules Content Pack for Visa	sn_bom_visa_cp	Manage card disputes with data transparency and automation
Financial Services Business Deposit Operations	sn_bom_deposit_b2b	Create transparent and repeatable processes that save time and cost for business deposits
Financial Services Business Lifecycle	sn_bom_clo_b2b	Speed customer onboarding and effectively respond to changes during the business lifecycle, with built-in compliance
Financial Services Business Loan Operations	sn_bom_loan_b2b	Make better, faster loan servicing decisions with data-driven automation
Financial Services Card Operations	sn_bom_credit_card	Digitize card operations across the front, middle, and back office, inclusive of dispute management capabilities
Financial Services Client Lifecycle	sn_bom_clo_b2c	Speed client onboarding and effectively respond to changes with built-in compliance
Financial Services Complaint Management	sn_bom_compl	Prioritize and quickly resolve complaints in a consistent, controlled, and auditable way
Financial Services Operations Core	sn_bom	Core Financial Services data model used in Financial Services Operations
Financial Services Payment Operations	sn_bom_payment	Consolidate requests for payment operations and route them to appropriate teams across the middle and back office
Financial Services Personal Deposit Operations	sn_bom_deposit_b2c	Create transparent and repeatable processes that save time and cost for Retail Deposit Operations
Financial Services Personal Loan Operations	sn_bom_loan	Financial Services Personal Loan Operations workflows for customer requests
Financial Services Remote Tables	sn_bom_remote	Financial Services Operations Core Extension: Securely integrate systems with out-of-the-box Remote Tables
Financial Services Treasury Operations	sn_bom_treasury	Speed onboarding for treasury services with streamlined workflows and eliminate redundant requests for customer information with a single system of action
FSO Process Mining Content Pack	sn_bom_po	Process Optimization for Financial Services Operations
Intelligent Servicing for Fraud	sn_bom_fraud	Facilitate fraud resolution with connected technology and teams in a consistent, controlled, and auditable way
Performance Analytics Content Pack for FSO	sn_bom_pa	Anticipate trends, prioritize resources, and maximize automation and self-service with Performance Analytics for Financial Services Operations

Learn more: ServiceNow Store

Learning and Enablement Resources

Review the FSO Learning and Enablement Resources article for more information!

What's Next

Explore additional Banking Service Management capabilities:

Financial Services Operations (FSO) for Banking: Application Overview
Preparing a Banking Data Model (Coming Soon)
Building Custom Banking Applications (Coming Soon)

Get Involved:

Subscribe for updates on the FSO Community Forum
Review videos on our Financial Services Operations YouTube Playlist

Happy implementing! Comment below for questions, additional assets, or to share your Banking Service Management success stories.

Labels: Financial Services Operations, Banking, FSO, Implementation, Getting Started