Requested
Customer submitted the form. No provider has acknowledged the slot.
Form submission alone can never reach this state.
Preparing the next view.
The page is loading. No inquiry, booking, or provider action is happening in the background.
The page is loading. No inquiry, booking, or provider action is happening in the background.
Most booking systems silently confirm when the form submits. IronWake keeps the gap visible: requested means requested, confirmed means a provider acknowledged it. Nothing in between is described as confirmed.
A booking record is one of three things: requested, confirmed, or disputed. Each transition is logged with the evidence that produced it. Form submission is never enough to reach the confirmed state.
Customer submitted the form. No provider has acknowledged the slot.
Form submission alone can never reach this state.
The capability list below is what the system is built to do. The status column tells you which of those capabilities are wired to a verified provider today.
Each capability is documented in the audit; none is described as live without provider evidence.
Each capability is documented in the audit; none is described as live without provider evidence.
Each capability is documented in the audit; none is described as live without provider evidence.
Each capability is documented in the audit; none is described as live without provider evidence.
Operators stop chasing phantom bookings. The dashboard shows the actual state of every slot. No fabricated metrics, no fake no-show rates.