CSM Best Practices and Knowledge Management · Topic 1 of 2
Architecture, End to End Process and Project Scope
CIS-CSM best practices: single data model, instances and scoped apps, the customer service process from engage to close, and Now Create project scope.
- 5 min
- CSM shares one data model with the rest of the platform; the case table extends Task.
- Each customer has its own instances; build in development, promote to production.
- CSM is a scoped application, so its tables and roles use the sn_customerservice prefix.
What it is
Three ideas frame every CSM implementation. Architecture is the platform CSM runs on: one data model, separate instances per customer, and scoped applications. The end to end process is the path a customer issue takes from first contact to closure. Project scope is what the implementation delivers, and in what order, managed with ServiceNow's Now Create methodology.
The exam uses these to test judgment: which approach is the best practice for a given situation.
How it works
One platform, one data model
CSM is not a separate product with its own database. Cases, accounts, contacts, install base items, incidents, problems, changes and configuration items all live in the same instance database.
That shared model is why CSM connects to other teams without integration work:
- The CSM case table (sn_customerservice_case) extends Task, so cases share task fields such as assignment group, state and work notes, and they use the same SLA and notification engines.
- An agent can raise an incident, problem or change request from a case, and the case keeps the link.
- An install base item can point at a configuration item, so a service issue on a customer's product connects to operational data.
Instances
Each ServiceNow customer runs its own instances, each with its own application logic and database. A typical landscape has a production instance plus sub production instances for development and testing.
| Instance | Used for |
|---|---|
| Development | Building and configuring the CSM changes |
| Test | Testing with realistic data before release |
| Production | The live service customers and agents use |
Changes are built in development and promoted onward, never made first in production.
Scoped applications
CSM is delivered as a scoped application. A scope groups an application's tables, scripts and roles under one namespace, which is why CSM tables and roles carry the sn_customerservice prefix. Scoping protects the application from unrelated changes and keeps upgrades predictable.
The end to end customer service process
| Stage | What happens |
|---|---|
| Engage | The customer reaches out on a channel such as web, email, phone, chat or messaging, or the business detects an issue first. An interaction record captures a contact even when no case is needed |
| Create case | A case is opened for the account or consumer; entitlements show what support the customer receives |
| Route and assign | Assignment rules or Advanced Work Assignment send the case to the right agent |
| Investigate | The agent uses knowledge, case tasks, and if needed other teams through incidents, problems or changes |
| Resolve and close | The case moves to Resolved; the customer accepts the solution and the case reaches Closed, its final state |
| Measure and improve | Surveys and dashboards show performance; solutions become knowledge for next time |
Customer service runs in three styles. Self service lets customers help themselves in a portal. Assisted service puts an agent on the case. Proactive service contacts customers about an issue before they report it.
Defining project scope with Now Create
ServiceNow manages CSM implementation projects with the Now Create methodology. It sets out a standard project lifecycle in five phases: Initiate, Plan, Execute, Deliver and Close, with exit gates between them. Some partner material adds a Get Started step before Initiate.
Initiate confirms the roles, the project team and the kickoff. Plan turns the agreed scope into stories tracked in sprints.
Scoping is where an implementer earns trust. The best practice is to start from the base system and configure rather than customize, then release in phases.
Questions to settle while scoping a CSM project:
- Which business model applies: B2B, B2C or B2B2C?
- Where do account, contact, consumer and product data come from?
- Which channels and case types are in the first release?
- How are cases routed, and which entitlements and SLAs apply?
- Which other teams receive work from cases?
- Which portal, knowledge and reports do customers and managers need?
A typical first phase covers core case management on one or two channels; later phases add more channels, Advanced Work Assignment, playbooks or further portals.
How the exam asks about this
- "Agents must raise a problem record from a case without building an integration." This works because CSM and ITSM share one platform and data model, so the case links to the problem.
- "The customer wants every requested feature in the first release." Recommend a phased scope that starts close to the base system.
- "Which methodology does ServiceNow use to manage CSM implementation projects?" Now Create.
What to remember for the exam
- CSM shares one data model with the rest of the platform; the case table extends Task.
- Each customer has its own instances; build in development, promote to production.
- CSM is a scoped application, so its tables and roles use the sn_customerservice prefix.
- The process runs engage, case, route, investigate, resolve, close, then measure and improve.
- Closed is the final state of a case; an interaction can record a contact without a case.
- Now Create phases are Initiate, Plan, Execute, Deliver and Close.
Do not recommend heavy customization of base CSM tables and logic to match a legacy tool. Configure the base system first; customization raises upgrade effort.
Common mistakes
Treating CSM as a standalone tool. Because everything sits in one instance database, links to incidents, changes and configuration items are native. Proposing an integration between CSM and ITSM on the same instance is wrong.
Scoping everything up front. A big bang release delays value and adds risk. Phase the scope and let early releases prove the process.
Calling Resolved the end of the case. Resolved still waits for the customer to accept the solution. The case ends in Closed.
Check yourself
Why can a CSM case link to an incident without an integration?
CSM and ITSM run on the same platform and share one data model in the instance database, so the records relate natively.
What is the final state of a CSM case?
Closed, reached after the case is resolved and the solution is accepted.
Which methodology does ServiceNow use to run CSM implementation projects?
Now Create, with phases Initiate, Plan, Execute, Deliver and Close.
Topic 1 of 2 in CSM Best Practices and Knowledge Management
Test yourself on CSM Best Practices and Knowledge Management
The full ServiceNow CIS-CSM question bank has 590 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by ServiceNow. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.