ServiceNow Certified Implementation Specialist - Customer Service Management (CIS-CSM) (CIS-CSM) (CIS-CSM) — Questions 76–150

The Company field on a contact record is a reference to the Account (customer_account) record and is the field that binds the contact to the business customer. When this reference is populated, the contact is treated as belonging to that account, so the contact can leverage the account's entitlements and raise cases against it from the Customer Service Portal.

Mandatory fields enforce data completeness at the Resolved transition, satisfying the workflow's requirement that specific information be captured before closure. Configuring these fields ensures agents cannot resolve cases lacking essential details, directly addressing the stem's demand for key components administrators must account for when designing Case Resolution Workflows.

Separate Knowledge Bases per subsidiary, each governed by distinct User Criteria, enforce record-level visibility so articles from Subsidiary A cannot surface for Subsidiary B users. User Criteria restrict access by user attributes, company, or role, satisfying the stem's hard isolation requirement within one shared ServiceNow instance.

Knowledge Workflow Configuration enforces the approval gate, satisfying the requirement that Tier 2 articles be reviewed by a Knowledge Manager before external publication. It defines states and transitions, so articles cannot reach published status without the designated approver completing their review step.

Reputation points derive from configurable point weights per activity, so raising weights for accepted answers and upvotes above basic post creation shifts scoring toward quality. This satisfies the stem's constraint of rewarding quality contributions rather than sheer posting quantity.

Expert Recognition awards visible badges and highlights to contributors whose answers are frequently accepted, satisfying the stem's community-forum setting. The mechanism is reputation-based recognition: the platform tracks accepted-answer counts and surfaces those users distinctly, encouraging sustained participation and signalling trustworthy expertise to other members browsing threads.

Matching Rules and Assignment Eligibility satisfy the skillset-to-product constraint by evaluating agent attributes against case criteria, then filtering eligible agents before assignment. Matching Rules define the fit between product and skill, while Assignment Eligibility restricts candidates, ensuring incoming cases route automatically to appropriately skilled agents without manual intervention.

The Activity Stream records every email, comment, and work note exchanged on a case, displaying sent and received communications chronologically in one place. This satisfies the requirement to view the complete communication history for a specific case.

Contextual Search surfaces relevant published articles directly on the case form, and its 'Attach' button links the selected article to the case record, creating the reference and tracking relationship the agent needs without leaving the case.

Comments and ratings submitted through the Customer Service Portal are written to the kb_feedback table, which stores the article reference, rating value, and user comments. This satisfies the requirement to capture portal-submitted feedback against knowledge articles.

A Survey Trigger condition on the Case table fires when the state field changes to Resolved, automatically dispatching the satisfaction survey to the customer contact. This declarative configuration satisfies the mandatory, event-driven survey requirement without custom code.

SLA escalation demands timely human awareness when a breach or warning threshold fires. The notification activity delivers templated emails to managers or support groups, satisfying the stem's requirement to handle escalation notifications within the workflow rather than merely logging the breach.

When a consumer becomes affiliated with a business customer, the standard pattern is to create a contact record linked to that account and associate the person accordingly, so their prior cases remain accessible while new activity gains account context. This preserves history and avoids duplicate identities, and it is a routine consideration when planning portal experiences for mixed requester populations.

The Contextual Search sidebar, surfaced via the Assistant tab, queries the knowledge base from within the active case form, so the agent never navigates away. This directly satisfies the stem's constraint of searching articles without leaving the case, unlike standalone Knowledge portals or global search interfaces.

Retiring a published article requires the knowledge_manager role, though workflow configuration can extend this to the author. This satisfies the stem's dependency on the configured approval workflow, which governs who may transition an article out of the published state.

AI Search queries both Knowledge and Communities result sources, and Genius Results surfaces a relevant KB article directly in the search response. This deflects cases by intercepting repeat questions at the search layer before a case is created.

Business Rules can be configured to run when a case is resolved, such as on update when the state changes to Resolved. They can execute server-side scripts to perform actions like sending notifications, updating related records, or creating tasks. This makes them a valid method to trigger automatic actions upon resolution.

Contextual Search Result Configurations let administrators define which fields are matched and assign field weights, so serial numbers in case descriptions surface relevant articles prominently. This satisfies the requirement to boost matches on the specific serial number field.

The Consumer record type represents individual customers who are not affiliated with a corporate account, enabling them to submit service requests directly. This satisfies the stem's requirement for individual consumers outside corporate accounts, unlike Business Account or Contact records.

Tab visibility on the Case form is governed by role-based access controls, so a missing Major Case tab indicates the agent's assigned roles lack the required permission. This directly satisfies the stem's constraint that the agent cannot view the tab despite the case existing.

"Work in Progress" is the ServiceNow case state that signals active agent involvement, satisfying the stem's requirement for a case currently being worked. It differs from "Open", which means unassigned or awaiting triage, and "Awaiting Info", which pauses the agent's work pending the customer's response.

Stages define the high-level milestones a case progresses through, such as intake, investigation and resolution, structuring the overall playbook flow. This satisfies the stem's requirement for components typically included in a CSM Case Playbook configuration.

ServiceNow resolves the article's Language field against the user's active session language, so a French portal session retrieves the French translation. This satisfies the internationalised knowledge base constraint: the platform stores each translation as a separate article version, and language matching selects the appropriate one automatically.

The portal derives the case's Account from the submitting contact's parent account record, so the lookup populates automatically without manual entry. This satisfies the scenario's automatic population requirement by inheriting the contact-to-account relationship stored in the CRM data model.

Case creation initiates the CSM case lifecycle, satisfying the requirement to identify its key components. Every case begins here, capturing the customer issue before assignment, investigation, or resolution can occur. Without this initial step, no subsequent lifecycle stage — triage, escalation, or closure — is reachable, making it foundational.

Response Templates in CSM allow agents to quickly insert predefined text with dynamic variables such as customer name and case number into an email or comment. They are designed for agent use during case handling, enabling personalized and consistent responses without manual data entry, exactly matching the scenario requirements.

Contacts link to a business account record, while consumers represent individual people. This satisfies the stem's distinction: contacts are account-scoped entities tied to a company, whereas consumers exist independently as person records, so the axis of difference is business-account association versus individual identity.

Assignment rules evaluate each case against their defined criteria; a case must satisfy those conditions for the rule to fire and apply its assignment. Matching the rule conditions is therefore one of the mandatory prerequisites.

Community question-to-article workflows let managers convert a verified community answer directly into a knowledge base article, preserving the original author and context. This satisfies the stem's requirement for Knowledge Management integration with Communities, closing the loop between peer-generated solutions and governed, reusable knowledge in the CSM environment.

Creating a Major Case Candidate escalates a case into the major incident management workflow, triggering cross-functional collaboration across teams. This directly satisfies the stem's requirement for an action performed from a Case record to initiate collaboration in Customer Service Management.

A multi-step approval workflow or Flow Designer flow bound to the knowledge base enforces sequential authorisation: the partner lead approves first, then the internal knowledge manager. Workflow-driven approvals support ordered stages, which a single approval step cannot provide, meeting the stem's two-step requirement.

Community discussion threads and questions can be converted into draft knowledge articles, letting agents capture user-generated content without retyping it. This satisfies the stem's requirement to leverage community content for knowledge management, since the article inherits the thread's content and links back to the originating discussion.

Problem Management provides the problem record and its many-to-many relationships to cases, enabling one problem to impact multiple related cases. Activating and configuring this module is the prerequisite for case-to-problem linkage, satisfying the stem's requirement that problem records span several cases.

Case Templates pre-populate fields such as short description, category, and assignment group, so agents avoid retyping recurring values. This directly delivers the stated benefit: reduced manual data entry plus consistent, standardised case information across similar cases.

Administrators access prior article iterations through the Versions related list, which records each saved revision as a separate entry. This satisfies the scenario's requirement to inspect historical article states without restoring them, since the related list exposes version metadata and content snapshots directly on the article record.

Removing child cases is available because the Major Case context aggregates related cases under a parent, and the child relationship must be severable without deleting records. This satisfies the stem's requirement for actions specific to that context, distinct from standard case actions such as reassignment or closure.

Active entitlements, their account linkage and expiration dates are stored as records in the Entitlement table, making it the authoritative source for this query. Reporting from it directly satisfies the requirement to list entitlements nearing expiry for a chosen account.

The Service Portal provides a self-service interface where end users submit cases directly, satisfying the requirement for a valid case-creation method in CSM. Submissions generate case records through the portal's configured record producer, distinct from agent-side or backend creation paths. This makes it one of the two valid mechanisms the question demands.

External repositories return their own field schemas, so mapping those result fields to ServiceNow search result display fields ensures titles, snippets, and links render correctly in the CSM portal, satisfying the requirement that external results appear as usable portal search results.

A Flow Designer flow triggered on the Account status field changing to 'Hold' can update related open cases and send notifications in one automated sequence. Workflow rules alone cannot reliably update child records and notify agents together.

Gamification requires awarding points for tracked community actions, so defining point values per action (posting, receiving upvotes) establishes the scoring currency. Without this mapping, reputation totals cannot accrue, making it a required configuration step for the reputation engine.

Entitlements link to service contracts, letting you group them so coverage is inherited from the contract rather than defined per entitlement. This satisfies the stem's requirement for a genuine Entitlements feature, since contract-level grouping governs which customers or assets qualify for specific support terms.

Agent Schedule and Skills directly drive the Assignment Workbench's selection logic: skills match the work item's requirements, while the schedule confirms availability during the required window. Together they satisfy the stem's constraint of influencing which agent the workbench selects, filtering candidates before assignment rather than after.

Data Policies enforce validation, required-field and format rules at the object level, so every case record adheres to the same standards regardless of entry channel. This prevents inconsistent or malformed values from being saved, directly satisfying the requirement to maintain data consistency across cases.

Create Knowledge from Community is the baseline UI action that copies a discussion thread's content into a draft knowledge article, preserving the link back to the source. It satisfies the requirement to convert a highly rated thread into validated knowledge.

Case tasks decompose a parent case into discrete units of work assigned to different teams, enabling parallel or sequential handling. This delegation mechanism satisfies the need to route sub-tasks to the appropriate resolving groups rather than one owner.

Case Types are defined under Customer Service > Administration > Case Types in the ServiceNow Navigator, where administrators create and extend case type records. This path satisfies the stem by providing the exact navigation route for defining new Case Types.

Customer Service Flow Designer provides the flow-based automation engine that can trigger on case creation, evaluate the product condition, create the problem record and establish the case-problem relationship, satisfying the requirement for automatic linked problem creation.

Linking cases to a problem aggregates every affected case under one root-cause record, so a single fix resolves all of them at once. This directly satisfies the systemic-issue constraint, since agents stop treating recurring symptoms individually and address the underlying defect.

Phone qualifies as a Work Channel since CSM logs voice interactions against cases, enabling agents to capture and manage customer conversations. This meets the stem's criterion of a channel used to receive and process customer work.

Following a tag entity creates a subscription record linking the user to that tag, so the platform automatically notifies them whenever a new thread is created carrying it. This satisfies the stem's requirement for updates on new threads matching #Billing, without the user manually monitoring the forum.

Blogs are a native ServiceNow Communities content type, letting authors publish posts that readers can comment on. This satisfies the stem's requirement for natively supported formats encouraging participation, since blog posts and threaded comments are built into the platform without custom development or external integration.

Forum access in ServiceNow Communities is governed by user criteria records linked to the forum via the Can Read and Can Contribute related lists. A user criteria record can evaluate conditions such as an active support entitlement, and the platform enforces it consistently across lists, search, and direct navigation. This is the native, supported mechanism for entitlement-based forum visibility.

The SLA Definition record carries the schedule and time zone fields that determine which support hours apply, letting each regional centre's operating hours drive its own SLA calculations. This satisfies the requirement for region-specific operating hours.

Mismatched display labels vs. backend choice values (e.g., 'Awaiting Info' vs 'awaiting_info') will prevent condition evaluation.

UI Builder and Service Portal Designer are the supported tooling for editing Community Home page widgets and layout, satisfying the stem's customisation requirement. Both expose the page structure, widget instances and layout containers an administrator must modify.

The sn_communities_moderator role grants access to moderation queues, letting holders review reported or flagged content and take action. This role is purpose-built for the moderation workflow, satisfying the requirement for users who interact with those queues.

User Criteria gate content visibility by matching user attributes, restricting proprietary forums to authorised accounts only. This satisfies the stem's security requirement by preventing unauthenticated or unauthorised community members from reading or posting in sensitive peer-to-peer forums.

The Virtual Agent embeds as a chat widget on the Customer Service Portal and Consumer Portal, letting end-users converse, resolve common requests and deflect cases before submission. Those portals are the supported end-user surfaces; agent Workspace is not an end-user channel.

The Create Knowledge UI action on the case form launches article creation with case fields pre-populated, letting the agent capture troubleshooting steps without leaving the record. This directly satisfies the requirement to author an article from the case itself.

The Customer Satisfaction Survey is the formal mechanism issued after case resolution, letting the customer rate the support experience and provide comments. Completing it satisfies the stem's feedback requirement, feeding directly into Cisco's service-quality measurement processes.

Major Case Management lets agents apply a single update to all child cases linked to a major case, rather than editing each individually. This mass update of related child cases is the capability named, keeping numerous affected cases synchronised during a widespread incident.

Modern SLA notifications are configured declaratively against percentage thresholds, so simple percentage-based email alerts need no workflow graph. This satisfies the stem's maintenance constraint: where only straightforward alerts are required, the notification feature avoids the overhead of building and maintaining full workflow logic.

The Pause condition stops the SLA duration timer while the case is in the Awaiting Customer state, and the Resume condition restarts it once the case re-enters a work-in-progress state. This is exactly the pause/resume behavior the manager requires, keeping elapsed SLA time from accruing during customer-wait periods.

The Report or Flag as Inappropriate button raises a moderation flag against the post, routing it into the community moderation queue for review. This satisfies the stem's requirement that a member bring spam to moderators' attention without needing moderator rights.

When an author checks out a published article, ServiceNow creates a new version in Draft state for editing. The original published version remains published and continues to be visible to users until the new version is published. This ensures that the current published content is not disrupted during editing. This is the standard behavior of knowledge article versioning.

Marking an account inactive blocks portal case submission because the Customer Service Management portal validates the account's active status before allowing a new case record to be created. This satisfies the stem's constraint that the account is inactive, preventing further inbound cases while preserving the existing case history for reference.

The Customer Relationship table models many-to-many links between accounts, so it suits peer or joint-venture arrangements where neither party is a subsidiary. The Account Parent field only expresses a strict hierarchical parent-child relationship, which cannot represent these reciprocal associations.

The default CSM workflow's transition condition requires the **Assigned to** field to be populated before a case leaves 'New'. Without an owner, the case cannot progress to 'Work in Progress', since assignment is the mandatory gate the workflow evaluates. Other fields, such as Short description, are not enforced by this transition.

A consumer record is designed for individual requesters who are not associated with a business account, which matches this caller exactly. By creating a consumer, the agent captures the person's details, allows them to submit and track complaints through the Customer Service Portal, and keeps the account table reserved for genuine business customers with contracts and entitlements.

Last name is a mandatory field on the Customer Contact record, satisfying the stem's requirement for standard fields. ServiceNow enforces it at the schema level, so a contact cannot be saved without it, unlike optional fields such as mobile phone or job title. This makes it a core identifying attribute for contact records.

Setting the Parent field on Company B's account to Company A creates the corporate hierarchy while preserving Company B's existing records and case history. This satisfies the requirement to reflect subsidiary status without data loss, since the account itself remains intact and only its hierarchical relationship changes.

An internal service agent can populate the Account field manually while creating the case, selecting the relevant account from the record. This satisfies the stem as one valid population method, alongside automatic derivation from the caller or related records.

The Account field links the case to the business account record experiencing the issue, establishing which customer the support request concerns. This lets agents track all cases for that organisation and drives entitlements and service-level agreements tied to that account.

Moderation rules evaluate posts against defined criteria and hold matching content for review before publication, so nothing inappropriate becomes publicly visible. This satisfies the pre-publication interception constraint, since filtering occurs at submission rather than after the post is already live.