Server or floor team exception response restaurant playbook
Direct answer
Connect table context, guest questions and order handoff without changing protected settings. During exception response, contain a failed, conflicting or unsafe workflow without hiding the evidence needed to resolve it.
Example ownership
- Table identity checks
- Guest QR fallback
- Order-context clarification
- Floor exception reporting
Required evidence
- Incident time
- Affected records
- Fallback action
- Named follow-up owner
Shift-moment sequence
- Identify the exact affected channel, record and first known time.
- Stop duplicate actions or new promises where evidence is unreliable.
- Activate the approved fallback within the role’s authority.
- Record facts, notify the accountable lead and assign reconciliation.
Escalation and stop condition
Emergency, safety, security, suspected data exposure and unresolved payment events override routine software steps.
Role boundary: Floor access should not silently include pricing, payment-gateway, role or site-wide settings.
Wobistro access boundary
Use individual staff accounts and grant the smallest useful module set. Wobistro permissions support the workflow when enabled; they do not define training, legal authority, food-safety responsibility or emergency command.
Verify allowed and restricted paths with a non-owner test account after changing the active plan, modules or role.