Predictive Analysis
Forecasts for the recorded demo calls, for the selected range: two plain historical rates, each with an observed count and a range for its own uncertainty, offered as this dashboard's only stated expectation for the next comparable call — never a calibrated per-call probability, never a causal claim, and never blended with the synthetic experiment. Show the synthetic experiment instead.
Mon 28 Sep 2026 14:54 UTC (Mon 28 Sep 2026 09:54 CDT) to Tue 29 Sep 2026 14:54 UTC (Tue 29 Sep 2026 09:54 CDT), by the server's clock right now. The boundary is inclusive: a call exactly at the start of the window is included, one second earlier is not.
Not counted here: 57 older than this window.
Forecast for the next comparable call
Two clearly specified questions about a future demo call. For each, the forecast is the observed historical rate — the baseline expectation for the next comparable call — and beside it is a 95% range for how much that underlying rate could reasonably differ from what was observed: a statement about the rate's own uncertainty, not about the odds of any one specific future call. Below 5 eligible calls, only counts are shown: too little evidence for either.
| Question | Observed and forecast |
|---|---|
| Will it connect? (of calls with a known connection status) | 1 of 1 — insufficient evidence for a forecast (fewer than 5 eligible calls) |
| If it completes, will it run longer than 5 minutes? (of completed calls with a recorded length) | 1 of 1 — insufficient evidence for a forecast (fewer than 5 eligible calls) |
Call length is how long a completed call lasted. It is not how fast the service answered, and it is not linked to any timing record — see below.
Recurring patterns in this range
The same small, fixed, local checks the Improvement queue uses, over the calls in this range: what was flagged most, each with a recommended action and the calls it was flagged on. No recording is listened to and no model judges a call; a call a check cannot decide is left out of that check's own rate, never counted as passing.
No check flagged a call in this range.
Every check, and the rest of the flagged calls: Improvement queue.
What a timing-based prediction still cannot do
No timing-based prediction is shown here. That specifically would need a timing record linked to a call, and a timing record carries no call identifier (known gap Q-07), so none of the 1 recorded calls in this range can be linked to one. The historical-rate estimates above use only each call's own recorded fields (connection, completion, length) — never a timing record — and are not a substitute for one: they say nothing about how fast the service responded, and this gap is unaddressed. The recorded calls are shown, with their own evidence, on the Calls tab.
| Evidence | Calls |
|---|---|
| Recorded calls | 1 |
| With a transcript | 1 |
| With a recording | 1 |
| With a stored weather briefing | 1 |
| Linked to a timing record | 0 |
| Eligible for a timing-based prediction | 0 |
Anything a model or a listener could say about these calls (was the answer right, did the voice sound clear) is not computed here: it is pending, and labelled as such wherever it would appear.