Skip to content

Dashboard

Dashboard is the quickest way to see whether a workspace is being used, what needs attention, and how usage is changing in the selected period.

It shows association, not causation. A rise after a release is a reason to inspect the related conversations; it is not proof that the release caused the change.

Workspace operations brief with usage signals and recent conversations

What operators look for

After a publish, operators usually watch:

  • whether any client users are arriving
  • whether conversations are starting
  • whether message volume is rising or dropping
  • whether form activity is appearing when request forms are part of the flow

Check launch readiness before traffic starts

When a workspace has not recorded live traffic yet, Launch readiness turns setup into three checks:

  • Agent setup: create the Agent and publish the version that should reach users
  • Channel publish: publish the Channel, then resolve any health or Agent-ownership warning
  • Traffic tracking: share the Channel and watch for the first client conversations

A published Channel is counted as ready only when it is healthy and Codeer can identify a clear published Agent for it. Use the card's action to open Agents or Channels when setup needs attention. For a ready Web Channel, open the live URL shown under Traffic tracking or use Copy live link, share it with users, and return to the Dashboard to confirm traffic arrives.

Handle active human handoffs first

When an active Agent handoff is waiting for a human reply, the Dashboard puts it ahead of other activity. Use Open longest waiting handoff to start with the conversation that has waited longest.

The handoff panel shows the oldest waiting items first, including how long each has waited and its Channel. Open the conversation when one is available; otherwise, open the user detail page to continue the follow-up.

Time range matters

Use the time-range switch to match the question you are asking:

  • Past 7 days: recent launch checks
  • Past 14 days: short pilot review
  • Past 30 days: broader adoption and trend review

Know what each metric counts

Metric What it represents
Daily active users Distinct client identities recorded for each day
Daily conversations started New conversation histories created that day
Daily form tool calls by Agent Times an Agent asked the user for a configured form
Daily form submissions by Agent Forms users actually submitted; this can be lower than form tool calls
Credit spend over time Credits recorded for the workspace in the selected period

Open View detailed usage to inspect daily credit records when access is available. For organization-wide plan limits, invoices, or payment method, use Billing and Credits.

Account for freshness

Today may be labeled Today so far. Historical usage is aggregated daily, while latest conversations and the human-reply queue can refresh on a separate path. That means a new conversation may appear before every usage chart catches up.

If the brief says usage is still aggregating, wait for the daily update before comparing totals. Use Conversations for immediate operating decisions and the charts for period-level patterns.

How to read a quiet dashboard

A quiet dashboard is not automatically a problem.

It may simply mean:

  • the rollout is still intentionally small
  • the audience has not been invited yet
  • the channel is live but traffic has not started

Use it together with Conversations instead of treating charts alone as the full story.