Calls

Part 1 is about calls, which this demonstration does not have. Part 2 is a different thing: synthetic requests to the briefing service, which it does have.

Part 1 · Calls: kept in a separate snapshot

Not measured Known gap

The synthetic figures on these pages contain no calls. Every figure here counts synthetic requests, and a request is not a call. The timing records the requests come from hold no call identifier, so requests cannot be counted as calls or grouped into them, and no number in Part 2 is a number of calls.

The real demo calls are in a separate, fixed snapshot on the Recorded demo calls tab (85 archive entries when it was taken). They are shown there with their recordings, transcripts and review findings, and are never counted together with the requests below, or used to explain them.

Number of calls Not measured

Not derived from requests. The snapshot lists its own count.

What would measure it: A call identifier stored with each timing record, so that requests could be tied to calls.

How each call ended Not measured

Whether the caller got what they needed is not in request timing.

What would measure it: Call records with outcomes, reviewed by a person.

Transcripts Not measured

No transcript is used by the synthetic figures. Transcripts are on the Recorded demo calls tab.

What would measure it: Reviewed call transcripts, held apart from this dashboard.

Recordings Not measured

No recording is used by the synthetic figures. Recordings are played on the Recorded demo calls tab.

What would measure it: A person listening to real recordings, in a private review tool.

Known gap (Q-07): a timing record cannot be matched to the call it came from. Read the item.

Time rangeWhole synthetic window Last 24 hours of the window Last 6 hours of the window

Showing 1,200 synthetic requests, Mon 05 Jan 00:01 UTC to Thu 08 Jan 04:25 UTC. Dates are synthetic. Trends, Predictions and the Improvement queue always use the whole window.

Part 2 · Synthetic request explorer: requests, not calls

Synthetic

Requests, not calls. A request is one ask of the briefing service: a briefing, an alternate-airport check or a flight plan. One call could make several, and this data cannot say which.

Counts beside each outcome are for the type and time range chosen. A request with no timing record has no known outcome, so it appears only under "No timing record" and "Needs attention", never as slow or fast.

1,200 synthetic requests match, showing 776 to 800.

Synthetic requests. Not calls.
Request	Started (synthetic)	Type	Outcome	Preparation time	Sections with a skipped lookup	Prediction
R-0425	Tue 06 Jan 08:53 UTC	Briefing	Slow (over 8 s) Near the time limit	15.5 s	None	Training period
R-0424	Tue 06 Jan 08:52 UTC	Alternate-airport check	Completed	1.8 s	None	Training period
R-0423	Tue 06 Jan 08:35 UTC	Briefing	Completed	8.0 s	None	Training period
R-0422	Tue 06 Jan 08:27 UTC	Flight plan	Completed	7 ms	n/a	Over before 1 s
R-0421	Tue 06 Jan 08:21 UTC	Briefing	Completed	5.5 s	None	Training period
R-0420	Tue 06 Jan 08:18 UTC	Type not recorded	No timing record	Not recorded	Not recorded	Not recorded
R-0419	Tue 06 Jan 08:09 UTC	Briefing	Completed	7.0 s	None	Training period
R-0418	Tue 06 Jan 08:06 UTC	Briefing	Slow (over 8 s)	12.0 s	None	Training period
R-0417	Tue 06 Jan 07:58 UTC	Flight plan	Completed	8 ms	n/a	Over before 1 s
R-0416	Tue 06 Jan 07:52 UTC	Briefing	Completed	6.8 s	None	Training period
R-0415	Tue 06 Jan 07:46 UTC	Type not recorded	No timing record	Not recorded	Not recorded	Not recorded
R-0414	Tue 06 Jan 07:32 UTC	Briefing	Slow (over 8 s)	9.5 s	None	Training period
R-0413	Tue 06 Jan 07:22 UTC	Briefing	Slow (over 8 s)	8.9 s	None	Training period
R-0412	Tue 06 Jan 07:14 UTC	Alternate-airport check	Completed	1.5 s	None	Training period
R-0411	Tue 06 Jan 06:53 UTC	Briefing	Slow (over 8 s)	11.8 s	None	Training period
R-0410	Tue 06 Jan 06:26 UTC	Flight plan	Completed	5 ms	n/a	Over before 1 s
R-0409	Tue 06 Jan 06:22 UTC	Alternate-airport check	Completed	1.6 s	None	Training period
R-0408	Tue 06 Jan 06:06 UTC	Briefing	Completed	7.1 s	None	Training period
R-0407	Tue 06 Jan 06:00 UTC	Briefing	Completed	6.1 s	None	Training period
R-0406	Tue 06 Jan 05:50 UTC	Alternate-airport check	Completed	1.2 s	None	Training period
R-0405	Tue 06 Jan 05:45 UTC	Briefing	Completed	5.9 s	None	Training period
R-0404	Tue 06 Jan 05:33 UTC	Briefing	Slow (over 8 s) Near the time limit	14.6 s	None	Training period
R-0403	Tue 06 Jan 04:59 UTC	Type not recorded	No timing record	Not recorded	Not recorded	Not recorded
R-0402	Tue 06 Jan 04:40 UTC	Briefing	Slow (over 8 s)	9.7 s	None	Training period
R-0401	Tue 06 Jan 04:22 UTC	Briefing	Completed	5.2 s	None	Training period

Engineering details: what a request record is

Each row is one synthetic timing record in the real record shape (fs.telemetry.request.v0), or a request the synthetic world lost before a record was written. Open a request to see its record, the field-by-field check of what was known at the 1-second mark, and which earlier requests the rolling baseline read.

The request number (R-0001 upward) is the order the requests were generated in. It is not a call number and is not stored in the record.