Call recorder
Voice calls are recorded on both sides, and the time from the end of each question to the first sound of the answer is measured on the recording itself, never by ear.
- When it runs
- During every voice call of the test
- Used in
- 13 reviews
- Runs on
- My browser on the call page, recording both sides
What the call recorder is
A call that answers after five seconds of silence feels broken whatever the voice sounds like. The recorder captures my side of the call and everything the page plays, and writes one stereo file: my questions on one side, the companion on the other. The answer time is then measured on that file by a voice detector, so the figure does not depend on anyone's reaction time.
How it works
- The call is started from the call page with the test account signed in, the way the app expects.
- After the greeting I ask the first question, wait for the first sound of an answer, and wait for silence before the next question; the same questions, in the same order, on every app.
- Throughout, every sound the page plays is captured, whatever route it takes through the browser.
- After the call the recording is converted to a sound file and a voice detector marks where each question ends and each answer starts. Each question is paired with the first answer after it, within a limit, and the gap is the answer time.
- The in-page sound meter kept its own times during the call; it is the cross-check, and the recording is the figure.
- The answer times of every call are pooled: median, fastest, slowest, the slowest one in ten, and the share under a second, with the questions that got no separate answer counted and listed.
- The recorder is checked against a fake call page that answers after a known delay; the measurement comes out within a fraction of a second of it.
What it records
- Per call
- The two-sided recording, an event log, screenshots, and for every question its start and end, the answer's start and end, the gap, and whether it was answered.
- Per app
- The pooled figures and the number of questions without a separate answer.
What it cannot catch
- The voice detector adds a small delay of its own before it declares an answer has started, in the order of a tenth or two of a second, the same for every app.
- A reply that runs straight into the next question has no separate answer and is counted as such rather than given a time.
- Interruptions, when the caller talks over the companion, are not measured.
- An app that plays its audio in a way the browser will not let a page capture gives a silent recording; the review says so when it happened.
Where it was used
Every published review that ran this checker, with the figure it produced there, read from the review’s own data. Each figure opens the test results behind it.
| Review | Figure | Tested |
|---|---|---|
| 1.93 s Median (recording) | 13 Oct 2026 | |
| 8.65 s Median to first sound | 18 Oct 2026 | |
| 45 of 45 Questions answered | 18 Oct 2026 | |
| test results | Invalid Date | |
| 1.45 s (24 answers) Median latency, all answers | 19 Oct 2026 | |
| 3.96 s Median latency | 16 Oct 2026 | |
| 2.34 s (45 questions) Pooled median | 14 Oct 2026 | |
| 1.72 s Median | 15 Oct 2026 | |
| 7.27 s (40 questions) Pooled median | 14 Oct 2026 | |
| 1.72 s Median | 15 Oct 2026 | |
| 4.26 s Median latency | 15 Oct 2026 | |
| 3.34 s Median latency | 16 Oct 2026 | |
| 5.34 s Median latency | 18 Oct 2026 |
Review
- Tested
- 13 Oct 2026
- Tested
- 18 Oct 2026
- Tested
- 18 Oct 2026
- Figure
- test results
- Tested
- Invalid Date
- Tested
- 19 Oct 2026
- Figure
- 3.96 s Median latency
- Tested
- 16 Oct 2026
- Tested
- 14 Oct 2026
- Figure
- 1.72 s Median
- Tested
- 15 Oct 2026
- Tested
- 14 Oct 2026
- Figure
- 1.72 s Median
- Tested
- 15 Oct 2026
- Figure
- 4.26 s Median latency
- Tested
- 15 Oct 2026
- Figure
- 3.34 s Median latency
- Tested
- 16 Oct 2026
- Figure
- 5.34 s Median latency
- Tested
- 18 Oct 2026
The other checkers for ai girlfriend
Written by Miles Foster, Owner and tester, RankDude. How RankDude tests and grades is on the methodology page.