ServiceNow Certified Implementation Specialist - Customer Service Management (CIS-CSM) (CIS-CSM) (CIS-CSM) — Questions 1–75

AI Search applies semantic and lexical correction, automatically fixing misspellings and mapping synonyms so queries still return relevant Knowledge articles. Legacy Text Search requires exact token matches, so typos or alternate wording fail. This satisfies the scenario's demand for capabilities beyond legacy Text Search.

The Consumer Service Portal ships with a household data model that links consumers through defined member relationships, letting agents view and manage family or household groupings without custom development. This out-of-the-box capability satisfies the stem's requirement for features provided natively, rather than requiring configuration or plugins.

Major Case Workbench supplies the dedicated workspace where agents triage, track and resolve high-severity cases, satisfying the stem's requirement for a Major Case Management plugin capability. It centralises case records, tasks and timelines, letting service teams coordinate complex incidents beyond standard incident handling.

Communication Plans in Major Case Management define stakeholder notification rules triggered by case events. When a major case is proposed, the plan automatically invites the relevant stakeholders to the meeting, satisfying the requirement for automatic, event-driven invitations without manual intervention.

On a case record, the Related Links section provides the Attach Knowledge action, letting the agent search the knowledge base and link an article directly to the case. This satisfies the requirement to attach a Knowledge article for customer assistance.

The sn_customerservice.customer role grants portal users self-service rights over their own profile and cases, satisfying the stem's minimum-privilege constraint. It scopes access to records the user owns, unlike agent or admin roles, which carry broader case-management permissions beyond what self-service requires.

Reaching the breach threshold triggers the SLA engine to write 'Breached' into the Task SLA record's Stage field, satisfying the automatic state transition the question demands. Stage is the engine-managed lifecycle value, so no user action is needed for this update to occur.

Community badges in ServiceNow CSM can be configured with criteria that automatically award the badge when a user meets specific conditions, such as accumulating a certain number of 'Helpful' votes on their posts. This feature directly supports automated recognition based on user achievements, making it the correct choice for this scenario.

On re-opening, the SLA engine re-evaluates start conditions; if they are met again, it creates a fresh Task SLA instance rather than resuming the prior one. This satisfies the stem's scenario by generating new SLA tracking for the reopened Case.

Matching multiple accounts leaves the case's customer field unpopulated, or flags it for manual agent review, because CSM cannot safely infer a single account from an ambiguous domain. This satisfies the stem's default behaviour constraint: resolution requires a unique match, so ambiguity defers to the agent rather than guessing.

The Service Portal provides the primary self-service channel for CSM case creation, letting customers submit requests directly through configurable catalogue items and record producers. This satisfies the stem's requirement for a primary channel, as portal submissions generate cases automatically without agent intervention, unlike secondary methods such as email or phone.

Each translated article carries its own workflow state, so a translation can be reviewed, approved and published independently of its source. This lets regional teams release localised content on separate schedules while the original remains unchanged, matching the multilingual CSM scenario.

When no schedule is set on the SLA Definition, the engine treats all calendar time as working time, effectively a 24x7 schedule. This means weekends and holidays count toward breach. Implementers must explicitly attach a schedule when business hours should be honored, otherwise targets are measured in calendar time.

Peer-to-peer forums let customers surface answers from fellow users, so recurring questions resolve without agent involvement. That directly satisfies the deflection constraint in the stem: reducing inbound case volume by shifting resolution to the community, rather than relying on internal knowledge articles or live agent assistance.

The Account Contact relationship lets one contact link to multiple accounts, so the existing user contact can be associated with the new account without duplication. This satisfies the scenario while preserving the contact's existing account linkage.

User Criteria in ServiceNow Knowledge Management allows administrators to define conditions based on user attributes, including company and product associations, to control which articles are visible. By setting up user criteria that reference the user's company or product entitlements, the specialist can ensure agents only see articles relevant to their assigned accounts and products. This is the correct mechanism for restricting article visibility dynamically.

Task SLAs are attached to the Case as related records, and the Task SLA related list on the Case form displays each SLA's stage, elapsed percentage and breach timers in real time, letting the agent monitor active commitments without leaving the record.

SLA Definition records hold the schedule, conditions and workflow that enforce resolution targets, and its pause condition and target fields calculate the time allowed against case priority. This satisfies the stem's requirement for the record type defining resolution time per priority, rather than the task-level SLA or entitlement records.

Reassigning the case changes the Assigned to field to the other agent, preserving all case history, activities, and related records. This is the standard way to transfer ownership while maintaining continuity. The case remains the same record, so all information is retained.

Entitlements are fundamentally tied to customer accounts.

Matching rules evaluate agent skills, capacity and other criteria to determine which agents qualify for a work item. Without them AWA cannot select a suitable agent, so they are mandatory for routing cases to available agents.

Script-based User Criteria lets you evaluate account or entitlement fields dynamically, so only users whose account matches the specified customer accounts pass the check. This satisfies the constraint of restricting a knowledge base to specific customer accounts rather than broad audience segments.

The 'Create Case from Question' UI action must be configured to appear on community question records for users with the necessary roles, such as customer service agents. This UI action provides the mechanism to generate a case directly from a question, pre-populating relevant fields. Without this configuration, agents would not have the button available to perform the action.

The Schedule field on the SLA Definition record accepts a predefined business schedule, letting the SLA inherit that schedule's time zone and working hours. This satisfies the stem by applying a custom schedule without writing code or creating a schedule source.

Assignment Rules execute as business rules on the case table, firing when a record is inserted or updated. This trigger point means routing logic evaluates whenever a case is created or its fields change, satisfying the stem's question about when rules run.

Task SLA [task_sla] is the default table storing both active and historical SLA instances attached to customer service cases, satisfying the requirement for a single table covering current and past records. Case SLAs are task-based, so their instances reside here rather than in the contract_sla definition table.

A custom business rule that inserts Task SLA records directly duplicates the work of the SLA background engine, which already evaluates SLA Definitions and attaches SLAs. Both paths create separate Task SLA records for the same case, producing duplicate attachments.

A Notification configured on the kb_feedback table with a Rating less than or equal to 2 condition triggers automatically when feedback is submitted. This directly satisfies the requirement to notify the article author on low ratings.

Account related lists surface every case record linked to that account through the lookup relationship, giving a consolidated view without building custom reports or filtering the full case list. This directly satisfies the requirement to view all cases associated with one specific account.

Tagging assigns keywords to discussions, and following a tag subscribes users to every future item carrying it. This pushes relevant threads into their feeds, satisfying the requirement to discover discussions without manually browsing each forum.

The History context menu on the kb_knowledge record exposes field-level audit entries showing who changed which field and when. This satisfies the lifecycle audit requirement, since ServiceNow writes these records automatically to the audit table whenever the article is edited.

Case deflection rate measures how many would-be cases were resolved through community search and content instead of agent-handled tickets. Tracking it satisfies the stem by quantifying community self-service success, showing whether published knowledge actually reduces inbound case volume.

The Task SLAs related list surfaces attached SLA records and their stage and remaining time directly on the task form, while the workspace SLA component renders the same countdown data in CSM Workspace. Both display live SLA timers without custom portal code.

Priority is a configurable field within a case template, letting agents classify severity consistently at case creation. Templates pre-populate such fields so every case captures the same structured attributes, satisfying the stem's requirement for items that can be included in a Case Template.

Routing a negative feedback task to the article's author satisfies the ownership constraint: the author holds the subject-matter expertise and edit rights needed to revise the flagged content. ServiceNow's knowledge feedback engine resolves assignment from the article record's author field, so the person who created the specific article receives the task.

The Task SLA table tracks the actual progress, stage, and breach status for each task instance.

Selecting 'Propagate updates' copies work notes and comments from the parent problem record down to all linked child cases. This keeps case agents informed of problem investigation progress without manual re-entry, satisfying the requirement to synchronise updates across related cases.

Contextual Search Contexts bind search sources to case fields, and Search Criterias apply conditional filters so agents default to the product-specific knowledge base matching the case's product. This satisfies the requirement to scope searches per product line automatically.

After an agent completes work and the case is ready for closure, its state becomes Resolved. This is the terminal working state that precedes Closed, distinguishing it from New, In Progress, or Escalated, and it matches the stem's condition of work being finished.

SLA stages are stored as records in the SLA Stages [sla_stage] table and referenced by the stage choice field on Task SLA records. Modifying display therefore means editing those stage definitions or the choice list, which is where CSM case SLA stage presentation originates.

Case Audit history records every field change made to a case, satisfying the requirement for a read-only, tamper-evident log. It captures who changed what and when, supporting compliance and troubleshooting without permitting edits to the recorded entries.

Feedback submitted against an article creates a feedback record and, where configured, a feedback task; both appear in the related lists on the article form. This satisfies the requirement to see the Outdated flag raised by a customer.

Contextual Search Sources are the configuration records that map external repositories, such as SharePoint, into CSM search. Defining one registers the connector and its search profile, so agents see external knowledge results during case creation, satisfying the requirement to search beyond ServiceNow articles.

Custom widget failures stem from JavaScript errors or unresolved widget dependencies, both surfaced in the Service Portal Widget logs and the browser console. These are the only places exposing client-side script exceptions and dependency-loading faults, directly satisfying the requirement to diagnose why customised widgets stop rendering after upgrade.

Peer answers in forums resolve common questions before a case is raised, deflecting inbound case volume. This satisfies the stem's constraint of integrating forums with CSM cases by reducing the number of formal cases reaching agents.

Creating a child case preserves the parent case's active state while spawning a linked record for the back-office team, so the original interaction context and history remain intact. This satisfies the stem's requirement to escalate without closing or losing the current case, unlike transferring or reassigning, which would move ownership away from the agent.

Hierarchical categories within each Knowledge Base provide a structured taxonomy for classifying articles, satisfying the requirement to categorise knowledge articles. Categories nest under a Knowledge Base, enabling browsing and filtering by topic. This is a native ServiceNow Knowledge Management categorisation method, distinct from article metadata such as keywords or article types.

The Retroactive field makes the SLA engine calculate elapsed time from the exact moment the Case was created, even when the SLA definition was authored afterwards. Without it, timing begins only when the SLA is attached, so the stem's backdated-start requirement fails.

Reassigning a case to another team transfers ownership within the ServiceNow case record, updating the assignment group field so the receiving team's queue reflects the work. This satisfies the stem's requirement that a manager perform the action, since assignment group changes are governed by manager-level role permissions rather than requester access.

The 'Can contribute' field on a knowledge base accepts user criteria, which defines who can create and edit articles. By creating user criteria that includes only the knowledge_admin role and applying it, only those users can contribute, while others can still read published articles if read criteria allow. This precisely meets the requirement.

Search Contexts define the conditions, such as Product and Category, that map a case to a specific knowledge base for Contextual Search. Configuring the matching rule there satisfies the requirement to auto-suggest articles from a designated knowledge base.

Recent activity feeds and top contributor leaderboards are widget components configurable within the Community Home page layout, satisfying the stem's customisation requirement. Service Portal Designer and UI Builder expose their placement, visibility and data-source settings.

Process Automation Designer provides a visual canvas showing a case's stages, activities and transitions across its lifecycle, letting administrators inspect and model the flow. This satisfies the stem's requirement to visualise the lifecycle of a case.

Inbound Email Actions define how incoming email headers and body content map to case fields when Email-to-Case generates records. This is the configuration point satisfying the requirement, since the action's field mappings determine which header values populate which case fields.

The consumer-based model treats individuals as consumers directly on the consumer table rather than grouping them under corporate accounts.

Community Home is the baseline portal page that aggregates forums, blogs and topics, acting as the landing page users reach when browsing community content. It satisfies the stem's requirement for the entry point to community browsing.

Service contracts define entitlements and SLA definitions; cases linked to a contract inherit those SLA terms rather than defining their own. This satisfies the stem's requirement to describe the Case-to-Service Contract relationship, where the contract supplies the SLA applied to the case.

Performance Analytics indicators aggregate scores over time and support breakdowns, so an SLA compliance indicator broken down by agent and grouped monthly displays the required percentage directly. Standard reports cannot compute this time-series compliance percentage as cleanly.

Cases raised for an individual buying for personal use use the Consumer record type, which stores personal contact details rather than a business Account. Selecting Consumer populates the Account/Consumer field correctly, satisfying the stem's personal-use constraint.

A scheduled job can query the kb_knowledge table for articles with a last review date older than 90 days and update their state to Retired. This is a flexible and reliable way to automate retirement based on the last review date. It ensures articles are retired exactly 90 days after their last review, meeting the requirement.

Account Hierarchy provides the parent–child account tree that customer service managers need to view and manage corporate relationships, satisfying the stem's requirement for hierarchical structure visibility. Unlike related modules such as Account Relationships, it specifically renders the multi-level account structure, enabling managers to navigate and administer linked parent and subsidiary accounts directly.

The Reset condition terminates the current SLA instance and starts a fresh one, restarting the timer from zero. This differs from Pause, which halts the clock but resumes the same instance, and from Stop, which ends it permanently without renewal.

Service Level Management (SLAs) defines response and resolution targets, then triggers escalation workflows when those targets are breached. The 24-hour resolution constraint maps directly to an SLA definition, whose breach action automatically escalates the case, satisfying the requirement without custom scripting or manual monitoring.

Performance Analytics dashboards for CSM Communities pull community activity data into indicators and breakdowns covering deflection rates and contributor rankings. This satisfies the in-workspace tracking constraint, since the dashboards surface adoption metrics without leaving the CSM interface.

By adding a reference field to the case creation form that references the Account table and is filtered to show only accounts associated with the logged-in contact through the Customer Relationship table, the contact can select the appropriate account. This is a standard customization using form design and reference qualifiers.

The Start condition field holds the filter criteria that determine which Case records enter the SLA workflow, so scoping it to Priority equals High and Account VIP status ensures the agreement applies only to those records.

A Notification is required to send an email or other alert to the group manager when the case is assigned. The notification can be triggered by the assignment event or by a condition on the case, such as when the assignment group changes to the specified group, ensuring the manager is informed.

Resolving a problem does not cascade to linked cases, so each case retains its existing state value. This satisfies the stem's default-behaviour constraint: ServiceNow applies no automatic state transition across the problem-to-case relationship, leaving agents to update case state manually.

Standard Reports query case objects natively, letting you aggregate metrics such as open volume, age, and resolution time by owner or status. They satisfy the tracking requirement without custom development, unlike dashboards alone or list views, which show records rather than performance trends.

Record Producers present a guided form interface that captures the fields needed to create a case, so portal users supply complete, structured information without navigating backend case forms. This directly simplifies case creation, satisfying the stem's requirement for a guided experience for users.

The Table field on an SLA Definition determines which task table the engine evaluates. If it is set to a table other than the Case table, the definition never attaches to cases regardless of how correct the conditions and schedule are. Verifying this field is the first logical troubleshooting step when an SLA does not attach.

The Email UI action on the article preview or contextual search panel opens a compose window pre-populated with the article link, letting the agent send it to the external contact. This satisfies the requirement to email a published article directly from the case.

The Escalation Record is the dedicated object that stores the escalation details, including the mandatory Escalation Reason field, and provides the tracking interface for a case assigned to a group. It satisfies the requirement to both record the reason and monitor escalation progress.

Advanced Work Assignment routes incoming work items by evaluating agent availability, capacity and skills against assignment criteria, pushing cases to the best-matched agent. This directly satisfies the requirement to route cases based on both availability and skills.

SLA Definitions support warning and breach notifications, and the SLA engine raises corresponding events that workflows and notifications can consume. Configuring the warning threshold and breach notification on the definition, or handling the breach event in a workflow, delivers emails at the correct times without custom polling. This is the supported, maintainable approach.