SevenRooms integration

Connect SevenRooms to your AI Employee to let restaurant guests check live table availability, book a table, find an upcoming reservation, reschedule it, or cancel it — all through a phone or chat conversation, without waiting for restaurant staff.

Setup takes about 15 minutes once you have the credentials. Credential provisioning by SevenRooms may take additional time.

Add the SevenRooms integration module to the customer's Builder. Follow the steps in Create a new project using these values:

Ensure Auto update enabled is on, then click Create. Once created, click the three dots next to the project and select Force Update Project to pull the latest module version.

The integration manages its temporary access token automatically. Don't paste a token into the Builder.

The module also contains settings that are managed automatically or reserved for advanced support use. Leave them as they are: sevenrooms_access_token (refreshed automatically), sevenrooms_override_agent_attributes (installs the standard booking configuration during publish), sevenrooms_search_booking_schema and sevenrooms_search_booking_instructions (built-in phone-number extraction for chat), sevenrooms_setup_persona_id (internal identity created during setup), and sevenrooms_venue_group_id (reserved for future multi-venue support and unused in this version).

After you click Publish All, the integration:

To verify, open the canvas library and confirm that the intents Regular Table Booking, Cancellation via Agent, and Restaurant Reservation Reschedule via Agent appear, with Make a Regular Table Booking, Canceling Appointment via Agent, and Rescheduling a Restaurant Reservation via Agent as their scenarios.

After a successful lookup, the guest profile is refreshed with future SevenRooms reservations whose phone number exactly matches the requested number. Cancelled reservations are removed from the upcoming list, and reservations from other connected booking systems are preserved.

The integration ships with three editable scenarios. Booking and cancellation come from Newo's standard canvas library; rescheduling is supplied by this integration. These are a reference implementation: you can edit them in the canvas and publish your changes, and the AI Employee uses the changes after the next Publish All.

Each scenario contains exact sentences that start an integration action. The AI Employee says the phrase, the integration runs the action, and the AI Employee reads the result before continuing.

Runs when a guest wants to reserve a table for a regular-size party. The AI Employee gathers the date, time, and party size, routes large parties according to the restaurant's large-reservation policy, says the availability phrase, lets the guest pick one of the returned times, gathers the guest's name and phone number, asks permission to submit, and then says the reservation phrase. It only offers times returned by the availability check, and it waits for the booking action to report success before confirming the reservation.

Runs when a guest explicitly asks to cancel a reservation. The AI Employee says the lookup phrase, presents the matching reservation (or lists all matches and asks the guest to choose), reconfirms the selected day and time, asks for final approval, says the cancellation phrase, and confirms only after SevenRooms reports success.

Runs when a guest wants to move an existing reservation to another date, time, or party size. The AI Employee says the lookup phrase, requires the guest to select exactly one reservation, gathers the replacement date, time, and party size, says the availability phrase and offers only the live returned times, reads back the original and replacement details, asks for explicit final confirmation, and then says the rescheduling phrase. On an error, it explains that the original reservation is unchanged.

Within each scenario you can reword greetings, questions, and confirmations around the trigger phrases, add restaurant-specific questions or policy wording (deposits, seating, accessibility, arrival guidance) before final confirmation, and adjust tone and supported languages. Don't skip the explicit confirmation of the selected reservation or replacement slot, and don't let the AI Employee claim success before the action result reports it.

To turn an action off entirely, switch off the matching feature in Module - SevenRooms and click Publish All.

Use a test guest and a time that is genuinely open in SevenRooms. Cancel the test reservation when you're finished.

With the default radius, a request for 7 PM searches from 4 PM through 10 PM. Slots that require card payment are not offered, because the integration doesn't collect payment details.

The Client ID, Client Secret, or Venue ID is missing, mismatched, or doesn't have access to the configured venue.

SevenRooms issued a new Client ID or Client Secret, but the Builder still contains the previous value.

A required trigger phrase was removed, shortened, or paraphrased.

The phone number given in chat differs from the number stored on the SevenRooms reservation, or Enable Booking Lookup is off.

If no reservation is found, the AI Employee asks the guest to verify the phone number and offers help from the restaurant team. It doesn't claim that the reservation was cancelled.

SevenRooms rejected the cancellation, or the reservation changed after it was loaded.

The selected replacement slot is no longer current, the reservation was refreshed without its provider identity, or SevenRooms rejected the change. The original reservation is unchanged.