ServiceNow Certified Implementation Specialist - Customer Service Management (CIS-CSM) (CIS-CSM) (CIS-CSM) — Questions 151–225

REST or SOAP Web Services APIs provide programmatic, bulk record creation into CSM tables, satisfying the legacy import requirement without manual entry. They support scheduled, repeatable loads and field mapping, making them a valid import method alongside import sets and templates.

The Case form's Escalate UI action lets an agent escalate a record on demand, satisfying the requirement for a manual escalation method. This gives human judgement a path alongside automated triggers, and the action typically sets the escalation state and notifies the assigned escalation group.

Flagging or submitting feedback marks the article as outdated without requiring author rights, routing it to knowledge managers for review. This satisfies the scenario where an agent identifies stale content but may lack permissions to edit the published article directly.

Task SLA [task_sla] records each SLA instance against a task, storing the stage, breach time and duration fields needed to calculate averages. Because tasks carry the Account reference, grouping resolution-stage records by Account yields the average Resolution SLA duration the manager requires.

Similarity search in ServiceNow Communities analyzes the text of a new question and compares it to existing discussions, presenting similar threads in real time. This helps users find answers without creating duplicates. It uses natural language processing and can be enabled in community settings. This is the intended feature to reduce fragmentation by suggesting relevant existing content as the user types.

Flagging an article as 'Not Helpful' on the Customer Service Portal automatically creates a Knowledge Feedback Task, which routes to the assigned knowledge owner for review. This satisfies the default behaviour requirement without custom configuration, since the portal feedback action maps directly to that task type.

Related Lists on the Case form expose the Account's associated Cases through the native relationship, letting the agent view every historical case submitted by that account without leaving the record. This satisfies the requirement to see the relationship natively, as the Cases related list is populated automatically by the Account lookup.

The Account hierarchy related list stores the parent-child linkage between the global enterprise account and each subsidiary, so CSM can roll up cases, entitlements and contacts. It directly satisfies the stem's requirement for multiple subsidiaries reporting to one global account.

The 'Create Case' moderation action converts a community thread into a formal case while preserving the discussion context and origin. This satisfies the requirement for specialised backend engineering support by routing the unresolved question into the CSM case workflow, where assignment rules and escalation paths reach engineering teams that community moderation alone cannot engage.

Guided Decisions present agents with a branching decision tree tailored to a specific case type, steering them through diagnostic questions and recommended actions. This standardises handling and reduces reliance on agent judgement for repeatable scenarios.

Case state transitions are driven by business rules, which execute on create and update to set status, assignment, and routing. If a rule's condition or action is misconfigured or inactive, the case stays in New even after an owner is assigned.

Customer relationships define connections between accounts, such as partner-to-customer links.

Accounts model organisations and therefore support multiple linked contacts, each with their own roles and relationships. Consumers are individual end users with a single record and no contact hierarchy, matching the stem's requirement to distinguish the two entity types in CSM data modelling.

Additional comments are customer-visible by default. They appear on the customer service portal and in notifications sent to the customer. This field is specifically designed for communication with the customer, ensuring transparency. Thus, it is the correct choice for a comment that should be seen by the customer.

The Pause condition is designed to temporarily halt the SLA timer without ending the SLA. By pausing when the case enters Awaiting Customer or Awaiting Problem states, the timer stops counting during those periods and resumes when the case leaves those states. The Stop condition on Closed correctly ends the SLA when the case is resolved and closed.

Reputation points and badges are the native ServiceNow Communities features for gamified recognition. Points can be awarded for actions such as having an answer accepted, and badges can be automatically granted when a user reaches a point threshold. This directly fulfills the requirement to award points and grant a badge at 100 points.

The Account Tier field on the Account record stores the tier classification, letting portal routing rules identify tier-one accounts and prioritise their contacts on login. Recording tier elsewhere would not drive the required entitlement-based handling.

Deflection Tracking with Search Analytics feedback records portal searches and article views that end without case creation, attributing each deflection to the knowledge consumed. This supplies the exact count of cases avoided through portal article viewing that the manager needs.

Assignment rules route incoming cases to queues or users based on conditions such as case origin, so cases created via Email are directed automatically to the specialised team. This satisfies the manager's requirement for automatic assignment without manual intervention, unlike manual routing or workflows that lack native assignment-rule targeting.

ServiceNow supports many-to-many contact-account associations through contact relationships and the contact-account mapping table, so one individual can serve several organisations. This satisfies the stem's requirement for a true statement about account-contact relationships, since the model is not restricted to a single account per contact.

Portal case submission requires the contact's user account to hold the appropriate portal roles, such as sn_customerservice.customer, which grant create access on the Case table. This satisfies the stem's condition that the contact possesses the necessary portal user roles.

In ServiceNow communities, moderators can use the 'Hide' action or set a post's visibility to 'Private' to temporarily remove it from public view while still allowing the author to see it. This action is reversible and supports investigation, as the post remains in the system and the author can receive feedback. It precisely meets the scenario's requirements.

The 'Create Knowledge' UI action on the community question record copies the thread's question and accepted answer into a new knowledge article draft. This satisfies the requirement to convert a resolved community thread into an official knowledge base article.

Workflow Notification activities fire on SLA stage transitions, such as entering an escalated or breached stage, sending alerts before the breach completes. This uses the workflow engine's stage-driven triggers, satisfying the requirement to notify stakeholders ahead of an SLA breach.

User Criteria records define the conditions—such as role, group membership or company—that gate portal case creation, and the system evaluates them against the requesting user before granting access. This directly satisfies the stem's requirement to determine whether a user may create a case on the Customer Service Portal.

State Model Definitions hold the permitted transitions between case states, so restricting 'New' from jumping directly to 'Closed' is enforced there. Other configuration areas govern fields, SLAs or UI behaviour, not the allowed state-to-state movement.

Advanced Work Assignment routes cases automatically to available agents using service channels, capacity and assignment rules, pushing work rather than relying on manual picking. It is a supported assignment method, satisfying the requirement for automated, skills-based case distribution.

AI Search search profile configurations and search sources control ranking, boosting and content selection, directly improving relevancy so outdated, low-quality community posts rank lower. This satisfies the stem's requirement to surface fresher, higher-quality results through administrator-configurable search behaviour.

The SLA engine evaluates Pause and Resume conditions against the task record to temporarily stop the timer without ending the SLA. Setting Pause to the 'Awaiting Customer' state and Resume to any other state causes the timer to hold while waiting on the customer and restart when the case is no longer in that state, preserving elapsed time toward breach.

Deleting or editing inappropriate posts directly enforces forum content standards, satisfying the requirement to maintain order and quality. Moderators hold this editorial privilege within community platforms, letting them remove spam, abuse or off-topic material before it disrupts peer-to-peer support. This is a core moderation capability, distinct from administrative configuration tasks.

The SLA Definition record's Schedule field references a schedule record containing the business hours and time zone. Attaching that schedule makes duration calculation count only defined business hours instead of continuous 24x7 time, satisfying the business-hours constraint.

Applying a Case Template copies its predefined field values onto the case record, pre-populating attributes such as priority, category and description. This satisfies the stem by automating data entry at creation, reducing manual effort and enforcing consistent case structure across records.

A Reference variable pointing to Account or Contact stores a true relationship rather than free text, enabling lookups, validation, and downstream reporting against existing customer records. This satisfies the best-practice requirement for capturing accurate Customer information on the record producer.

Creating a distinct account for each division and assigning Contoso as the Parent builds a standard account hierarchy. Each division can then hold its own contacts, contracts, and entitlements for independent case tracking, while the Parent reference lets reporting and roll-up logic aggregate division activity up to Contoso without duplicating records or custom fields.

The Start condition determines when the SLA attaches to a task. By adding a condition to exclude cases where the case type is 'Internal', the SLA engine will not attach the SLA to those cases at all. This is the correct approach because the Start condition is evaluated when the task is created or updated, and if it evaluates to false, no SLA instance is created.

The Customer Relationship table is specifically designed to model many-to-many relationships between contacts and accounts. By creating a record in this table for each account the contact is associated with, the administrator enables the same contact to be linked to multiple companies without duplicating the contact record.

The SLA engine generates Task SLA records with calculated start, pause, stop and breach times, drives stage progression, and attaches the workflow. Inserting records manually bypasses that schedule calculation and stage logic, leaving SLAs that never transition or trigger correctly.

Problem records consolidate many related cases under one root cause, so a single investigation and fix resolves numerous customer incidents. This many-to-one linkage is the core benefit, reducing duplicate troubleshooting and preventing engineers from treating each case as an isolated defect.

SLA Definitions contain the workflow conditions and target durations applied to cases. Configuring a condition on priority equals High with an eight-hour resolution target satisfies the requirement irrespective of account tier, since SLA conditions override tier-based defaults.

Script-based User Criteria execute on every community page load, so heavy or uncached scripts create the performance bottleneck described. Keeping scripts lightweight and caching results satisfies the stem's constraint of optimising script-based User Criteria to restore acceptable forum performance.

Reassigning the case to the correct group routes it to the team with the appropriate expertise and ownership, restoring proper handling. This preserves the customer's case history and SLA tracking rather than closing or duplicating the record.

When an article is checked out, it is locked to that author. Other users cannot check it out until the first author checks it in or an administrator cancels the checkout. This prevents conflicting edits and preserves version integrity. The second author may see that the article is checked out and can request the first author to check it in, but cannot proceed themselves.

The Create Child Case UI action on the Case form generates a new case linked via parent-child relationship, copying account and product details from the parent. This satisfies the stem's requirement for a standard UI action producing an inheriting follow-up case.

Child cases inherit state changes through the Major Case Management configuration properties, which define the propagation behaviour between the primary case and its children. This satisfies the stem's constraint that a state change on the primary Major Case must cascade to child cases, rather than leaving them unchanged or requiring manual updates.

Promotion detaches the child from its existing major case hierarchy, so it becomes a standalone major case rather than remaining nested beneath its former parent. This satisfies the scenario's requirement that promoting a child case alters its hierarchical position within Major Case Management.

The Knowledge Base record's Workflow field binds an article workflow to that base, so every article created within 'Customer Support' inherits the approval cycle before publication. Configuring it there enforces the Knowledge Manager approval the stem requires.

Customers can add comments to their cases through the portal, which posts to the case activity stream and notifies the assigned agent. This is a supported customer interaction, satisfying the requirement for portal-based case communication.

The knowledge article workflow controls state transitions. To enforce approval before publishing, the workflow must include an approval activity in the Review state, assigned to the knowledge manager. When an article enters Review, the approval activity triggers, and the article cannot move to Published until approved. This directly meets the requirement by gating publication on manager approval.

Installed Base items (assets) carry an Account reference, tying each customer's deployed products to their account record. This direct association supports entitlement checks and case resolution, satisfying the stem's requirement for record types linked to an Account.

Contextual Search in ServiceNow CSM uses the text entered in the short description field to search knowledge bases and display relevant articles in real time. It is designed to deflect cases by offering solutions as the user types. By enabling Contextual Search on the Customer Service Portal, the knowledge manager can provide immediate article suggestions, enhancing self-service and reducing case creation.

SLA definitions can reference case category or subcategory as a condition, letting organisations apply distinct service levels by issue type. This makes category hierarchies meaningful beyond reporting, directly supporting differentiated response and resolution targets per category.

A Service Contract groups entitlements and coverage terms for an account, defining what support a customer receives and when. It satisfies the stem's requirement by acting as the container that binds entitlements to an account, enabling CSM to validate coverage during case creation and enforce service-level commitments.

Case Matching Rules in CSM automatically compare fields on new cases with existing open cases to detect duplicates or related issues. By defining match criteria on fields like Customer and Product, the system creates a relationship between the new case and any matching open cases. This is exactly what the manager needs to link cases automatically.

User Criteria referencing the Company field, or a script evaluating entitlement records, restricts article visibility to contacts whose company holds the Premium Support contract. This satisfies the requirement to enforce contract-based access rather than open portal access.

Translation Management links the translated article to the source as a separate record, so publishing the translation leaves the source article's workflow state untouched and still published, satisfying the requirement that the original remains live.

Deactivating the linked sys_user record sets Active to false, which invalidates the contact's portal authentication and terminates existing sessions, because portal login checks the underlying user account's active state rather than the contact record alone.

A Flow Designer flow triggered on the Contact table fires when a contact is created, and can conditionally generate an approval task for the account manager. This satisfies the requirement for automatic approval generation on strategic-account contacts.

The question author owns the thread and can mark any reply as the Accepted Answer, while designated community moderators hold override rights to mark or change it when the author is inactive or the thread needs curation. This satisfies the stem's requirement that both parties share that authority.

Associating the Search Context with the Workspace Search Config or Table Configuration wires the context into the agent workspace, so suggested articles surface against the record being viewed. Without this binding, the context never activates for agents.

The task_sla table stores per-task SLA records, so it exposes actual elapsed runtime against defined targets, breach occurrences, and the resulting compliance percentage. That directly satisfies the stem's demand for metrics covering durations, breach counts, and compliance, which no configuration or definition table provides.

The sn_communities_moderator role grants the exact permissions the stem requires: moderating posts, approving pending content, and managing reported items within Communities. It satisfies the constraint of a single role covering all three moderation duties, unlike broader admin roles that would over-provision access.

Locking a community thread blocks new replies while leaving all existing posts visible and readable. This is the standard moderation action for halting further discussion without deleting content, satisfying the scenario's requirement to stop contributions while preserving the thread.

Escalating a case writes to the case record's Escalation field, recording that the case has been raised. This satisfies the scenario's requirement to reflect escalation status on the case itself, rather than merely notifying a queue or reassigning ownership.

The community content state lifecycle moves posts through Draft, Pending Approval and Published, satisfying the requirement that a managing editor approves content before it goes live. The Pending Approval state blocks publication until the editor acts.

The Target field determines which SLA timer the definition governs, such as Resolution or Response, and sets the metric objective type the engine evaluates. Setting it to Resolution means the definition only attaches to resolution-based timers.

The 'Additional comments' field exists to communicate directly with the customer, satisfying the requirement to convey supplementary information alongside the record. Unlike internal work notes, which stay within the assignment group, this field is customer-visible, making it the correct channel for outward-facing updates.

The Schedule field on an SLA Definition references a business schedule that defines working hours and holidays. The SLA engine uses that schedule to calculate business elapsed time, so only time within the contracted support hours counts toward the SLA target. This directly satisfies the requirement to exclude nights, weekends, and holidays.

Account hierarchy lets the case reference the subsidiary as the account while the entitlement resolves through the parent's contract. Setting Account to the subsidiary and choosing a parent-linked entitlement satisfies the requirement to bill the parent corporation.

Community badges can be configured with specific criteria, such as the number of helpful answers a user has provided. By setting the badge criteria to require at least five helpful answers, the system automatically awards the badge when the threshold is met. This is the intended feature for recognizing user achievements based on contribution metrics.

The Table field is mandatory because an SLA Definition must bind to a specific task table, such as the Case table, to know which records it evaluates. Without this target, the SLA engine cannot attach conditions or schedules, so ServiceNow blocks saving the definition until a table is selected.

The customer_account table underpins the account-based service model, acting as the primary container that groups business customers and their related contacts, cases and entitlements. Unlike consumer records, accounts represent organisations, so this table satisfies the stem's requirement for the organisational container in ServiceNow CSM.

The Account record includes a Contacts related list that shows all contacts associated with that account. This allows the agent to quickly view and access other contacts, such as subject matter experts, without leaving the account context. It is the standard and efficient way to see all contacts for an account.

Average response time and resolution rate for unanswered questions measure how quickly community members engage and resolve queries, indicating deflection effectiveness. This satisfies the stem's requirement for a community performance metric reviewed by the director.

Logical categorisation directly enables case deflection by letting users self-serve answers before submitting a ticket. Clear forum structure reduces search friction, so members locate existing solutions rather than raising duplicate cases. This satisfies the stem's deflection constraint, since discoverability determines whether peer content is actually reused. Poor navigation forces escalation, defeating the community's purpose.

Short Description and Description map directly onto the article's own equivalent fields, so ServiceNow copies them automatically when an agent creates a knowledge article from a case. This satisfies the stem's default-copy constraint without requiring manual entry or additional configuration.