Moving customer support from incident workaround to purpose-built CSM

A UK employee experience software company had been handling customer interactions through service request processes and the ServiceNow Incident module. This worked after a fashion, but the Incident module is designed for internal IT — it is not built for external customer service across multiple accounts and contacts. As the business grew and the number of customers increased, the limitations became increasingly visible: no proper account or contact model, case handling that did not suit external service, and reporting that could not reflect how customers experienced support.

The challenge

The core challenge was moving from an internally oriented model to one designed for external customers — without disrupting live support in the process. This meant:

• Modelling customers, accounts and contacts correctly within ServiceNow Customer Service Management.
• Transitioning from an Incident-based way of working to a case-based one in a way that felt natural for support agents.
• Designing case handling, assignment and reporting that matched how the organisation actually supported its customers.
• Keeping the implementation close to out-of-the-box CSM to ensure it remained maintainable as the platform evolved.

The approach

Hikon began by mapping the current state — how customers reached the organisation, how requests and issues were handled, and where the Incident-based approach fell short. That foundation informed the design: accounts, contacts, the case model, assignment routing and reporting were all shaped around the real support operation rather than a template.

Build and test followed, configuring CSM, validating the new model against real scenarios, and managing the transition from the old approach so support continuity was maintained throughout.

The solution

The CSM implementation gave the organisation a customer service platform with proper accounts, contacts and cases, replacing the Incident-based workaround. Customer interactions were now handled in a model built for external service: cases assigned to the right teams, accounts and contacts represented accurately, and reporting that reflected customer-facing performance rather than internal IT metrics.

Outcomes

• A purpose-built customer service capability on ServiceNow CSM, replacing an Incident-based workaround.
• Customers, accounts and contacts represented correctly in a model designed for external service.
• Case handling, assignment and reporting suited to supporting customers at scale.
• A maintainable implementation, close to out-of-the-box, that could grow with the business.

Why it matters

Many organisations that adopt ServiceNow for internal IT eventually reach the point where customers need to be served through the same platform. Using the Incident module for external service is a common stepping stone — but it is a workaround, and the limits show as the customer base grows. This engagement shows what a proper transition to CSM looks like: designed around real customer interactions, delivered without disrupting live support, and built to last.