ServiceNow CIS-CSM Study Guide

Certified Implementation Specialist, Customer Service Management

Trademark disclaimer: ServiceNow, Now Platform, Now Create, and all related product and feature names are trademarks or registered trademarks of ServiceNow, Inc. This study guide is an independent, original work produced for exam preparation. It is not affiliated with, endorsed by, or sponsored by ServiceNow, Inc. No official exam content or copyrighted course material is reproduced here.

Exam shape: 60 scored questions, 130 minutes, multiple-choice (single answer) and multiple-select. The exam validates that you can scope, design, configure, and deploy a Customer Service Management implementation on the Now Platform. This guide is ordered by blueprint weight, spend your time proportionally.

#	Domain	Weight
2	CSM System Setup and Configuration	50%
4	CSM Portal, Knowledge, Catalog, Communities & PA	25%
3	CSM Integration	15%
1	Engagement Methodology and Project Planning	10%

Domain 2: CSM System Setup and Configuration (50%)

This is half the exam. If you master one domain, make it this one. It covers the customer data model, case management, assignment, roles, entitlements/SLAs, and the agent experience.

The customer data model: Account, Contact, Consumer

CSM extends the platform's Customer Service application with records that describe who you support. Three core record types anchor the data model:

Account: a company or organization you provide support to. Accounts can be hierarchical (parent/child) so a global enterprise and its subsidiaries are modeled as related records. Accounts can be subdivided into Business Units and child accounts for large customers. The Account is the B2B anchor.
Contact: an individual person who belongs to an Account. Contacts are the people you interact with in a B2B relationship. A Contact's underlying sys_user record is what logs in to the portal.
Consumer: an individual customer in a B2C model who has no associated company. Consumers are stored in the Consumer (csm_consumer) table and are the direct customer in business-to-consumer support.

Engagement models you must distinguish:

B2B (business-to-business): you support Accounts and their Contacts. Cases are tied to an Account.
B2C (business-to-consumer): you support Consumers directly; there is no Account/Contact layer.
B2B2C (business-to-business-to-consumer): a layered model where a business sells through to end consumers. The data model links a partner/seller Account, the products/assets sold, and the end Consumer, so you can support the consumer while still tracking the business relationship that delivered the product. This is the model to reach for when an enterprise serves consumers through partner organizations.

Related records that round out the model: Products and Product Models, Assets, Sold Products (what a customer purchased) and Install Base Items (what is installed or in use at the customer, linked to sold products through Installed Products), Partners (organizations that resell or service on your behalf), and Relationships between accounts/contacts.

Case management and case types

The Case (sn_customerservice_case) is the central work record in CSM: it represents a customer's request, question, issue, or complaint. The case lifecycle typically flows New → Open (Work in Progress) → Awaiting Info → Resolved → Closed, with states configurable per business need. Cases support Case Tasks for breaking work into assignable pieces.

Case types let you tailor forms, fields, flows, and behavior to different kinds of work. Out-of-box and configurable case types commonly include:

Standard / support case: the general issue or question.
Order case (Customer Service for Orders / Order Management): handles product orders and order-related issues.
Major case (Major Issue Management): used when a single root issue affects many customers. An agent proposes an existing case as a major case candidate; when a major issue manager or customer service manager approves it, a new major case is created and the original case becomes one of its child cases. Other affected cases are added as children, and updates such as comments, state, close notes and resolution code sync from the major case to them.
Case from interaction: created from an Interaction record (chat, phone, messaging) captured in the Agent/Configurable Workspace.

Create Case can be initiated by agents in the workspace, by customers in the portal, by email (Inbound Email Flows such as Create case from email; inbound email actions are the legacy method), and via integrations. Cases capture the Account, Contact/Consumer, Product, Asset/Install Base, Priority, Contact type/channel, and entitlement/contract context.

Advanced Work Assignment (AWA)

AWA automatically pushes work (cases, case tasks, chats, interactions) to the right agents based on availability, capacity, and skills, replacing manual queue cherry-picking. Core building blocks:

Service Channel: defines a type of work to be routed (e.g., a case channel, a chat channel). Each channel carries a work item capacity cost that consumes agent capacity.
Queue and routing conditions: each queue belongs to a service channel, and the queue's routing condition decides which work items enter it. The queue's Work Item Sort Order decides which pending item is assigned first.
Assignment rules: after an item is in a queue, the assignment rule (for example Most Capacity or Last Assigned, with skills and shifts) picks which eligible agent in the queue's groups receives it. Items not accepted or rejected within the timeout can be reassigned; AWA does not move work an agent has already accepted.
Agent capacity / Agent presence: each agent has a maximum capacity; presence states (Available, Busy, Offline) gate whether work is pushed. AWA only assigns to available agents who have remaining capacity.
Skills: skill-based routing matches required skills on the work item to skills on the agent.

Set up an AWA channel for cases/case tasks so work is auto-assigned rather than manually picked.

CSM roles

Roles control who can do what. The CSM-specific roles you must know (namespace sn_customerservice):

Agent (sn_customerservice_agent): internal service rep who works cases in the workspace.
Manager / ESM Agent / Senior Agent: supervisory roles that add reporting, escalation, and team management. Customer Service Manager (sn_customerservice_manager) oversees agents and teams.
Customer (sn_customerservice.customer): an external Contact who can log in to the Customer Service Portal, open and track cases for their Account, and use self-service. This is the standard external end-user role.
Customer Admin (sn_customerservice.customer_admin): a privileged external Contact who can manage other Contacts within their own Account (add/disable users, manage account info), i.e., delegated administration of their company's users in the portal.
Consumer (sn_customerservice.consumer) and Consumer Agent: for B2C support.
Partner (sn_customerservice.partner, partner_admin): for partner organizations in B2B2C/partner scenarios.

Key distinction for the exam: Customer = manage my own cases; Customer Admin = manage my company's other users; Agent = internal worker; Manager = internal supervisor. Never grant admin or itil to an external contact.

Entitlements, service contracts, and SLAs

CSM ties what support a customer is owed to the case:

Service Contract: the agreement between you and the customer defining the support they're entitled to (term, products covered, support hours).
Entitlement: defines the type of support and the supported channels (for example phone, chat, web), optionally with case or hour units. An entitlement is associated with an Account (or Consumer), Product, Asset or Contract. Contact is not an entitlement attribute, and entitlements do not select SLAs.
Entitlement calculation: when a case is created, CSM scores each candidate entitlement against the case's Account or Consumer, Product, Asset, Contract and channel (Contract weighs most; Sold Product and Install Base count when Proactive Customer Service Operations is active) and assigns the highest-scoring one.
SLA (Service Level Agreement): SLA definitions are attached to a service contract, a company or a product and attach to cases when their conditions match (conditions can reference the case's contract or entitlement). CSM uses the platform's SLA Definitions (Task SLA) with schedules/business hours; SLAs can pause (e.g., Awaiting Info) and breach.

Special Handling Notes

Special Handling Notes are configurable, condition-based alerts that surface important contextual instructions to agents at the right moment, for example, "VIP account, escalate immediately," "Do not contact after 6pm," or compliance warnings. They are tied to records (Account, Contact, Consumer, Product, etc.) or to records matching conditions, can be scheduled (effective dates), and display as a pop-up or a list in the workspace so agents see them before acting; agents can dismiss pop-up notes. They only display guidance: they do not enforce handling, restrict access or record an acknowledgment. They are a common exam topic because they're a CSM-specific way to guide agent behavior without code.

Agent experience: Configurable Workspace

The CSM Configurable Workspace (built on UI Builder / Next Experience) is the modern agent interface, succeeding the older Agent Workspace. Agents use it to work cases, run Playbooks, view the customer's information and history in Customer Central, launch interactions, and access guided processes. Know that the Configurable Workspace is the current recommended agent UI and that legacy Agent Workspace customers are guided to migrate to it.

Domain 4: CSM Portal, Knowledge, Catalog, Communities & PA (25%)

This domain covers the self-service side: where customers go, what they find, and how you measure it.

Customer Service Portal

The Customer Service Portal (Service Portal-based, csp / csm portal) is the external-facing site where Contacts, Consumers, and Customer Admins log in to:

create, view, and track cases;
search Knowledge and Communities;
order from the Service Catalog;
manage account/contact information (Customer Admin).

It is theme-able and configurable; pages are built from Service Portal widgets. Distinguish the customer-facing Customer Service Portal from the agent-facing Configurable Workspace.

Knowledge Management

CSM uses platform Knowledge Management: Knowledge Bases contain Knowledge Articles, governed by user criteria (who can read/contribute). For CSM:

Agents search and attach knowledge to cases and can create a knowledge article from a case (capturing the resolution for reuse).
Customers search knowledge in the portal for self-service / case deflection (resolving without opening a case).
Articles follow a workflow (draft → review → publish → retire) and support feedback/ratings.

Service Catalog for CSM

The Service Catalog lets customers request standardized products and services from the portal. In CSM, Catalog Items and Record Producers can create cases or orders; Order Guides bundle related items. Record Producers are the common way to generate a structured case from a catalog request with mapped variables. Catalog requests integrate with Request Management (REQ/RITM/SC_TASK) when fulfillment uses the request workflow.

Communities

Communities is a moderated, social self-service space where customers ask questions, share answers, and engage with experts and peers, increasing deflection and engagement. Concepts: forums/topics, questions and answers, upvotes/accepted answers, gamification (points/badges), moderation, and the Community Service Portal. Community content complements knowledge for self-service.

Performance Analytics (PA)

Performance Analytics provides indicators, scorecards, dashboards, and trend data to track CSM KPIs over time (case volume, resolution time, CSAT, SLA attainment, deflection). PA snapshots data on a schedule to show trends (distinct from real-time Reports). CSM ships with PA content packs/solutions for customer service metrics.

Domain 3: CSM Integration (15%)

CSM rarely stands alone. Know how cases connect to fulfillment, field work, and ITSM.

CSM + Field Service Management (FSM)

When resolving a case requires on-site work, CSM integrates with Field Service Management. From a case, an agent creates a Work Order (and Work Order Tasks); FSM dispatches and schedules technicians. The work order is related to the originating case and copies the case's account, contact and mapped fields when it is created; the two records do not synchronize automatically afterward. Activate the CSM-FSM integration to enable creating work orders from cases.

CSM + ITSM (Incident, Problem, Change, Request)

Incident: agents can create or relate an Incident when a customer-facing case stems from an internal IT issue; the case and incident stay linked.
Problem: recurring or root-cause issues escalate to Problem Management.
Change: fixes requiring a change link to Change Management.
Request Management: catalog-driven fulfillment uses REQ/RITM; CSM cases can spawn or relate to requests.

The pattern to remember: the case stays the customer's record of truth, while linked ITSM/FSM records handle the internal/field work, keeping the customer informed via the case.

Other integration concepts

Proactive Customer Service Operations: connects CSM to operational/ITOM signals (e.g., monitoring, service health) so you can detect issues and proactively notify affected customers or auto-create cases before they call. It ties service-aware data (often via CSDM) to customer impact.
Integration Hub / Flow Designer: used to orchestrate outbound/inbound integrations and automate case-to-fulfillment handoffs.
Email / inbound channels: Inbound Email Flows (Create case from email, Update case using Reply) create and update cases from email; inbound email actions are the older scripted method. Messaging and chat create interactions.

CSDM alignment

The Common Service Data Model (CSDM) is ServiceNow's prescriptive, standard way to model service data (services, applications, CIs) across the CMDB and product domains. For CSM, CSDM alignment matters because Proactive Customer Service and service-aware case management depend on cleanly modeled business/technical services and offerings mapped to customer-facing products. Aligning to CSDM is a design-time best practice that lets CSM relate cases to the right service and supports proactive operations.

Domain 1: Engagement Methodology and Project Planning (10%)

ServiceNow expects implementers to follow a prescribed delivery methodology and manage scope professionally.

Now Create (the ServiceNow implementation methodology, formerly the ServiceNow Implementation Methodology / SIM) breaks an engagement into five phases, Initiate → Plan → Execute → Deliver → Close, backed by reusable assets, accelerators, and leading practices.
Statement of Work (SOW): formally defines scope, deliverables, timeline, and boundaries the team commits to.
Design workshops: validate business requirements and confirm the future-state process with stakeholders before building. Requirements become user stories.
Scope / change control: any out-of-scope request must be impact-assessed (effort, timeline, risk, regression) and routed through the change control process for sponsor decision. Never silently absorb work (scope creep) or refuse without explanation.
Leading practices to reduce risk: engage stakeholders early; use out-of-box first before customizing; phase the rollout (MVP then iterate); validate with UAT; plan data migration and go-live readiness.

Fast-recall cheat list

Account = company (B2B). Contact = person at an account. Consumer = individual (B2C, no company).
B2B2C = business → partner/business → end consumer; links partner account, product/asset, and consumer.
Case = central CSM work record; Case Task = sub-work; Major Issue Management = one root issue, many affected customers: an approved candidate creates a new major case, with the original and other affected cases as children.
AWA: Service Channel (capacity cost) → Queue (routing condition decides entry, Work Item Sort Order decides order) → assignment rule picks an available agent by group/skills/capacity. Presence + capacity gate assignment.
Roles: agent (internal worker), manager (internal supervisor), customer (external, my cases), customer_admin (external, manage my company's users). Never give external users admin/itil.
Special Handling Notes = condition-based, record-tied agent guidance (pop-up or list) with effective dates; display only, no enforcement or acknowledgment record.
Entitlement = what support is owed (support type and channels), matched by account or consumer/product/asset/contract/channel (not contact). SLAs attach to a service contract, company or product through SLA conditions; entitlements do not select them. Service Contract = the agreement.
SLA = response/resolution timing via Task SLA + schedules; pauses on Awaiting Info.
Configurable Workspace = current agent UI (migrate off legacy Agent Workspace). Playbooks = guided processes inside it.
Customer Service Portal = external self-service (cases, knowledge, catalog, community). Communities = social Q&A self-service.
Knowledge: attach to case, create article from case; user criteria controls access; drives case deflection.
Catalog: Record Producer → creates a case; Order Guide bundles items; ties to Request Management.
PA = trended KPIs (indicators, scorecards, dashboards); snapshots over time, unlike real-time reports.
CSM + FSM = case → Work Order for on-site work. CSM + ITSM = case links to Incident/Problem/Change/Request; case stays customer's record of truth.
Proactive Customer Service Operations = service/ITOM signals → notify affected customers / auto-create cases before they call.
CSDM = standard service data model; align services/offerings so cases map to the right service and proactive ops work.
Now Create = ServiceNow delivery methodology (Initiate→Plan→Execute→Deliver→Close; hypercare sits in Close). SOW sets scope; change control governs out-of-scope requests.