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 926 to 950.

Synthetic requests. Not calls.
Request	Started (synthetic)	Type	Outcome	Preparation time	Sections with a skipped lookup	Prediction
R-0275	Mon 05 Jan 19:23 UTC	Briefing	Slow (over 8 s)	11.1 s	None	Training period
R-0274	Mon 05 Jan 19:22 UTC	Flight plan	Completed	8 ms	n/a	Over before 1 s
R-0273	Mon 05 Jan 19:20 UTC	Briefing	Completed	5.2 s	None	Training period
R-0272	Mon 05 Jan 19:15 UTC	Briefing	Completed	1.8 s	None	Training period
R-0271	Mon 05 Jan 19:13 UTC	Briefing	Completed	5.3 s	None	Training period
R-0270	Mon 05 Jan 19:06 UTC	Briefing	Completed	3.1 s	None	Training period
R-0269	Mon 05 Jan 19:05 UTC	Briefing	Completed	4.7 s	None	Training period
R-0268	Mon 05 Jan 19:05 UTC	Briefing	Completed	2.3 s	None	Training period
R-0267	Mon 05 Jan 19:02 UTC	Briefing	Completed	7.1 s	None	Training period
R-0266	Mon 05 Jan 19:00 UTC	Briefing	Completed	3.9 s	None	Training period
R-0265	Mon 05 Jan 18:58 UTC	Briefing	Completed	5.6 s	None	Training period
R-0264	Mon 05 Jan 18:55 UTC	Briefing	Completed	2.8 s	None	Training period
R-0263	Mon 05 Jan 18:54 UTC	Alternate-airport check	Completed	958 ms	None	Over before 1 s
R-0262	Mon 05 Jan 18:54 UTC	Briefing	Completed	4.3 s	None	Training period
R-0261	Mon 05 Jan 18:53 UTC	Briefing	Completed	4.1 s	None	Training period
R-0260	Mon 05 Jan 18:52 UTC	Briefing	Slow (over 8 s)	8.9 s	None	Training period
R-0259	Mon 05 Jan 18:49 UTC	Briefing	Completed	3.6 s	None	Training period
R-0258	Mon 05 Jan 18:49 UTC	Briefing	Slow (over 8 s)	8.2 s	None	Training period
R-0257	Mon 05 Jan 18:48 UTC	Alternate-airport check	Completed	2.6 s	None	Training period
R-0256	Mon 05 Jan 18:45 UTC	Flight plan	Completed	9 ms	n/a	Over before 1 s
R-0255	Mon 05 Jan 18:30 UTC	Briefing	Completed	4.6 s	None	Training period
R-0254	Mon 05 Jan 18:28 UTC	Briefing	Completed	6.5 s	None	Training period
R-0253	Mon 05 Jan 18:23 UTC	Briefing	Completed	3.5 s	None	Training period
R-0252	Mon 05 Jan 18:22 UTC	Briefing	Slow (over 8 s)	11.8 s	None	Training period
R-0251	Mon 05 Jan 18:14 UTC	Briefing	Completed	2.8 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.