Skip to main content

Check Signal Health

Signal Health measures capture and session conditions such as questions, sessions, time to first token, error rate, capture-path conversion, and feedback volume. It does not determine why a user was confused or prove answer quality.

Investigate a low-signal state​

  1. Select the intended assistant and period.
  2. Check whether question/session volume changed with traffic or deployment.
  3. Inspect open → message → answer conversion and error rate.
  4. Check response timing for a deployment regression.
  5. Confirm plan eligibility, enableChatLogging, and visitor consent.
  6. Inspect an original record in Captured Questions.
  7. Apply context filters in Friction Insights only after capture looks reliable.

Eligible operational events and persisted conversation evidence are not identical. A decline can reflect traffic, consent, plan, configuration, CSP, authentication, or widget errors—not an improvement in user understanding.

CSV export is controlled by plan and export permission. Use Embed and Deployment, Contextual Help, and Troubleshooting for deployment failures.