SERVICENOW CSM
Customer Service Management, modelled on how your customers are actually structured
CSM looks like ITSM with different labels. It is not. The hard part is the account model — who is entitled to what, which contacts can raise cases for which entities, and how that survives a customer reorganising.
What CSM covers
- Case Management
- Intake, routing, escalation, and case lifecycles that differ from incident because customers are not employees.
- Account & Contact Model
- B2B hierarchies, partner relationships, install base, and contact roles — the decisions that are expensive to change later.
- Entitlements & SLAs
- Service contracts, entitlement checking, and response commitments that match what your legal agreements actually promise.
- Customer Portal
- Self-service that reduces case volume rather than hiding the contact form, plus knowledge aimed at customers instead of at agents.
- Omni-channel
- Email, web, chat and messaging into one queue, with context that survives a channel switch.
- Field Service Management
- Work orders, scheduling, parts and dispatch, where the case leads to someone physically attending.
Your customers are not your employees
Case management looks like incident with different labels. The account and entitlement model is where CSM projects are actually won or lost.
WHERE IT GOES WRONG
What we see on CSM instances that stalled
- The account hierarchy was modelled wrong
One customer, several legal entities, shared contracts, and a contact who can raise cases for two of them but not the third. Getting this wrong is the most expensive mistake in CSM, because everything downstream references it.
- Entitlements do not match the contracts
The platform promises a four-hour response that the signed agreement does not, or vice versa. This surfaces during the first escalation, which is the worst possible moment.
- The portal was built for deflection, not resolution
Hiding the contact form increases frustration and case volume via other channels. Deflection works only when the self-service path genuinely resolves the request.
- CRM and CSM disagree about who the customer is
Two systems of record for accounts, no agreed direction of sync. Data reconciliation then becomes permanent operational overhead.
AI ON THIS MODULE
AI in CSM has a customer on the other end
The stakes are different here. An internal agent giving a poor answer is an annoyance; a customer-facing one is a commercial and sometimes contractual problem.
- Now Assist for Case
- Case summarisation and reply drafting for agents. Lowest-risk starting point because a human still sends it.
- Customer-facing agents
- Self-service that resolves. Entitlement-aware, so it must respect the account model and what each contract actually covers.
- Knowledge for customers
- A separate discipline from internal knowledge. Customer-facing articles need their own review cycle before AI reads them aloud.
- Escalation boundaries
- Defining exactly when an agent must hand to a person. The most important design decision in customer-facing AI.
Before you switch it on. We deploy AI agent-side before customer-side, without exception. Prove the answers are right where a human reviews them first.
How we approach CSM
Model accounts before anything else
We map your real commercial structure — including the awkward cases — and confirm it against contracts before configuring.
Make entitlements match reality
Read the actual service agreements, then implement those. Where they conflict with each other, we tell you.
Design the portal around the top ten reasons customers contact you
Everything else is secondary navigation.
Agree the CRM boundary in writing
One system owns the account record, the other consumes it, and the direction is documented.
CSM, asked and answered
Can we run CSM and ITSM on the same instance?
Yes, and most organisations should — but the data separation, roles and portal experiences need deliberate design so that customers and employees never see each other’s records.
Do we need Field Service Management?
Only if resolving cases involves someone travelling. It is a substantial module and worth scoping separately rather than bundling into a first CSM rollout.
How does CSM handle partners and resellers?
Through the account and partner model, with delegated access. It is one of the areas where modelling decisions made in week two constrain you for years, so it deserves the time.
NEXT STEP
Start with a 30-day platform review
One month, a fixed scope, and a written verdict on what your CSM implementation needs — which you keep whether or not you continue with us.