Moderate evidence
Published recordBusinessGood Space
More
Efficiency Without Quality? A Six Sigma DMAIC (Define, Measure, Analyze, Improve, Control) Field Study of Sub-Intent Library Curation in a Live Airline Chatbot
- Truvace record
- TRV-2026-3097raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- 9c47d17dc1ef…check it
This study asks whether the Six Sigma DMAIC (Define, Measure, Analyze, Improve, Control) cycle can improve utterance capture in a live enterprise chatbot, and how much of the change is attributable to the intervention during a concurrent migration to large language model (LLM) components. Turkish WhatsApp utterances of Turkish Airlines’ TK Assistant (80,295 utterances, January–July 2025) was analyzed; utterance capture scores (success threshold 0.95) were graded on a five-level scale, with 0.95 as the success th…
The gain
In a field study of Turkish Airlines' TK Assistant WhatsApp chatbot, 17 of 22 recurring added texts were captured as exact matches at first recurrence, versus none of eight recurring non-added controls.
What this doesn’t fix
The drop in successful capture rate from 21.04% to 16.11% cannot be separated from the concurrent migration to large language model components, so the intervention's effect on overall performance is uncertain.
Sources
1 on file- Applied Sciencesdoi:10.3390/app162211506
Cite this record
v1Truvace Impact Record TRV-2026-3097, v1: “Efficiency Without Quality? A Six Sigma DMAIC (Define, Measure, Analyze, Improve, Control) Field Study of Sub-Intent Library Curation in a Live Airline Chatbot.” Truvace, 2026-11-22. /record/TRV-2026-3097 (accessed on the day you copy it). sha256 9c47d17dc1ef796c…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-3097 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.
ace