The complete WebChatAgent dashboard explained
Find the right surface quickly and understand what every daily number actually measures.
The dashboard home is an operational overview, not a full analytics report. It combines assistant access, quick actions and daily statistics so the next task is one click away.
Dedicated pages for conversations, live chat, analytics, leads, feedback, questions, bookings and calls provide the detailed workflow behind each number.
What you will have at the end
- A clear mental map of dashboard navigation
- Correct interpretation of daily KPIs
- A repeatable path from signal to detailed record
Before you start
- A WebChatAgent account
- Optional: one chatbot with sample activity
Overview first, workflow second
Home summarizes today across six metrics: sessions, user messages, bot replies, conversion, leads and bookings. It does not replace date-range analytics.
Navigation visibility can depend on account permissions, plan and enabled features.
01–05
Set it up step by step
Open and manage AI assistants
Use the assistant list as the entry to configuration.
The assistant cards show the bots available to the account. Open one to access configuration, data sources, tools, widget, integrations and testing. Confirm the name before changes.
Use Quick Actions
Jump directly to common workflows.
Use quick actions for tasks such as creating an assistant or opening a common dashboard. Treat them as shortcuts; permissions still apply at the destination.
Read the daily statistics
Distinguish activity from conversion outcomes.
Sessions count conversations, user/bot messages count activity, while conversion, leads and bookings express outcomes. Use these numbers to spot a change today, then investigate a longer range in Analytics.
Example & result
See the practical test and its result
Every tutorial includes a fixed input, the expected outcome and a transparent record of what was actually verified locally.
Practical example: The complete WebChatAgent dashboard explained
This exact scenario was completed with the temporary tutorial account.
Exact test input
Create “Tutorial Lab”, open Data Sources and return to the dashboard.
Expected result
The assistant appears once and all primary areas remain reachable.
What was actually verified
The empty dashboard, creation dialog and resulting Tutorial Lab navigation entry were verified.
Tips & tricks
Make the setup reliable
Test with realistic examples, record your baseline and change one setting at a time. That makes real improvements visible.
Do not optimize from one day
Daily cards are an alerting surface. Use Analytics date ranges and comparable traffic before drawing conclusions.
Permission-test team roles
Sign in with a representative team member and confirm the visible navigation matches assigned responsibilities.
When something does not work
Troubleshooting
Check status, permissions and test data systematically before changing the model or prompt.
The expected option is missing
Confirm the account plan, feature permissions and selected chatbot. Paid or beta features can be hidden when prerequisites are not met.
The test result is inconsistent
Reset the test conversation, keep the input identical and change one setting at a time so the cause remains measurable.
Ready for a production-style test
Choose one dashboard signal each week, open its detailed records and document the concrete content, routing or process change that follows.