Upload & run · Ozonetel

Upload & run everything happens in the background — you can close this tab

Add more calls from Excel

The same Ozonetel export format. Calls already in the system are recognised by call id and skipped, so re-uploading a bigger file only processes what is new.

Or run one call

Paste a recording URL. Everything else is optional — but campaign decides which pitch rubric the call is scored against, so fill it in if you know it.

Is anything waiting to be processed? every call, and what is holding it up

Nothing is waiting. All 2645 calls are in a final state, which is why a new run finishes immediately at 0% of 0 — it is not broken, there is genuinely nothing left to do. Uploading the same export again will not change this: only rows with a call id the system has never seen create new work.

Calls	State	What it means
2124	Transcribed and scored	Finished. Nothing further will happen to these.
257	Transcribed, then excluded from scoring	There was no scoreable conversation in the call - reported as n/a rather than as a low score.
227	Recording too short to transcribe	Under the 5-second floor - the call connected but almost nothing was recorded. No tokens were spent. Only a longer recording makes these eligible again.
26	Recording could not be downloaded	The url did not return audio. It is not attempted again; to try one of these once more, paste its url into “run one call” above.
9	Transcript rejected as fabricated	The transcript described audio that is not in the recording, so nothing was stored. Re-running will not change it while the file is the same.
2	Recording gone from S3	The url answers 'not found'. Ozonetel purges its recordings after about 90 days, so there is nothing left to fetch.

Campaigns with no pitch type calls here are transcribed but cannot be scored until someone says which pitch they were meant to follow

Every campaign is mapped. Nothing is being held back from scoring for want of a pitch type.

Recomputes every score from the current rubric and campaign map. No tokens — it reads the transcripts already stored.

Tidy up data that cannot become useful — and what to repair instead of delete

A call with a transcript is never deleted here, whatever else is wrong with it — the transcript cost real tokens and in most cases the recording has since been purged from S3. Where a problem is fixable, this offers the repair rather than removal.

What	Why it is here	Action
Calls whose id Excel destroyed	The call id was saved in scientific notation, so the real digits are gone. These match no recording and can never be scored or repaired - a corrected file has to be uploaded instead.	nothing to do
Calls with no recording, never transcribed	The export carried no recording link for these, so there is nothing to transcribe. If the link was simply in a column we misread, re-upload the file instead - that restores the link and queues them.	nothing to do
Campaign or agent holding a number	These came from a file whose columns were read by position. The value is an Excel time, not a campaign. Blanking it clears the filters; re-uploading the file restores the real names instead, which is better if you still have it.	nothing to do
Upload records for files that could not be read	The file was rejected or held nothing, so no calls came from it. The row is only a note of the attempt.	nothing to do
Runs that did no work	A run that started when nothing was pending. It processed nothing, so the row records only that someone pressed the button.	nothing to do

Before deleting anything that came from a mis-read file, try re-uploading that file. Columns are matched by header now, so a re-upload restores the real campaign and agent names and puts calls whose recording link was misread back in the queue. Deleting them throws away recoverable calls.

Uploaded files what each file brought in — and, when nothing happened, why

File	Sheet	Rows	New	Already known	Calls from this file	Transcribed	Result	Uploaded	Remove
no files uploaded yet

Runs newest first · a run marked interrupted had its process killed, and simply re-running resumes where it stopped

#	What	Stage	Status	Progress	Done	Failed	n/a	Started
22	waiting work ui:run	finished	done	100% of 2 stage-items	2	0	0	28 Sep 2026, 04:27
21	waiting work ui:run	transcribe	interrupted	0% of 1 stage-items	0	0	0	27 Sep 2026, 16:27
20	waiting work ui:run	finished	done	0% of 1 stage-items	0	1	0	26 Sep 2026, 16:28
19	waiting work ui:run	finished	done	97% of 34 stage-items	33	1	0	26 Sep 2026, 04:27
18	waiting work ui:run	finished	done	99% of 2233 stage-items	2017	32	184	25 Sep 2026, 15:37
17	waiting work ui:run	transcribe	interrupted	84% of 993 stage-items	833	4	5	25 Sep 2026, 13:37
16	waiting work ui:run	transcribe	interrupted	0% of 995 stage-items	0	0	2	25 Sep 2026, 04:27
15	waiting work ui:run	transcribe	interrupted	0% of 996 stage-items	0	0	1	24 Sep 2026, 17:39
14	tmp7mey1osp.xlsx upload:excel	transcribe	interrupted	0% of 1000 stage-items	0	0	4	24 Sep 2026, 17:22
13	added MANUAL_DIA9e2de5d9ee44f324be677 + anything else pending upload:call	finished	done	100% of 2 stage-items	1	0	1	17 Sep 2026, 11:42
12	added MANUAL_DIA9e2de5d9ee44f324be677 + anything else pending upload:call	finished	done	7% of 29 stage-items	1	27	1	17 Sep 2026, 11:24
10	Sep1-1040s.xlsx upload:excel	finished	done	99% of 2401 stage-items	1582	28	791	11 Sep 2026, 17:49
9	Sep1-10.xlsx upload:excel	finished	done	97% of 592 stage-items	339	18	235	11 Sep 2026, 17:06
8	Aug1-5.xlsx upload:excel	finished	done	100% of 631 stage-items	415	0	216	07 Sep 2026, 12:32
2	single call MANUAL_DIA9e2de5d9ee44f324be677 upload:call	finished	done	200% of 4 stage-items	7	0	1	04 Sep 2026, 10:08
1	ozonetel transcripts.xlsx upload:excel	finished	done	200% of 296 stage-items	519	3	73	03 Sep 2026, 13:51