Text preview & study summary

ServiceNow CIS-CSM - Customer Service Management Implementation - Cases Entitlements Omnichannel Portal

A free sample of 5 questions from this quiz, shown in full with answer choices and explanations. No interactivity — everything is visible on this page for study and review.

Want to test your knowledge? Launch the Interactive Exam Simulator

Question 1

An account manager wants to see a complete history of all interactions between the company and a specific customer, including all cases, phone calls, emails, and satisfaction scores. Which CSM feature provides this 360-degree customer view?

Answer choices

  • A. Create a custom report filtered by account

  • B. CSM Account 360 / Customer 360 view — a consolidated account workspace showing all cases, activities, contacts, entitlements, installed products, and satisfaction scores in a single pane (Correct)

  • C. Navigate to each table individually and search by account

  • D. Export data from multiple tables to Excel

Explanation

ServiceNow CSM provides an Account 360 view (Customer 360 in newer releases) accessible from the account record or CSM Agent Workspace: (1) All cases (open and historical) with status and priority; (2) Activity timeline — email exchanges, phone call logs, chat transcripts; (3) Contacts and their case history; (4) Installed Products — what the customer has purchased/deployed; (5) Entitlements — service contracts and remaining quota; (6) NPS/CSAT scores — satisfaction trend over time; (7) Outstanding quotes or renewals. This single-pane view enables account managers and senior support agents to understand the full customer relationship quickly. Individual table navigation (option C) is inefficient and lacks the integrated timeline view.

Question 2

A CSM implementation is going live in 2 weeks. The project team needs to ensure that all critical CSM configurations are correct before go-live. Which approach is BEST for pre-go-live validation?

Answer choices

  • A. Go live and fix issues as customers report them

  • B. Conduct a structured User Acceptance Testing (UAT) phase: test all case creation channels (portal, email, phone), validate SLA triggering and escalation, verify entitlement enforcement, test survey sending on case closure, and validate all integration points with a representative set of test cases from each customer tier (Correct)

  • C. Have the implementation team click through screens to check they look correct

  • D. Review the configuration documentation and mark it as tested

Explanation

CSM go-live validation requires systematic testing: (1) Channel testing — create test cases via portal, email, and simulated phone/chat to verify all inbound channels route correctly; (2) SLA validation — create cases for each customer tier and verify correct SLA definition applies and timer starts; (3) Entitlement verification — test Gold, Silver, and Standard tier cases to confirm entitlement enforcement; (4) Escalation paths — test priority changes, SLA breach notifications, and supervisor escalation triggers; (5) Survey testing — verify post-closure surveys are sent to the correct contacts; (6) Integration points — test FSM work order creation, ITSM escalation, and external system updates; (7) Security — verify customers can only see their own cases in the portal. Documentation review (option D) is necessary but not sufficient — functional testing validates actual behavior.

Question 3

A company's field service team handles on-site customer service dispatch. When a CSM case cannot be resolved remotely, it should automatically create a Field Service Management (FSM) work order and dispatch a field technician. What is the correct integration approach?

Answer choices

  • A. Field service dispatch is completely separate from CSM; agents send emails to the dispatch team

  • B. Configure the CSM-FSM integration: when a CSM case is escalated to "Requires Field Service," a Flow Designer flow creates a Work Order in FSM (fsm_work_order), linked to the CSM case, with the customer's location and product details auto-populated (Correct)

  • C. Create a new incident in ITSM and assign it to the field service team

  • D. Field technicians check CSM cases independently and self-assign

Explanation

ServiceNow's CSM-FSM integration is a native platform capability: (1) CSM case escalation trigger — a button, state change, or condition (e.g., "Remote resolution failed" checked) in the CSM case; (2) Flow Designer action: "Create Work Order" in FSM with auto-population of customer address, installed product, issue description, and priority from the CSM case; (3) Work Order linked back to the CSM case via relationship (the case shows "Related Work Orders" in a related list); (4) Customer is notified when technician is scheduled and dispatched; (5) FSM mobile app allows technicians to update work order status and resolve the linked CSM case upon completion. Separate email processes (option A) break the case management thread and create accountability gaps.

Question 4

A financial services company using CSM needs to ensure that when a VIP customer (marked as "Priority" on their account) submits a case, it is immediately escalated to a senior agent and a supervisor is notified. How is this automated?

Answer choices

  • A. Agents monitor a shared inbox and manually identify VIP cases

  • B. A business rule or flow triggered on case creation: if the related account has a "VIP Priority" flag, immediately set case priority to P1, assign to the VIP Support Group, and trigger a supervisor notification (Correct)

  • C. Add the customer's name to an email distribution list and CC the supervisor

  • D. Configure an SLA that times out in 15 minutes for VIP customers, triggering a notification

Explanation

VIP escalation automation: (1) Business Rule (before Insert) or Flow Designer trigger (Case Created): check `current.account.u_vip_priority == true`; (2) Set case priority to 1-Critical; (3) Set assignment group to VIP Support Group; (4) `gs.eventQueue('csm.vip.escalation', current)` fires a notification event; (5) Notification sends email/SMS to on-call supervisor with customer name, case number, and issue summary. This executes immediately upon case creation regardless of channel. SLA notification (option D) introduces a 15-minute delay before notification — unacceptable for VIP escalation. Manual monitoring (option A) creates gaps during breaks/shifts. The key advantage of the business rule approach is zero-latency automated escalation.

Question 5

During a CSM implementation, the client asks you to configure the system so that customers who email support@company.com automatically have cases created with the correct category and assignment. What components must be configured?

Answer choices

  • A. Only a mailbox monitoring scheduled job

  • B. Inbound Email Account (monitors the mailbox), Inbound Email Actions (rules that parse the email and create/update cases), and Email Routing rules that set category and assignment group based on email subject/body patterns (Correct)

  • C. Manual review of the shared email inbox by agents

  • D. An autoresponder that asks customers to use the portal instead

Explanation

ServiceNow email-to-case processing requires: (1) Inbound Email Account — configure the IMAP/POP3/Exchange connection to support@company.com in System Mailboxes; ServiceNow polls/receives emails; (2) Inbound Email Actions — server-side scripts that evaluate inbound emails and create csm_case records, setting fields from email metadata (subject → short description, from address → contact lookup); (3) Routing rules/conditions — subject line contains "billing" → set category = Billing, assign to Billing Queue; (4) Auto-acknowledgment — confirmation email to customer with case number. Without all three components, emails arrive but aren't processed into cases. Manual review (option C) is the pre-automation baseline being replaced. Autoresponders (option D) redirect rather than convert email interactions.