Reports and operational visibility
Review conversation and team activity using the reporting views enabled for your workspace.
Use a test channel or sample conversation first. Confirm the visible result in ValueChat before applying the setup to production traffic.
How it works
- 01
Reports
Reports. Available views cover operational measures such as conversation volume, agents, inboxes, tags, teams, response/resolution handling and customer satisfaction where configured.
- 02
Filters
Filters. Use the intended date range, timezone, inbox/team and accessible account scope. A count in an inbox is not automatically the same metric as a report over a date range.
- 03
AI activity
AI activity. Agent traces and workflow execution history explain individual actions, errors and handoffs. They complement reports; a completed execution is not a revenue or conversion attribution model.
- 04
Limits
Limits. Report visibility depends on workspace features and role permissions. Do not infer advanced analytics, payment reporting, model cost billing or revenue guarantees from basic conversation reports.
What to verify
✓The expected channel, conversation, contact or execution is visible.
✓The assigned person or agent matches the routing rule.
✓No customer-facing message claims an action that failed.
✓Activity or execution history contains enough context to investigate.
Collect the workspace, channel, conversation and execution identifiers, then contact support@valuechat.app. Never send API keys or passwords.