Follow a WhatsApp message from webhook to outcome.
Real runtime events are joined with durable webhook and state records. Select a message to see exactly which gates it crossed and where it stopped.
Recent traffic
Choose a message from the index.
Its exact route, timing, decisions, writes, and safe exits will unfold here.
—
Visited stages
The automation is designed to stop safely.
These are the invariants that shape every branch in the map. When confidence or state is uncertain, the system asks or exits before mutation.
Clean means clean twice.
The target business row and column X are checked before the batch and again immediately before each write.
One winner, no close rival.
The best update candidate must be at least 70%; every other candidate must be no more than 30%.
OCR cannot invent intent.
New-call and update triggers—and caption business identity—come from caption text only. OCR is reserved for document intake.
Originals, never overwrites.
Identical file hashes are skipped. Update numbering is shared across extensions and existing files remain untouched.
A person chooses the target.
Up to five candidates become a numbered WhatsApp decision. No candidate folder is mutated while the choice is pending.
Record first, process second.
The raw webhook is durably appended before work starts. An unexpected failure is visible and explicitly retryable.