Completed
The appointment happened as scheduled.
Menu
A booking request and a confirmed slot are not the same state.
This system maps the handoff from a booking request to a named next action and owner, and separates request-only intake from real provider confirmation. Capability, demo status, and provider status are listed below.
Only a real confirmation reaches Confirmed.
A visitor submits a booking request. Nothing is confirmed yet: this is a request, not a hold on a calendar.
What a confirmed slot can become.
Cancelled
The visitor or the business cancelled the confirmed slot.
Rescheduled
The confirmed slot moved to a new time, tracked as a state change, not a new unrelated record.
No-show
The confirmed slot passed without the visitor attending.
What this system delivers.
Request → review → confirmation state machine
Five pre-confirmation states and four post-confirmation states. The transition into Confirmed only happens after a real provider or owner action.
Request-only UI works on this site today
The booking request form records preference and starts a reviewed intake path. Confirmation is explicitly pending until a provider or owner approves.
Calendar provider connection pending
A verified calendar provider is required before Confirmed state can fire. Cal.com, Google Calendar, or similar would be the integration target.
Capability ready; provider-dependent part awaits account
The implementation is built. Production confirmation for any specific business waits for the matching calendar provider account to be linked and verified.
Booking Certainty Starter
Lite tier implementation fee:
India₹12,999
International$199
Lite covers the agreed architecture. Standard and Pro add depth, integrations, and verified provider setup. Domain, hosting, AI compute, phone numbers, messaging, and calendar provider costs are billed directly by their providers and are never marked up by IronWake.