Configuration · Measurement

# Measure support that helps members continue

Look beyond reply counts. Track whether learners, community members, and customers can complete the next step they came for.

## Define the outcome for each workflow

A replay question is resolved when the right permitted resource is found. An access issue needs a confirmed entitlement and a successful correction. An onboarding question needs a clear next step. Keep these different outcomes distinct.

## Measure speed and completion separately

Track first response, time to resolution, reopened requests, and time spent waiting for a person. A fast greeting can coexist with a long unresolved case.

## Monitor AI coverage and human workload

Count requests resolved without a human reprise over a defined follow-up window. Include knowledge review, exception handling, and supervision when estimating time released.

## Connect support to the member experience

Review repeated friction around onboarding, learning resources, and community participation. Compare satisfaction and renewal behavior cautiously: support can influence them, but a dashboard alone does not prove why someone converted or left.

Illustrative support workflow

### “The AI replies quickly, but access tickets keep reopening.”

Investigate the actual access outcome and the connected workflow. Measure confirmed fixes and repeat contact, rather than treating the first message as a successful resolution.