ServiceNow's Customer Zero approach to AI experimentation

ServiceNow’s Ashraf Karim, Senior Vice President of Connected Customer Experiences and Technology, describes how the company acts as “Customer Zero” by testing new platform features internally before releasing them to customers, generating practical lessons about AI adoption in post-sale experiences such as support, onboarding, education, and developer services. She emphasizes that effective experimentation requires strong data foundations and instrumentation, particularly in historically underinvested post-sale functions, and focuses on customer outcomes including time to value, adoption speed, and fast issue resolution. Early agentic support tools successfully automated complex troubleshooting tasks but were initially abandoned because users found five-to-fifteen-minute waits unacceptable, leading the team to improve communication about background progress rather than simply changing the models. Users also preferred concise recommendations and next actions over visibility into every automated troubleshooting step, though the desired level of transparency can change as trust develops. ServiceNow evaluates nondeterministic AI outputs with an internal LLM judge against golden datasets while preserving customer control through follow-up questions and live-agent escalation, but it relies on real-user experimentation to measure satisfaction. Alongside business metrics such as revenue, operational savings, and agent time saved, the company tracks customer effort score, completion rates, repeat contacts, sentiment, and CSAT to distinguish technology performance from experience design. Karim argues that continual testing, learning from unsuccessful ideas, and separating technology variables from experience variables are essential as organizations deploy AI agents across diverse customer needs.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.