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

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.

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.

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.

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.

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.