Two kinds of conflict, each with a clear rule
- Booked elsewhere on the network: a guest on your book holds another active reservation on the same night at a different ConTROLL venue. You see that the conflict exists. The other venue's name and booking details are never shown.
- Overlapping bookings here: the same guest holds two active reservations at your venue with seating times within two hours of each other. Matching uses the guest's identity in your own records, not a name alone.
Where your team sees it
Conflicts appear in the Daily Report, on the reservation card and as a dashboard alert for tonight's book. They are generated from the same stored rules every time, so the warning is still in the Daily Report when the AI summary is unavailable or out of date.
What teams do with it
- Make a discreet courtesy call to confirm the party size and arrival. Guests often cancel the booking they do not need.
- For an overlap at your own venue, confirm whether both bookings are intended.
- Release or re-offer the table if the guest confirms they are dining elsewhere.
What it does not do
- It does not accuse the guest of anything. A double-booking is a prompt to confirm, not a score against them.
- Walk-ins, canceled reservations and no-shows never trigger a conflict.
- Network conflicts are compared by service date, and only against other ConTROLL venues. They cannot see bookings at restaurants that are not on ConTROLL.
- A conflict does not change a guest's risk level or VIP standing.