If you have ever worked on a ServiceNow Customer Service Management implementation and felt like something was missing from the customer data model, there is a good chance the gap was in how products are tracked after they are sold. The Sold Products and Install Base features in ServiceNow CSM are among the most powerful, and most underutilized, capabilities in the platform. When configured correctly, they transform customer service from a reactive ticketing exercise into a proactive, context-rich experience.
This article breaks down what Sold Products and Install Base actually are, how they work together, where they fit in both B2B and B2C scenarios, and why they are critical to making the most of CSM alongside Field Service Management and the Common Service Data Model.
What Are Sold Products and Install Base?
These two concepts are closely related but serve distinct purposes.
Sold Products represent a record of a specific product or service that has been purchased by a customer. Think of it as the bridge between your product catalog and your customer account. When a customer buys a software license, a piece of hardware, or a service subscription, a Sold Product record captures that transaction and ties it to the account or consumer.
Install Base is the broader framework that tracks where products are deployed, configured, and actively being used. An Install Base Item is a physical or logical instance of a product that exists at a customer site, in a customer environment, or associated with a specific end user. It answers the question: where is this product right now, and what state is it in?
Together, they form a lifecycle view of everything a customer owns or uses, from the moment of purchase through deployment, maintenance, and eventually retirement.
A simple way to visualize the relationship:
“`
Product Catalog
|
v
Sold Product <– linked to Account / Consumer
|
v
Install Base Item <– linked to Location / Asset / Configuration Item
|
v
Cases / Work Orders / Entitlements
“`
This chain means that when a customer calls in with an issue, the agent can immediately see what that customer bought, where it is installed, what version it is running, and what support entitlements cover it, all from one screen.
Why This Matters for Customer Service
Without Sold Products and Install Base, customer service agents are often flying blind. They know a customer has an account, but they do not know what products that customer is actually using. This leads to a familiar pattern of agents asking customers to repeat information they should already have, longer handle times, misrouted cases, and a poor overall experience.
When these features are properly configured, agents get immediate context. They can see:
- Every product the customer has purchased
- Which of those products are under an active support contract
- The current status and health of each installed item
- Any open or recent cases related to that product
- Scheduled maintenance or upcoming renewals
This context-driven approach is what separates world-class service from average service desk performance.
How It Works in a B2B Context
In a business-to-business scenario, the data model revolves around Accounts, Contacts, and the sites or locations where products are deployed. This is where Install Base becomes especially powerful because enterprise customers often have complex, multi-site deployments.
Consider a manufacturing company that purchases an industrial IoT monitoring platform from a technology vendor. That vendor might deploy sensor hardware at five different factory locations, each running different firmware versions with different configuration profiles.
In ServiceNow, the setup would look something like this:
“`
Account: Acme Manufacturing
|
|– Sold Product: IoT Platform License (Enterprise Tier)
| |– Entitlement: 24/7 Support, 3-year term
|
|– Install Base Items:
|– Sensor Array Unit – Chicago Plant (v2.1 firmware)
|– Sensor Array Unit – Detroit Plant (v2.3 firmware)
|– Sensor Array Unit – Houston Plant (v2.1 firmware)
“`
When a contact from the Chicago plant calls about a sensor malfunction, the agent immediately sees that specific Install Base Item, its firmware version, its location, and its support history. If a field technician needs to be dispatched, the case can be escalated to Field Service Management with all of that context already attached to the work order.
This is also critical for account managers doing renewal planning. They can see exactly which Install Base Items are approaching end-of-life, which support contracts expire in the next 90 days, and which accounts might be candidates for an upgrade conversation.
How It Works in a B2C Context
In business-to-consumer scenarios, the model shifts slightly. Instead of Accounts, you are working with Consumer records, which represent individual customers. Install Base Items are still used, but they tend to be simpler in structure and are associated directly with the consumer rather than a complex account hierarchy.
Take a home appliance company that sells smart refrigerators with connected monitoring features. Each unit sold to a retail customer needs to be tracked individually, linked to that consumer, and associated with any warranty or service plan they purchased.
The data model might look like this:
“`
Consumer: Jane Smith
|
|– Sold Product: SmartCool Pro 3000 Refrigerator
| |– Serial Number: SC300-X4892
| |– Warranty: 2-year parts and labor
|
|– Install Base Item: SmartCool Pro 3000
|– Location: Jane’s Home Address
|– Status: Active
|– Last Service Date: 6 months ago
“`
When Jane contacts support because her refrigerator is displaying an error code, the agent pulls up her consumer record and immediately sees the unit, its serial number, its warranty status, and its service history. There is no need to ask Jane for model numbers or purchase dates. The agent can determine whether the issue is covered under warranty and, if a technician visit is required, dispatch it through Field Service Management with the address already populated.
This kind of seamless experience directly impacts customer satisfaction scores and reduces call handle time.
The Connection to Field Service Management
The Sold Products and Install Base framework becomes even more valuable when CSM is paired with ServiceNow Field Service Management (FSM). FSM handles the dispatching of field technicians, management of work orders, and tracking of parts used in service visits.
When a case in CSM involves a product issue that requires an on-site visit, the agent can create a work order directly from the case. Because the case is already linked to an Install Base Item, the work order inherits all the relevant context: the customer location, the product type, the serial number, any known issues with that specific model, and the skills required of the technician.
The FSM work order then tracks:
- Which technician was assigned and dispatched
- Travel time and arrival confirmation
- Parts ordered or consumed during the repair
- The outcome and resolution notes
When the work order is completed, that information flows back and updates the Install Base Item record. The service history is preserved, and the next time that customer calls, the agent can see a complete picture of every interaction and every service visit associated with that product.
This closed loop between CSM and FSM is one of the most compelling reasons to invest in the Sold Products and Install Base data structures from the start of an implementation.
Alignment with the Common Service Data Model
The Common Service Data Model, or CSDM, is ServiceNow’s recommended framework for organizing service and technology data consistently across the platform. It defines how concepts like Business Applications, Services, Products, and Configuration Items should be structured and related to each other.
Sold Products and Install Base sit very naturally within the CSDM framework. Specifically, Install Base Items can be related to Configuration Items in the CMDB, which means you can connect customer-facing product records with the underlying technical infrastructure that supports them.
For a SaaS vendor, for example, a single Install Base Item representing a customer’s software subscription might be linked to:
- A Business Application CI in the CMDB representing the application instance
- A Hosting Environment CI representing the infrastructure tier
- Entitlement records that define what the customer is allowed to access
This alignment means that when an infrastructure issue causes a service degradation, you can trace the impact all the way down to which customers are affected, which Install Base Items are impacted, and which cases or SLAs might be at risk. It enables proactive outreach to affected customers rather than waiting for the phone to ring.
The CSDM alignment also supports reporting and analytics. Because the data is structured consistently, you can build dashboards that span IT Operations, Customer Service, and Field Service to give leadership a unified view of service health and customer impact.
Entitlements: The Third Pillar
No discussion of Sold Products and Install Base is complete without mentioning Entitlements. Entitlements define what level of service a customer is entitled to receive based on what they have purchased. They can be tied to Sold Products, Install Base Items, or Accounts directly.
When an agent creates a case, ServiceNow can automatically verify entitlement eligibility based on the product associated with the case. This ensures that customers on a basic support plan do not accidentally receive premium-level service, and that customers with premium contracts get routed to the appropriate support queue with the right response time commitments.
For B2B scenarios, entitlements are often complex, covering multiple products, locations, and contact types. For B2C scenarios, they tend to be simpler, such as a warranty period tied to a specific unit’s purchase date.
Getting entitlements right is where many implementations stumble. The key is to ensure that Sold Products are created and linked at the time of purchase, so that entitlement records are accurate and up to date before customers ever call for support.
Practical Tips for Implementation
Getting value from Sold Products and Install Base requires some upfront planning. Here are the most important considerations:
- Define your product catalog structure before building Sold Product records, since the catalog drives the categorization of everything downstream
- Decide whether Install Base Items should map to physical assets, logical instances, or both, based on your business model
- Plan your integration with order management or ERP systems so that Sold Products are created automatically when purchases are fulfilled
- Use the Account hierarchy in CSM to model parent-child relationships for enterprise customers with multiple subsidiaries or locations
- Build entitlement templates for common support packages to reduce manual configuration at the time of sale
- Train agents to search by Install Base Item and Sold Product, not just by account name, so they develop the habit of working in context
- Use the Install Base Item health status field to support proactive service programs, where you reach out to customers before problems occur
Common Pitfalls to Avoid
The most common mistake is treating Sold Products as an optional add-on rather than a core data structure. When organizations skip this step and only track customers at the account level, they lose the product context that makes everything else work.
Another frequent issue is failing to keep Install Base records updated after field service visits. If technicians complete work orders but the resolution does not flow back to update the Install Base Item status or configuration details, the records become stale and agents stop trusting them.
Finally, do not underestimate the data migration challenge. If you are implementing CSM for an existing customer base, you will need a strategy for loading historical Sold Products and Install Base records from whatever systems you are replacing. Incomplete historical data undermines adoption because agents quickly learn that the Install Base cannot be trusted for older customers.
The Business Case
When Sold Products and Install Base are implemented well, the business outcomes are measurable. Organizations typically see a reduction in average case handle time because agents spend less time gathering context. First-contact resolution rates improve because agents can immediately diagnose issues in the context of the specific product version and configuration. Customer satisfaction scores increase because customers feel recognized and valued rather than having to re-explain their situation on every call.
For field service operations, the benefit is in reduced truck rolls. When the work order already contains accurate product information, technicians arrive with the right parts and knowledge, rather than discovering on-site that they need a different component or a specialized skill.
For account management and sales teams, the Install Base becomes a goldmine of upsell and renewal intelligence. Knowing exactly what every account owns, when those products were purchased, and when support contracts expire gives commercial teams the data they need to have proactive, informed conversations.
Bringing It All Together
Sold Products and Install Base are not flashy features. They do not come with a slick dashboard out of the box or generate immediate excitement in a demo. But they are the quiet foundation that makes everything else in ServiceNow CSM work properly. They connect the customer to their products, the products to their support entitlements, and the service history to the ongoing relationship.
Whether you are supporting industrial equipment at enterprise manufacturing sites or consumer electronics for individual households, the principle is the same: great service requires knowing what your customers have, where it is, and what they are entitled to receive. ServiceNow gives you all the tools to capture and act on that information. The investment is in building the data structures correctly from day one and maintaining them with discipline over time.
Organizations that get this right consistently outperform those that do not, both in operational efficiency and in customer retention. That is the real value of Sold Products and Install Base.