[object Object]

The CSM project lifted the ITSM data model wholesale, which made the demo work and the production rollout collapse on the second account merger. Customer Service Management on ServiceNow is genuinely strong; treating it as ITSM-with-customers-instead-of-employees is the most reliable way to get six months in before the data-model rebuild becomes unavoidable.

ITSM vs CSM

ITSM serves employees with a model rooted in incident, request, and change against internal CIs. CSM serves customers with a model rooted in case, work order, and asset against external entities (Account, Contact, Consumer, Product). Different data models, different portals, different SLAs, different escalation patterns. Install both if you have both audiences; lifting one to serve the other shape produces an unmaintainable hybrid.

Contact, Account, Consumer

CSM’s identity model is the foundation. A Contact belongs to one or more Accounts in B2B; a Consumer is an individual customer with no account context in B2C. Cases attach to a Contact and either an Account (B2B) or directly to the Consumer (B2C). Getting the data model right up front prevents years of mess — Contacts created without Account links, duplicate Contacts on every email change, Consumer records used as a workaround when the proper Contact-plus-Account pattern was needed.

CSM identity entities:
  Account (organization-level, B2B)
  Contact (person, may belong to multiple Accounts)
  Consumer (person, B2C, no Account)
  Asset (product instance owned by Account or Consumer)
  Entitlement (service level applicable to Asset)

Omnichannel Routing

Cases come in via email, chat, phone, portal, social, and self-service. Omnichannel routing puts them in one queue and routes by skill, availability, priority, and customer entitlement. The Matchmaker engine handles the match using rules you configure; the default rules are reasonable starting points and need tuning per industry. Skill-based routing requires a maintained skill catalog (see the related Skill-Based Assignment article); without it, omnichannel degrades to round-robin.

// Route case based on entitlement and skill
function routeCase(caseSysId) {
  var caseRec = new GlideRecord('sn_customerservice_case');
  caseRec.get(caseSysId);
  var entitlement = getActiveEntitlement(caseRec.account, caseRec.product);
  var skills = getRequiredSkills(caseRec.category, caseRec.subcategory);
  return matchmaker.findBestAgent({
    entitlement_tier: entitlement.tier,
    required_skills: skills,
    availability: 'on_shift'
  });
}

Field Service Integration

CSM integrates with ServiceNow Field Service Management for on-site work — case generates work order, work order dispatches a technician with the right skills and parts, technician completes work and the resolution flows back to the case. Worth the integration cost if on-site service is part of your model; overkill if field work is rare. The integration handles parts inventory, dispatch optimization, and customer scheduling without bolt-on integrations.

Self-Service First

Customer portal with knowledge plus community plus chat deflection. Every case deflected is a case your agents did not handle and a customer who got an answer faster. Measure deflection rate weekly — searches that resolved in a knowledge article, conversations that resolved in Virtual Agent, community posts that received accepted answers. The deflection number compounds with knowledge base quality; investing in articles is the highest-leverage CSM improvement after the data model is right.

Common Failure Modes

Contact records created from inbound email without Account linkage — Contacts pile up unattached and reporting by Account misses cases. Build the inbound flow to look up the Account from the email domain or prompt the agent to attach. Entitlements modeled at the Account level only — service tiers vary per Product or per Contract; model at the right grain. Cases auto-closed by aging policy without customer confirmation — destroys CSAT; require explicit closure or use a soft-close with reopening window.

What Changed in 2026

CSM gained Now Assist surfaces specific to customer service — case summarization, suggested responses ranked by historical success, draft email composition. The Zurich release added Agentic AI flows for high-volume case categories (return requests, status inquiries) on Enterprise Plus. The customer-facing surfaces (portal chat, Virtual Agent) gained multi-turn context retention.

Implementation Sequence

Validate the identity model first — Account, Contact, Consumer relationships against your actual customer base. Build the inbound flows next. Add omnichannel routing once the queue is stable on email-only. Layer in field service integration if applicable. Do not enable AI features until the underlying data model and routing work cleanly; AI on a broken foundation produces confidently-wrong responses faster.

What to do this week: pull the count of Contacts without Account links and the count of duplicate Contacts (matching email or matching name plus phone) — those two numbers are your data model debt baseline.

[object Object]
Share