> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Real-time insights

> Interpret the current workspace live counter and prepare freshness, access, and event requirements for future live insights.

The current live conversation read returns a count from the workspace's shared cache. It does not identify sessions, stream transcripts, calculate sentiment, or produce live recommendations.

## Read the available signal

Use [Get live conversation count](/api-reference/agents-platform/get-live-conversation-count) with a permitted workspace API key. The current implementation ignores `agent_id` and `agent_ids`; the result remains workspace-wide even when those parameters are supplied.

| Result | Interpretation |
| - | - |
| A count is returned | A cached workspace value was read. Confirm the producer and freshness before operational reliance. |
| Zero is returned | The cached value may be zero, or the cache key may be absent. This alone does not prove there are no active sessions. |
| An unavailable error is returned | The cache may be unavailable or its stored value invalid. Preserve the error state instead of displaying a fabricated zero. |

## Design a useful live display

<Steps>
  <Step title="Label the scope">
    Display the selected workspace and identify the value as a workspace count. Do not present it as an agent-specific metric or a list of active calls.
  </Step>

  <Step title="Expose freshness and failures">
    Record when your application last completed a successful read. This is a fetch time, not proof of when the underlying counter changed. Use a bounded refresh policy and display stale or unavailable state after failed reads.
  </Step>

  <Step title="Verify the producer before alerting">
    In a deployment with a supported runtime, confirm that authorized test sessions change the counter as expected and that ended sessions are reconciled. Establish operational thresholds only after the counter's behavior and freshness are understood.
  </Step>
</Steps>

The saved `monitoring_enabled` and `monitoring_events` fields do not establish a subscribable live event stream. Future transcript or insight streaming needs a released event schema, conversation-level authorization, delivery behavior, and retention policy. Review [real-time monitoring](/agents-platform/monitor/real-time-monitoring) and [WebSocket preparation](/agents-platform/deploy/server/websockets).

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Can I alert on zero as proof that all conversations ended?" id="real-time-insights-faq-zero">Not without additional evidence. A missing cache key also returns zero, and the read does not report producer freshness.</Accordion>
  <Accordion title="Will enabling monitoring create a live transcript dashboard?" id="real-time-insights-faq-stream">No. Saved preferences are separate from a working producer, transport, authorization path, and interface.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.