Capture the request without promising capacity
Record party size, desired date and time, contact channel, supplied seating need and the version received.
Workflow blueprint
A reservation request should never masquerade as a confirmed table
An educational confirmation and seating handoff, not a live booking engine, table optimiser, messaging service, deposit processor or accessibility decision.
Keep party size, requested time, seating questions, capacity review, offered slot, guest response, confirmed version, later amendments, arrival outcome and released plan distinct.
TL;DR — Keep party size, requested time, seating questions, capacity review, offered slot, guest response, confirmed version, later amendments, arrival outcome and released plan distinct.
Review and offer a bounded arrangement
Name the capacity reviewer, proposed time, response deadline, unresolved feature question and reason an alternative was offered.
Confirm the exact accepted version
Preserve guest response, confirmation reference, party details, authorised notes and any later amendment as a new controlled state.
Hand arrival or release to the floor
Record arrival report, late or changed party question, seating handoff, cancellation or release reason without inventing a service outcome.
Page-specific decision aid
A reservation request, capacity review, offer, confirmation, amendment, arrival and release card
The card follows a party of six requesting a peak time, a seating-feature question, an alternative offer, guest confirmation, duplicate web request, increase to eight, reviewer-approved amendment, late-arrival call, partial arrival, floor handoff and release of the unused planning hold.
- ✓A requested time is not a confirmed table.
- ✓A seating question is not a promised accommodation.
- ✓An arrival report is not proof of service.
Scope first
What Codeblix would confirm before implementation
This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.
- ✓Requests offers and confirmations remain different states
- ✓Guest supplied needs use restricted role visibility
- ✓Amendments identify the confirmed version they replace
- ✓Live tables messages deposits accessibility waitlists marketplaces and no-show proof excluded
Relevant Codeblix foundations
Review the existing product areas that support the proposed workflow.
Use the related planning tools
Run the operational calculation, save the result in the URL and share it with your team.
Map this workflow to your operation
Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.
Discuss your workflow