Reconcile reservation status across the phone and booking systems

Name the states you actually use

Booked, confirmed, cancelled, seated and no-show can mean different things across products and restaurant workflows. Write a field mapping rather than assuming every platform uses the same labels. The test pack uses ordinary operational language; adapt it to the exact states supported by your configured system.

Separate booking status from communication status. A reminder being delivered does not mean the guest reconfirmed, and a missed call does not mean the reservation was cancelled. If the phone integration cannot see a state, it should not imply that it can.

Test manual edits and timing

• Staff change the reservation directly in the book before the guest calls again.
• A cancellation arrives before an older confirmation event.
• Two authorized users attempt different changes close together.
• A delayed response arrives after staff have resolved the exception.

The expected result should be a documented conflict rule and a verifiable final record. A “last update wins” policy is only meaningful if clocks, timestamps and allowed writers are understood. Ask the provider how version conflicts are surfaced and whether staff can see them.

Reconcile at the right level

Daily booking counts can match while the wrong reservations have been changed. Review linked records for representative lifecycle cases, including party-size changes and cancellations. Inspect the final date, time, venue, party size and status rather than only the number of bookings.

Keep an exception list with a named owner and a next action. An integration team may investigate logs, while the shift lead needs a guest-facing answer immediately. Define how those responsibilities connect so a technical investigation does not leave the host stand without a usable state.

Use evidence, not assumptions

For every fixture, capture the before state, the operation, the resulting state and the relevant system references. Note the environment and test time. If a screenshot omits the venue or date, it may not prove the intended scenario. Redact unnecessary guest information before sharing evidence.

The workbench requires an evidence reference for a pass to count as documented. It does not inspect that evidence or verify its authenticity. A reviewer must still confirm that the referenced material supports the stated result.

A status conflict worth testing

Illustrative case: staff cancel a test booking in the reservation book, then an older confirmation event arrives. Ask which version wins and inspect the final record. The caller-facing system must not claim the booking is active solely because it received a delayed message.

Loman’s SevenRooms synchronization article provides company-stated integration context. Your own test must establish the configured timing and conflict rule; the public article is not an audit of event ordering.