Form webhook
A validated POST endpoint is implemented; production row, task, and owner readback remain separately verified.
The page is loading. No inquiry, booking, or provider action is happening in the background.
When a real form submission lands after hours, IronWake can queue it and attempt an owner-email reply. Provider-generated delivery, durable outbox/CRM linkage, and named-assignee routing remain separate proof gates.
Pick a channel to see the implementation and proof state. A configured adapter is not the same as provider-generated delivery or CRM proof.
A validated POST endpoint is implemented; production row, task, and owner readback remain separately verified.
The recovery chain is documented as five ordered steps. Each step shows the documented capability and whether it is wired to a verified provider today, so the audit can start from a clear target.