When most people hear ServiceNow CSM — Customer Service Management — they picture a case management tool. Something built for external customers, support agents, and complaint queues. And for a lot of IT teams, that assumption is enough to stop the conversation before it starts. But here's what gets missed: for large organizations where a central IT department serves multiple group companies, CSM isn't just a customer service tool. It's a structural platform decision — one that determines how cleanly your services are defined, how securely your data is separated, how automatically your SLAs are enforced, and how transparently your costs are reported.
Through this article, I want to highlight the limitations that IT organizations face in a multi-company setup when they rely only on ServiceNow IT Workflows — and show how introducing ServiceNow CSM data model in ServiceNow architectural model easily eliminates many issues like platform maintenance, upgradability & scalability.
Business Model Transformation: Internal Customer-Service Provider
In complex multi-brand organizations, central IT has typically been viewed as a support function. However, a shift is underway toward an Internal Customer-Service Provider model, complete with structured financial and billing systems. Group management and executives now require detailed information about the actual IT expenditure and activities associated with each company within the central IT organization.
Challenges without ServiceNow CSM:
Without the ServiceNow CSM data model, your architecture would look like the diagram below. With CSDM as the base layer — containing Business and Technical Service Offerings — IT workflows use the CSDM model as master data, with an experience layer sitting on top.
Layered Architecture without CSM
When we take this model and apply it to a Central IT which is providing IT services to multiple companies with clear requirements of data & process segregation following key customizations and configuration are needed.
- Customizations in Company Structure & User Criteria – The company table in foundation data model is over customized to accommodate the Group Companies as Customers. This leads to code-based user criteria to achieve the security requirements on the platform for maintaining the data and processes segregation of each platform
- Catalog & Service Offering Subscription – As the service offerings and catalog grow, it becomes increasingly difficult just to use “subscribed by” field on service offerings to track who has bought what.
- Messy Contracts & SLA Management – Due to point 1 and 2 above, the contract & SLA management becomes a nightmare for IT organization. For example, if company A has a “Premium” contract for Service Offering Email and company B has “standard” contract for same Service Offering. The result, often in practice, is two different service offerings Email Premium & Email standard in CSDM.
- Portal Widget Customizations – Additional Portal customizations with ACLs & User Criteria are done to show company A & Company B only their relevant tickets, services & assets.
With above mentioned customizations & configuration changes it becomes hugely challenging to manage & govern the ServiceNow platform, it takes extra effort to upgrade, scale and maintain the platform.
Plugging in ServiceNow CSM:
Layered Architecture with CSM
When we activate the ServiceNow CSM account structure, it delivers the following benefits –
- Logical Separation of Processes & Data – With CSM Account Data model, maintaining each group company as Accounts brings in a logical separation of processes and underlying data for IT workflows. This separation can be leveraged with no-code and low-code configurations across the platform.
- Sold Products to Service Offerings link - Company A and Company B are each set up as Accounts in CSM. Against each account, you attach Sold Products — which in the CSDM/CSM integrated model, map directly to Service Offerings. For Service Offering Email, we can maintain two separate sold products Email Premium sold to Company A and Email standard sold to company B. This one architectural change leads to marked improvement in Contracts & SLA management.
- Out of the Box Security Configurations – Leveraging Account Structure, Cases (incidents, problems & changes) are segregated out of the box i.e. Requests & Incidents of Company A are visible only to users from company A without any need of ACL configuration or User Criteria adjustments. The activation of CSM also brings in snc_external role to the platform which automatically limit access to end users of different group companies.
- Minimal Customer Portal Configurations – With Account-Contact Data model, the visibility & security conditions are built-in the underlying ACLs. No additional complex configurations are required. If needed, an individual customer portal for each brand can be created & maintained with minimum effort.
- Increased visibility for Financials – The service and product each group company (internal customers) are using are clearly visible and segregated. This helps in better business & resource planning while providing proactive support to all your customers.
- Enhanced Customer Experience – ServiceNow CSM enables to manage the end users as contacts in Account Contact data model. This gives more options to central IT team to enhance end user experience as they do not have to worry about security/access configurations
Summary
If you are running a central IT organization that provide service to multiple group companies, you might also be facing similar challenges. Without ServiceNow CSM, a central IT organization ends up using customization to patch the gap. Every new business demand ends up being a code-heavy configuration which becomes a nightmare to maintain and manage with every upgrade. The CSDM gets duplicated service offerings effecting CSDM health. And most of all it hinders or stops organizations to get maximum value from the ServiceNow platform.
This is much more than adding new application to your instance. It is about leveraging out of the box data model which is more aligned to your business model and outcomes. Adopting CSM account data model, brings in end-to-end relationship for each Internal Company (Account) to the Services they are consuming, mapped via Sold Products, linking to end Assets and CIs used to provide that service. This complete visibility changes the IT Financials side too. Contract & Entitlements for each company are tied to their account, not buried in scripted logic. Chargeback and billing become reportable because the cost chain from CI to service to company is traceable through the data model itself. And when leadership asks what it costs to serve Company A versus Company B — you have a clear, defensible answer without running a manual exercise to find it.
