Kept working in deliberate failure drills[6]
During the tests we caused failures on purpose. These finished normally without any action from the user.
- 61 / 62
- live test meetings
- 37 / 38
- after-meeting re-reads
For teams and enterprises
Start with your team’s requirements.
What we measured
Our own tests, on public recordings with human transcripts. Lower error rates are better. Each figure carries how it was tested and when.
Tests and dates
- [6] Failures caused on purpose during the same tests. Live: 61 of 62 testable cases completed normally (in one case, one line out of four was lost to an unrelated cloud error). After-meeting re-read: 37 of 38 cases completed normally; one case did not complete. Tested October 2026. How we measure
- [9] All tests used public recordings with human transcripts. No customer recordings were used. Results are from KaigiFlow’s own tests in October 2026 and describe those tests, not every meeting. How we measure
Device availability, deployment and data-handling requirements deserve a clear conversation.
What a team can discuss with us
- Deployment
- Recording policies
- Language coverage
- Data handling