Investigation brief
Summarizes the most useful next reading of the current range.
Analytics helps you understand how the workspace is being used over a selected time range.
Use it to review demand signals, compare the current window with the previous one, find busy time buckets, inspect hub and client activity, and notice when missing telemetry limits a diagnosis. Use Analytics when the question is about usage volume, geography, trends, or which hub or client deserves the next look.
| Question | Simple answer |
|---|---|
| Which range should I start with? | Use 24h for a normal review, 1h for a live issue, and 7d or 30d for trends. |
| What is the Top 15 explorer? | A ranked list for utterances, messages, intents, clients, hubs, and countries. |
| What happens when I select a row? | Analytics applies the matching filter so the rest of the page answers the same question. |
| What if Analytics is locked? | Open Billing. Usage analytics need workspace hub capacity. |
| What should I capture for support? | Range, active filters, data-quality warning, top signal, and any client or hub detail. |
Investigation brief
Summarizes the most useful next reading of the current range.
Current vs previous
Compares the selected window with the same prior window.
Telemetry completeness
Shows missing metadata that can limit map, intent, client, or hub diagnosis.
Demand signals
Lists the top utterances, messages, intents, clients, hubs, and countries.
Saved views
Jumps to common views such as Live ops, Country focus, Stability, and Noisy clients.
Time and heatmap
Shows when usage happens and which buckets are busiest.
Client posture
Groups clients by connected, idle, reconnect-prone, noisy, quiet, or disconnected behavior.
Geography
Shows country-level activity when telemetry includes country metadata.
Analytics can be visible in the sidebar and still show a locked state. The page text says Usage analytics need workspace hub capacity when the workspace is on the Free path.
When that happens:
24h range.Do not treat locked Analytics as a broken chart. It is a plan boundary until Billing says the workspace includes the needed capacity.
24h; use 1h for live incidents, 7d or 30d for trends.| Panel | What it answers | What to do next |
|---|---|---|
| Investigation brief | What matters most in the selected range. | Use the suggested action or clear filters. |
| Saved views | Which common lens to apply. | Choose Live ops, Country focus, Stability, or Noisy clients. |
| Current vs previous | Whether usage rose or fell from the prior matching window. | Widen the range if there is no baseline. |
| Telemetry completeness | Which missing fields limit the read. | Capture the warning before drawing conclusions. |
| When usage happens | Utterances, messages, connects, and disconnects over time. | Select a peak bucket when a spike needs review. |
| Signal composition | How the activity splits across speech, messages, connects, and disconnects. | Select a segment to focus the explorer. |
| Web Traffic Requests by Country | Where requests concentrate when country signal exists. | Select a country to filter the page. |
| Bucket heatmap | Busy and quiet windows at a glance. | Select the busiest cell or peak button. |
| Usage by hub | Which hubs carry the most volume. | Open the hub detail or filter the hub. |
| Connected surface | Hub volume, active clients, idle clients, and last seen time. | Open the hub row when a hub needs inspection. |
| Posture segments | Connected, idle, disconnected, flapping, noisy, and quiet clients. | Select a segment to filter the client ledger. |
| Clients worth checking | Clients with reconnect churn, stale presence, unusual volume, or missing country signal. | Open the client detail before changing setup. |
| Client usage ledger | Client-level utterances, messages, country, state, and age. | Open a client detail or filter that client. |
Saved views reset the page to a useful starting point:
| View | Use it when | What it changes |
|---|---|---|
| Live ops | Something is happening now. | Uses 1h and starts with message signals. |
| Country focus | You need geography. | Uses 7d and opens country signals. |
| Stability | You are checking reconnects or disconnects. | Uses 24h and message signals. |
| Noisy clients | One client may be too active. | Uses 24h, filters noisy clients, and opens client signals. |
Active filters appear as chips under Filtered by. Select one chip to remove that filter, or use Clear all to return to the full selected range.
The Top 15 explorer shows five ranked rows at a time and keeps the rank stable as you page through results.
Use the tabs to switch the question you are asking:
Selecting a top row applies the matching filter. That lets the rest of the page answer the same question without making you rebuild the search.
Use the search box inside the explorer when the Top 15 list is long enough that you already know the signal name. Search filters the visible top signals; it does not change the selected time range.
| Explorer action | Result |
|---|---|
| Switch tabs | Changes the ranked signal type. |
| Search top signals | Narrows the current tab by label. |
| Select an utterance, message, or intent | Applies that text filter. |
| Select a client or hub | Filters to that client or hub. |
| Select a country | Filters to that country. |
| Use Previous or Next | Moves through the ranked results five at a time. |
Client detail shows utterances, messages, connects, disconnects, posture, geography, and last seen time. From there you can filter the selected client or its hub.
Hub detail shows active and idle clients, recent usage, and the clients attached to that hub. Use it when the top list names a hub but the next check belongs to a specific client.
Open details before changing setup. Analytics is strongest when it helps you choose the next owner page: Clients for connection state, Permissions for access, Hubs for hub setup, Live Map for live presence, or Billing for plan limits.
Analytics can still be useful when some enrichment is missing.
| What you see | What it means |
|---|---|
| Country enrichment pending | Activity is still tracked by time, hub, client, and message, but map detail is incomplete. |
| No country signal yet | Telemetry has not included country metadata for the selected range. |
| No activity in this range | Try a wider range, then confirm Dashboard and Live Map are seeing fresh activity. |
| Telemetry completeness warning | Capture the missing field before opening support. |
For an Analytics question, include:
Analytics is clear when: