Sample report. Built from the public MultiWOZ 2.2 run of 7 November 2026, not from a customer. A real audit reads your agent’s last week of conversations.
Unknown Ops · audit report
What your agent couldn’t answer
1 · Fix with one reply ENTRY
Each of these is a fact the owner or a shift manager can supply. Each one becomes a single email: the question, how often it was asked, and a reply box.
| # | Question customers couldn’t get answered | Times | Domain |
|---|---|---|---|
| 1 | Entertainment venue in the centre | 106 | attraction |
| 2 | Multiple-sports venue outside the east | 102 | attraction |
| 3 | Entrance fee / admission price not in the data | 74 | attraction |
| 4 | College outside the centre / west | 38 | attraction |
| 5 | Theatre / cinema in an area with none | 36 | attraction |
| 6 | African restaurant in the wrong area / price | 34 | restaurant |
| 7 | Swimming pool in an area with none | 33 | attraction |
| 8 | Concert hall outside the centre | 27 | attraction |
| 9 | Architecture outside the centre | 26 | attraction |
| 10 | Nightclub outside the centre / south | 25 | attraction |
| 11 | Vietnamese restaurant in the wrong area / price | 14 | restaurant |
| 12 | Lebanese restaurant in the wrong area / price | 12 | restaurant |
| 13 | Japanese restaurant in the wrong area / price | 11 | restaurant |
| 14 | Turkish restaurant in the wrong area / price | 11 | restaurant |
| 15 | Thai restaurant in the wrong area / price | 10 | restaurant |
| 16 | Boating in an area with none | 10 | attraction |
| 17 | Park in the west | 10 | attraction |
| 18 | Korean restaurant in the wrong area / price | 9 | restaurant |
| 19 | Seafood restaurant in the wrong area / price | 6 | restaurant |
The email this produces · example for gap “Entrance fee / admission price not in the data”
Asked 74 times, never answered
“What is the entrance fee?” Reply with the answer and we’ll publish it to your agent.
↩ Reply2 · Needs a tool TOOL
No knowledge entry can fix these. Each needs a live lookup or an action, such as checking availability. They are reported as integration work, never sent to a shift manager as a question.
| # | What customers couldn’t get | Times | Domain |
|---|---|---|---|
| 1 | Booking slot unavailable (room or table) | 1,065 | hotel, restaurant |
| 2 | Hotel search: no match for the requested combination | 711 | hotel |
| 3 | Train: no service at the requested time / route | 97 | train |
| 4 | Restaurant search: common cuisine, no match for price / area | 78 | restaurant |
| 5 | Buy / reserve attraction tickets | 5 | attraction, train |
3 · Left out, with the reason
38 “No [cuisine] restaurant” rows, 745 occurrences: a dataset artifact from an ontology that lists cuisines with no venues. Excluded from the 24, and listed in full in gap_table.md.
Domains are the dataset’s (Cambridge, UK, booking dialogue), not target customers. What this run does not show is stated on the method page.