Choose the part of your workflow that is hardest to see. Each page shows how that handoff works, what is already proven, and what still needs a provider.
Find my workflow leakEvery inquiry is written to a durable record before any notification attempt runs. A dropped notification cannot erase the inquiry, and a review task can retain a next action and due date even when no provider is configured.
Live intake; provider pending →Maps the handoff from a booking request to a named next action and owner. Until a calendar provider is connected and verified, every booking stays a reviewed request rather than a confirmed slot.
Request-only; provider pending →Validates and records every public form submission before any notification is attempted, with a hidden spam trap and no administrative credentials shipped to the browser.
Operating locally today →A future system category for first-response triage. Scope, provider, and disclosure rules are not yet approved, so this category has no connected behaviour or claimed outcome.
Not yet built →IronWake does not describe a planned category as though it were connected, and does not describe a request-only flow as though it were a live confirmation.