Skip to content

Automation WhatsApp document auto-send (1.7.0) — Production Readiness Audit ​

FieldValue
Date2026-10-08
Re-verified2026-10-08 — Pest WA auto-send + outside window + catalog 1.7.0; headed Playwright test:e2e:automation:headed 1/1 (WA checkbox persist)
StatusGo for production
ScopeOptional auto_send_whatsapp on generate_quotation / generate_invoice; catalog automation 1.6.0 → 1.7.0
CompanionAutomation deployment · Document auto-send 1.6.0 · CHANGELOG

Executive summary ​

Automation 1.6.0 emailed PDFs via auto_send. 1.7.0 adds independent auto_send_whatsapp: after create, status transitions (Sent / Unpaid) once when either channel is on, then queues the PDF as a WhatsApp document into an open 24-hour conversation (AutomationDocumentWhatsAppSender → queueMedia). Soft-gates WhatsApp Cloud entitlement. Missing conversation / closed window / missing actor fails the run (same strictness as missing email).

GateResult
Platform freezePass
WA off → draft / email path unchangedPass
WA on → send status + media jobPass (Pest)
Outside 24h window → failed runPass
Module missing → failed runPass (entitlement check)
Catalog migrate-only 1.7.0Pass
SPA checkbox soft-gated by whatsapp-cloudPass (headed e2e: hidden when revoked, persist when entitled)
Headed Playwright one-sessionPass (test:e2e:automation:headed 1/1)
Live Meta handset smokePost-deploy QA

Upgrade & staging smoke ​

  1. php artisan migrate --force — catalog → 1.7.0 (do not db:seed).
  2. Entitle WhatsApp Cloud + Storage; confirm Horizon whatsapp-outbound.
  3. Builder: Generate Quotation/Invoice → enable WhatsApp auto-send → trigger with contact phone matching an open conversation → PDF document queued.
  4. Closed window / no conversation → run Failed.

Rollback ​

Catalog down → 1.6.0 with matching code. Config keys auto_send_whatsapp are ignored by older code.

Official documentation for the EloSync SaaS Platform.