Channel Activity
Channel activity helps you understand what happened after a user or visitor sent a message.
What to Review
Review activity when you need to answer:
- Which channel received the message?
- Which agent version served the response?
- Did the request connect successfully?
- Did the response use the expected knowledge?
- Were there errors or retries?
For Website Support verification, the strongest proof is a recent test message whose activity shows the expected served agent name, served revision, runtime session, and delivered state.
Common Review Moments
- After installing the widget.
- After deploying a new agent version.
- After changing knowledge.
- After a visitor reports a confusing answer.
- Before expanding a support agent to more pages or domains.
Prompt Composition
Some activity records may show safe prompt-composition metadata, such as status and hashes for knowledge sections. Treat these as proof signals. The dashboard should not expose raw hidden prompt text in public activity views.
What Activity Does Not Prove
Activity can prove that a specific revision served a message. It does not prove that every saved draft or knowledge edit is live. If an answer ignores new knowledge, republish the agent, bind the new published revision on the Website Support channel, then send another test message.
Channel Activity vs Eval Center
Use Channel Activity when you need to inspect one message or widget test. It is the best place to confirm the served revision, accepted state, delivered state, and recent channel errors for that interaction.
Use Eval Center when you need an aggregate quality view across delivery health, behavioral eval runs, imported suites, feedback, and redacted runtime evidence.
The two surfaces answer different questions. Channel Activity shows what happened to a message. Eval Center helps you review whether the support-agent change looks healthy across recent evidence.