Best Practices: Creating CSM Cases for both ESC(Internal) and CSM(External )Portals
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi everyone,
I am currently working on a design for a client and would like to get your input and any relevant ServiceNow best practice documentation on the following scenario.
The Requirement:
My client needs to deploy a total of 6 record producers that all generate CSM cases, but they are split across two distinct portals and audiences:
- ESC Portal (Internal): 4 Record Producers designed for internal employees.
- CSM Portal (External): 2 Record Producers designed for external customers.
The Context& Challenge:
The 4 internal RPs on the ESC portal are meant for internal employees raising cases for their own internal issues (essentially an internal Shared Services/ Internal Support model).
Since Cases reside in the CSM scope. but the ESC portal is traditionally geared towards ITSM/ HR workflows and internal ( snc_internal ) users, I want to ensure my architecture aligns with ServiceNow's recommended practices before implementation.
Specifically, I am looking for advice or official documentation on:
- Data Model & Roles: What is the best practice for setting up internal employees to raise their own CSM cases without violating licensing or granting them external customer roles?(e.g., leveraging the Customer Service with Service Management plugin, or Employee as a Consumer).
- Segregation: Should I be utilizing CSM Case Types to separate these internal shared service cases from external customer cases?
- Portal Configuration: Best practices for configuring the Standard Ticket page in ESC so internal users can properly view and interact with their CSM cases.
Any links, Now Create documents or personal experiences implementing this hybrid model would be highly appreciated.
Thank you in advance!