Scope
This guide covers measurement for Web Chatbot. Availability depends on your tenant package, role and configured providers.
Purpose
Deploy project-aware website conversations and lead capture.
Measure starts, engagement, handoffs and captured intent.
Before you start
Correct tenant and project selected
Required source or provider is available
An accountable owner is identified
Test data can be separated from live activity
Procedure
- Write the decision the report must support and choose the correct scope.
- Measure starts, engagement, handoffs and captured intent.
- Verify source freshness, identity coverage and the reporting window.
- Compare the result with campaign, customer and commercial context.
- Record data gaps, assumptions and alternative explanations.
- Create the next task, experiment or operating change from the finding.
Verify the result
Measure starts, engagement, handoffs and captured intent. Confirm that the intended record, state, run or report is visible to another authorised operator and that its next owner is clear.
Completion checkpoint
The capability is in the intended state, evidence is current, exceptions are owned and the next action can be understood without a separate status message.
Controls and limitations
Bound knowledge, disclosure, permissions and human escalation. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.