CSM / HRSD Architect
1Customer or Employee data model, integration with existing ITSM CMDB, multi-channel portal design
Modernization path
Deploy CSM and HRSD for customer and employee experience.
ServiceNow Customer Service Management and HR Service Delivery implementation: portals, workflows, CRM and HR system integrations unified on the Now platform.
Key figures
12-24 months
optimal window to deploy CSM or HRSD after ITSM (mature CMDB, stabilized team)
< 3 clicks
target for mobile-first CSM portal to resolve a standard case
5-8 people
typical team for a standard CSM or HRSD scope, over 6 to 14 months
ATLAS methodology applied
From scoping to deployment, five structured phases.
Each phase aggregates one or more of the ten ATLAS steps. No phase starts until the previous one has delivered its validated artefact. The ATLAS methodology makes AS/400 migration predictable and auditable.
- 01Phase 1
Scoping & business sponsoring
ATLAS stepsE1 Intake · E2 DiscoveryIdentify the formal business sponsor (Customer Service Director for CSM, CHRO for HRSD), scope perimeter and priority workflows, inventory existing tools to replace or integrate (Salesforce, Zendesk, Workday Help, etc.), assess prior ITSM maturity.
Phase deliverableBusiness+IT co-signed project charter + priority scope - 02Phase 2
Experience workshops
ATLAS stepsE2b Functional spec · E2e CapturePersonas, user journey, historical friction points, autonomy expectations workshops. The CSM portal is designed mobile-first with fewer than 3 clicks to resolve. The knowledge base is written in customer tone (CSM) or employee tone (HRSD), not IT jargon.
Phase deliverablePersonas + validated journeys + signed portal mockups - 03Phase 3
Target architecture & integrations
ATLAS stepsE3 Dependency mapping · E4 Target architectureData architecture on the Now platform (Customer or Employee model), CRM (Salesforce, Dynamics) integrations for CSM or HR system (Workday, SAP SuccessFactors, ADP, Cegid) for HRSD, pooling of portal / CMDB / workflow engine with existing ITSM.
Phase deliverableSigned target architecture + integration mockup - 04Phase 4
Configuration & development
ATLAS stepsE5 Migration · E6 Parity validationForm, workflow, knowledge base, communities (CSM) or HR self-service (HRSD) configuration. Performance Analytics. User testing on real case sets.
Phase deliverableConfigured platform + business key-user-validated workflows - 05Phase 5
Change management & go-live
ATLAS stepsE7 DeliveryChange management started 3 months before go-live, key user and end user training, CHRO or Customer Service Director support, communication plan, post-go-live adoption measurement.
Phase deliverablePlatform in production + trained key users + measured adoption plan
Who is concerned
Business context and modernization stakes.
Why extend ServiceNow beyond ITSM
Once ServiceNow ITSM is in place, many organizations seek to extend the platform to customer (CSM) and employee (HRSD) functions to pool the portal, the CMDB, the workflow engine, and AI capabilities. The promise: one tool, one user experience, one ALM rather than continuing to stack Salesforce Service Cloud, Workday Help, Zendesk, and others. ServiceNow CSM (Customer Service Management) covers external customer relations (cases, multi-channel communications, customer knowledge base, communities). ServiceNow HRSD (HR Service Delivery) covers internal HR services (onboarding, offboarding, administrative requests, employee FAQ, HR tickets).
The right time to deploy CSM or HRSD
The right timing to extend to CSM or HRSD is between 12 and 24 months after the initial ITSM deployment. Before 12 months, the ServiceNow team is still in ITSM stabilization and the CMDB is not mature — deploying CSM or HRSD too early weakens both perimeters. After 24 months, the business teams that could have benefited from CSM/HRSD have often found other tools (Salesforce, Zendesk, Workday Help) and pooling is more difficult. Typical scenario: ITSM in year 1, ITOM in year 2, CSM or HRSD in year 2 or 3 depending on business priorities.
Source platform
Fragmented customer / employee environments
Scoping reference
Typical duration and team for this path.
A ServiceNow CSM or HRSD implementation is typically structured over six to fourteen months depending on scope. The cell combines a ServiceNow CSM/HRSD architect, two to three functional consultants (customer relations or HR), two ServiceNow developers, a UX designer for the portals, an integrations consultant (CRM, HR system), a project manager. For a standard CSM scope with customer portal + multi-channel cases + knowledge base + communities, plan eight to ten months with a cell of five to six people.
Challenges
- Offering a unified experience on the customer and employee side.
- Integrating with existing commercial CRMs and HR systems.
- Designing fluid journeys without business friction.
ATLAS approach
- Customer / employee experience workshops.
- CSM and HRSD configuration, tailored portals.
- Salesforce / Dynamics / HR system integrations.
Expected outcomes
- Operational customer and employee portals.
- Documented and automated resolution workflows.
Identified pitfalls and ATLAS response
What we learned on this migration path.
Pitfall 01
Modeling CSM on ITSM without rethinking the customer experience. The external customer is not an internal technician: their journey, expectations, and patience differ fundamentally.
ATLAS response
Dedicated customer experience workshops before configuration: personas, user journeys, historical friction points, autonomy expectations. The CSM portal is designed mobile-first with fewer than 3 clicks to resolve a standard case. The customer knowledge base is written in the tone of the end customer, not in IT technical jargon.
Pitfall 02
Deploying HRSD without strong CHRO sponsorship. HRSD touches core HR processes (onboarding, payroll, training) and without sponsorship, the project stalls on organizational arbitrations.
ATLAS response
Formal CHRO sponsor identified from scoping, HR+IT co-pilot rather than IT-only piloting. HRSD processes are not configured in IT silo — each workflow (onboarding, leave request, expense management) is validated by HR teams before development. HR change management started 3 months before go-live.
Cell composition
A specialized cell for this modernization path.
Several distinct profiles, mobilized over the full program duration. Reproducing this cell internally is rarely realistic — the legacy skills shortage and ATLAS expertise depth make outsourcing structurally faster and less risky.
Duration
6 to 14 months depending on CSM, HRSD or both scope
Volume
5 to 8 people for a standard CSM or HRSD scope
Profiles
CSM or HRSD functional consultant
2-3For CSM: customer journey, knowledge base, communities. For HRSD: onboarding, HR requests, employee FAQ
ServiceNow developers
2Form configuration, workflows, client/server scripts, Performance Analytics
Portal UX designer
1Mobile-first, accessibility, autonomous journey, non-technical tone (CSM) or internal tone (HRSD)
Integrations consultant
1Connectors to Salesforce / Dynamics 365 (CSM) or Workday / SAP SuccessFactors / ADP / Cegid (HRSD)
Project manager + business sponsor
1+1For CSM: Customer Service Director. For HRSD: CHRO. Formal co-pilot — not IT-only piloting
Frequently asked questions
What decision-makers ask about this path.
Does ServiceNow CSM replace Salesforce Service Cloud?+
Yes for the majority of cases, but the choice depends on the global ecosystem. ServiceNow CSM is advantageous when the organization already has ServiceNow ITSM and wants to pool. Salesforce Service Cloud remains preferable when the organization already has Salesforce CRM (Sales Cloud) and wants native sales-service integration. Both tools functionally cover external customer relations; the main selection criterion is consistency with the dominant ecosystem. Our initial scoping evaluates this choice with the client.
Does HRSD replace Workday or SAP SuccessFactors?+
No. HRSD does not replace a core HR system (Workday, SAP SuccessFactors, ADP, Cegid) — it integrates on top to add an employee experience layer (portal, FAQ, HR tickets, cross-functional workflows). The core HR system keeps HR data management (employees, contracts, payroll, talents). HRSD brings the service layer that classic HR systems do less well: unified portal, AI search, communities, cross-functional workflows between functions (IT, HR, Facilities).
How much does a CSM or HRSD deployment cost?+
For a standard CSM scope (customer portal + multi-channel cases + knowledge base + communities) with a few thousand served customers, plan six hundred thousand to one million euros of implementation in nearshore co-delivery. For a standard HRSD (employee portal + onboarding + HR requests + knowledge base) with one to five thousand employees, plan four hundred to eight hundred thousand euros. ServiceNow CSM or HRSD licenses are added, varying with the volume of users and activated modules.
Considering ServiceNow CSM or HRSD?
Three concrete ways to start — from a targeted POC to a full implementation. Our approach clearly distinguishes CSM (external customer experience) from HRSD (employee services), with business sponsorship formalized from scoping.
Case studies
Client cases on this technology
Other paths in the same pillar