OpenTable's Summer Tools Target Table Rules and Guest Recognition

OpenTable announced more than 20 new or enhanced restaurant features on August 26, 2026. Three functions deserve different kinds of scrutiny before operators put them to work.

Table Automations adjusts table minimums according to live demand. Group Guest Visit History provides cross-location guest insights. Conversational Reporting, for questions in ordinary language, was in testing. Those are the descriptions in OpenTable's announcement.

For an operator, the useful starting point is the decision each function changes. A feature that alters bookable inventory needs different oversight from a profile that helps a host recognize a guest.

Table rules need an operating owner#

If an automated rule changes the party sizes accepted at a table, it changes who can book that space. That makes configuration a service decision with revenue consequences.

Consider an illustrative four-seat table approaching service with no reservation. Making it available to a smaller party may help fill unused capacity. Doing so too early could also remove an option for a later larger party. The right decision depends on demand, timing and the restaurant's willingness to accept that trade.

That example does not establish OpenTable's exact configuration options. It identifies what a manager needs to understand before activating an automated rule: its trigger, the inventory it affects and the person authorized to intervene.

For a trial, managers could record rule changes and check them against the reservation book. They could track bookings made after each change, whether those guests arrived and any staff intervention. Counting automated actions alone would miss the work shifted back to the host.

OpenTable cited internal data showing average monthly savings of 4.5 hours in an initial test and more than 2 million automations since the test phase. A site's return would depend on the time its staff previously spent adjusting rules and the work required to monitor the changes.

A familiar guest at a new location#

A guest arriving at a new location may already know the restaurant group well. Prior visits can give the host a starting point for the welcome.

A host needs to decide which information belongs in the interaction. A useful visit record might help explain an existing preference. An irrelevant or outdated note can lead a host into an awkward assumption. The review process should therefore include who can add information, who can see it and how a mistaken record is corrected.

The release does not detail the permission and correction controls, so a group would need to establish how those tasks work.

The value also depends on timing. Information visible during a quiet afternoon does little for a host who cannot find it while seating several parties. A small rollout could observe whether staff actually use the history during service and whether it changes a specific hospitality action.

Reporting still needs a checked answer#

A reporting trial needs a known answer to compare against. Operators considering this tool should first confirm whether they can participate and what data the trial covers.

A natural-language answer needs the same definitions as a conventional report. Suppose a manager asks which location increased covers most. The answer depends on the date range and whether it measures reservations or seated diners, absolute gains or percentage growth.

In a hypothetical comparison, one location rises from 100 seated diners to 120, while another rises from 200 to 230. The second adds more diners, but the first grows faster: 20% against 15%. Either could lead the report, depending on the question.

The sensible acceptance test is a familiar question with a result already established from underlying records. Staff should be able to identify the period and measure used, then reconcile the answer. That tests whether the tool supports a decision rather than merely producing fluent text.

The business case should identify the work each function improves. A table rule should help manage usable inventory, a guest record should support a hospitality action, and a report should produce a verifiable answer.