In-app guidance becomes workflow orchestration, CS teams design adoption, and usage must prove out across regions

By DripPublished

The gist

Customer Success is shifting from reactive support and onboarding toward embedded, AI-driven workflow orchestration inside the product itself.

This week’s developments

In-App Guidance Becomes Workflow Orchestration

Whatfix is scaling AI-powered, contextual in-app guidance across Generali’s AGORA underwriting platform for users in roughly 27 countries across Europe, the UK, Asia, and North America. The rollout embeds step-by-step tips, nudges, intelligent agents, and ScreenSense-based context detection directly into live underwriting work, covering both onboarding and daily task completion.

The AGORA program already reports 80% faster completion of pre-bind underwriting activities and a 75% reduction in AGORA-related service desk tickets, plus lower support and maintenance staffing costs. That makes the signal clear: in-app guidance is no longer a training add-on; it is being measured as operational infrastructure.

For Customer Success teams, this shifts the job from periodic enablement to continuous orchestration inside the product. The practical edge now sits with practitioners who can configure contextual guidance, read workflow-level usage signals, and prove gains in time-to-proficiency and support burden. In enterprise rollouts, the value is moving away from static documentation and reactive ticket handling toward measurable adoption control.

How should we operationalize workflow guidance across teams and roles?

If you're an individual contributor

  • Static enablement is fading; your edge is workflow-level guidance skill.
  • Learn to configure in-app nudges and read usage signals—those skills make you indispensable as adoption moves inside the product.

Sources

If you manage a team

  • Your team must coach in-product behavior, not just run training sessions.
  • Shift coaching toward contextual guidance, exception handling, and adoption metrics so reps can prove time-to-proficiency gains.

Sources

If you lead the organization

  • You need to fund product-led orchestration, not more documentation.
  • Rebuild the CS operating model around in-app guidance, workflow analytics, and support reduction—or keep paying for manual adoption.

Sources

Stay ahead in Customer Success

Get the weekly Customer Success brief in your inbox — the developments, what they mean by seniority, and what to do next.