TL;DR: Customer success and support are part of the product experience, helping customers onboard, train admins, implement features, and resolve blockers faster, according to StrongDM. For identity teams, that framing matters because access tooling only delivers value when deployment, adoption, and operational support are built into the programme.
NHIMG editorial — based on content published by StrongDM: Why customer happiness matters
Questions worth separating out
Q: How should teams evaluate support quality in identity tooling?
A: Teams should evaluate support quality by testing how quickly the vendor can diagnose real access failures, not by reading service descriptions.
Q: Why does customer success matter in access management programmes?
A: Customer success matters because identity controls only create value when teams can onboard, train, and run them consistently.
Q: How do you know if an identity platform is actually being adopted?
A: Look for behavioural signals such as regular use of the intended workflows, fewer manual exceptions, and lower dependence on informal access paths.
Practitioner guidance
- Bake enablement into rollout planning Assign onboarding, admin training, and escalation ownership before the first deployment wave.
- Test support against real identity failures Use scenario-based evaluation for entitlement breakage, access path failures, and configuration mistakes.
- Measure adoption as a control signal Track whether admins and users are actually using the intended workflows, not just whether the software was deployed.
What's in the full article
StrongDM's full blog post covers the people and process detail this post intentionally leaves at the analytical level:
- How StrongDM structures Customer Success around onboarding, training, and rollout planning
- How the Support team handles tickets, screen shares, and escalation workflows
- How internal support metrics are used to evaluate service experience
- How the company frames customer feedback as input into product iteration
👉 Read StrongDM's perspective on customer success and support in access management →
Customer success for access tooling: why teams should care?
Explore further