After a reservation system outage, start with future bookings that may have been created, changed, or canceled during the affected period. Compare the restored reservation list with independent evidence, then contact guests whose plans cannot be verified. Do not treat a restored screen alone as proof that every booking is correct.
Give one person responsibility for the list, another for guest replies, and a manager authority to resolve conflicts. Prioritize the next service first, but continue checking later dates until the full affected window is reconciled.
Identify the dates and records that need attention
Mark the time when records were last known to be reliable and the time when staff could resume checking bookings. Include a buffer if either time is uncertain. Then identify every future service date with a booking that could have been made or changed in that interval. The affected booking dates may extend well beyond the day of the outage.
Pull the restored list using authorized access. Compare it with whatever independent records your restaurant actually has: a dated reservation export, an earlier printed list, confirmation emails, phone notes, or a booking-channel record. Record when each source was created. A printout from before the outage can establish an earlier booking, but it cannot prove that the guest did not later change it.
For each potential booking, capture the guest name, local date and time, party size, status, booking channel, and a reliable way to contact the guest. Include relevant special requests where appropriate. Use the contact details attached to the strongest available evidence; if two sources disagree, flag the difference rather than guessing. Limit access to the working list and follow your restaurant's guest-data procedures.
Ask your reservation provider what recovery covers: restored bookings, edits, cancellations, and records from connected channels may not all have the same recovery point. For a restaurant reservation system, also ask whether direct website bookings and Google bookings, where available, can be reviewed separately. A channel count is useful, but it does not identify which individual guest needs a call.
Reconcile each booking against independent evidence
Use the following fictional worksheet. The outage affected changes made from Friday at 4 p.m. until Saturday at 10 a.m. The team has a restored list, a printout made Friday at 3 p.m., and individual confirmation records. The table shows four future guest parties, not four physical tables; seating capacity must be checked separately.
| Guest and requested service | Evidence | Working status | Next action |
|---|---|---|---|
| Lee, Tuesday 6 p.m., party of 2 | Restored record matches a confirmation issued before the outage | Confirmed for this review | No correction needed; contact only if the restaurant chooses to reassure guests |
| Diaz, Tuesday 7 p.m., party of 4 | Restored record says 6 p.m.; later confirmation says 7 p.m. | Uncertain time | Check capacity for both times and ask the guest |
| Patel, Wednesday 6:30 p.m., party of 3 | Confirmation exists, but no restored record appears | Uncertain booking | Check capacity and contact the guest before adding a booking |
| Jones, Wednesday 7 p.m., party of 2 | Restored booking appears; phone note says the guest requested cancellation during the outage | Uncertain status | Check the note and ask whether the guest still plans to come |
In this example, the expected result is one matched record and three cases requiring resolution. The Diaz confirmation is later than the conflicting restored record, but the team still checks with the guest and confirms it can seat the party at the requested time. The Patel confirmation is evidence of a request, not permission to promise a table before checking the floor plan. The Jones note is not treated as a completed cancellation without further confirmation.
Match records using more than a name. Two guests can share a surname, and one guest can have more than one booking. Compare date, time, party size, contact details, and any reference number. Keep the original evidence and record who made each decision. If a booking was edited, note which version is being used and why.
Reconcile counts as a second check: count matched, uncertain, canceled, and duplicate entries by service date. Counts can reveal a missing record, but equal totals do not prove the right guests are on the list. Resolve individual discrepancies before marking a service complete.
Send different messages for confirmed and uncertain bookings
For a matched booking, a reassurance message is optional. If you send one, state the details you have verified and give the guest a way to report a difference. Avoid suggesting that every booking in the system has been checked when only this record has been reviewed.
Confirmed example: “Hi Lee, we're looking forward to seeing your party of 2 on Tuesday at 6 p.m. If those details don't match your plans, please call us at [restaurant number].”
For an uncertain booking, explain the specific question without assuming the guest is at fault. Offer a response route staffed by someone who can check availability. Do not put sensitive details in a message, and use the contact channel the restaurant is authorized to use.
Uncertain example: “Hi Diaz, we're checking a reservation for Tuesday for a party of 4. We have different times in our records. Were you expecting 6 p.m. or 7 p.m.? Please call us at [restaurant number] so we can confirm availability.”
For Patel, the message should ask whether the guest still expects to dine at 6:30 p.m. and say the restaurant will confirm availability. For Jones, ask whether the cancellation request still reflects the guest's plans. Until the answer is resolved, neither an unverified booking nor an unverified cancellation should be presented to staff as final.
Choose an outreach order based on the next service, the likelihood of a conflict, and how long the guest needs to respond. A phone call may be more useful than an email shortly before opening. Record the attempt and its result; a message sent is not the same as a guest reached. If the address or number is doubtful, do not send booking details to it until staff can verify it belongs to the guest.
Assign owners, track replies, and escalate conflicts
Name a reconciliation owner for the master list. Give the host or another designated employee responsibility for outreach, and identify the manager who can approve an alternative time or seating arrangement. At shift change, hand over the unresolved list and the next action for each guest. Avoid separate unchecked copies that can diverge.
Track the evidence reviewed, current status, contact attempt, reply, decision, and person responsible. Use clear statuses such as “needs review,” “contact attempted,” “guest reached,” and “resolved.” Set a callback deadline based on the service date. If a guest has not replied by then, the manager should decide how to handle the remaining uncertainty and brief the host; silence is not confirmation or cancellation.
Before offering a time, check the physical floor plan, existing parties, party sizes, and seating duration. A party of four is not necessarily one available table: the restaurant may need to combine tables, and doing so can affect other reservations. If the requested time cannot be accommodated, offer only alternatives the manager has checked. Record the guest's choice and update the working list through the approved process.
Practice the handoff with fictional records before relying on it. In a simulation, staff should identify the three uncertain cases in the worksheet, route each to an owner, draft the appropriate message, and show where a reply and manager decision would be recorded. Use a practice list and drafts only: do not send guest messages, take a real payment, or dispatch a courier. This is a simulated check, not a live service pilot.
Pass: every uncertain case has an owner and next action; no unverified time is described as confirmed; and the manager checks seating capacity before offering a table. Fail: a case has no owner, a sent message is counted as a reply, or a booking is added or canceled solely to make totals match. Correct the process and repeat the simulation before a live service pilot, which should use the restaurant's normal guest-contact controls.
Keep the final service list accessible to the host and manager, and use your restaurant management software procedures to decide where the authoritative updates belong. For a separate look at the operational cost of guests who do not arrive, see the guide to measuring reservation no-shows.
Next step: Compare this worksheet with Fleksa's reservation system and ask how your team can review booking channels, access records, and document corrections. Confirm current availability and your intended workflow before choosing a setup.
Frequently asked questions
Should we contact every guest after an outage?
Not necessarily. Prioritize guests whose future booking details or status cannot be verified. You may also choose to reassure guests with matched records, provided the message accurately states what you have checked.
What if the guest does not respond?
Record the attempt, set a callback deadline, and escalate to the manager before service. Do not treat silence as confirmation or cancellation. Brief the host on the unresolved case and the manager's plan.
Is a restored reservation list enough to confirm a booking?
Not by itself when an outage may have affected recent changes. Compare the individual record with independent evidence, including its date and time, and resolve conflicting information with the guest when necessary.
