SevenRooms Integration

Connects SevenRooms with the Newo AI agent so callers and chat visitors can check table availability, make reservations, find upcoming reservations, reschedule them, and cancel them without waiting for restaurant staff.

Time to first success: about 15 minutes once you have your SevenRooms credentials and venue identifier. Credential provisioning by SevenRooms may take additional time.

Before You Start

Make sure you have:

• an active SevenRooms account with external integration access;
• the Client ID, Client Secret, and Venue ID supplied for the restaurant by your SevenRooms representative;
• a venue in SevenRooms with bookable dates and times;
• access to Newo Builder, including permission to edit project settings, edit the canvas, and click Publish All.

What the AI can do

• Check live table availability. The agent asks for the preferred date, time, and party size, then searches the configured number of hours before and after that time. It labels the result with the restaurant location and presents bookable times in 12-hour format using the project's business time zone.
• Create a reservation. After the guest chooses an available time and confirms, the agent creates the reservation in SevenRooms.
• Recognize returning callers. When a phone number is identified at the beginning of a call, the agent quietly loads upcoming SevenRooms reservations into the guest profile.
• Find reservations in chat. If chat has no caller number, the agent uses the phone number supplied in the conversation and asks for one when it is missing.
• Handle multiple upcoming reservations safely. The agent lists the matches and asks the guest which one to cancel.
• Reschedule an existing reservation. The agent identifies one reservation, checks live replacement availability, asks for explicit confirmation, and moves the original reservation to the selected time.
• Cancel a confirmed reservation. The agent reconfirms the selected date and time, asks for final approval, and then cancels it in SevenRooms.

Returning-guest recognition

Phone calls and chats use the same guest profile but obtain the phone number differently:

Channel	What happens
Phone call	As soon as the caller number is identified, upcoming reservations are loaded quietly before the guest asks to manage one.
Chat	When the guest asks to find or cancel a reservation, the agent uses the phone number already present in the conversation. If none is available, it asks for the reservation phone number.

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, while reservations belonging to other connected booking systems are preserved.

Features at a glance

Feature	Included
Check live table availability	✅
Present the restaurant location and business-local times in 12-hour format	✅
Create a reservation	✅
Load reservations by caller phone at conversation start	✅
Search reservations by phone in chat	✅
Store found reservations in the guest profile	✅
Ask the guest to choose when several reservations match	✅
Move a reservation to a live available time after confirmation	✅
Cancel a reservation after confirmation	✅
Reserve slots that require card payment	❌ (payment collection and card tokenization are not supported yet)
Manage several venues from one integration instance	❌ (one Venue ID is used per instance)

Setup

1. Prepare your SevenRooms account

1. Ask your SevenRooms representative to enable external integration access for the venue.
2. Obtain the restaurant's Client ID, Client Secret, and Venue ID.
3. In SevenRooms, confirm that the venue has bookable availability for the dates you will use during testing.

SevenRooms console navigation can vary by account. If these values are not visible to you, request them from your SevenRooms representative rather than creating substitute values.

2. Get your SevenRooms credentials

SevenRooms supplies a paired Client ID and Client Secret. Keep both private. The Venue ID must belong to a venue accessible with those credentials.

The integration manages its temporary access token automatically; do not paste a token into Newo Builder.

3. Configure in Newo

1. Open the project in Newo Builder and find the Module - SevenRooms settings group.
2. Paste the supplied values into Client ID, Client Secret, and Venue ID.
3. Keep API Base URL set to https://api.sevenrooms.com/2_4 for US production. Use https://api.eu.sevenrooms.com/2_4 only when SevenRooms confirms that the venue is hosted in the EU production environment.
4. Confirm that the project's Business Time Zone matches the SevenRooms venue. Availability and reservation times are interpreted in this time zone.
5. Leave the feature switches enabled unless the restaurant intentionally does not offer that action through the agent.
6. Set Availability Search Radius (Hours) to how far before and after the guest's preferred time the agent should search. The default is 3 hours.
7. Keep Automatically Add Default Scenarios to Canvas enabled for a new project.
8. Click Publish All.

Setting (UI label)	Purpose	Default
API Base URL	Selects the SevenRooms production environment used by the configured credentials.	https://api.sevenrooms.com/2_4
Enable Availability Check	Allows the agent to retrieve open table times.	on
Availability Search Radius (Hours)	Searches this many hours before and after the requested time, within the same calendar day.	3
Enable Reservation	Allows the agent to create reservations.	on
Enable Cancellation	Allows the agent to cancel a selected reservation.	on
Enable Reservation Rescheduling	Allows the agent to move one selected reservation to a confirmed live slot.	on
Enable Booking Lookup	Loads and searches upcoming reservations by phone.	on
Automatically Add Default Scenarios to Canvas	Adds booking, cancellation, and rescheduling canvas content.	on

4. Hit Publish All

After Publish All, the integration:

• prepares the secure SevenRooms connection;
• enables the selected availability, reservation, lookup, rescheduling, and cancellation actions;
• adds Newo's standard booking and cancellation content plus the rescheduling intent and scenario when Automatically Add Default Scenarios to Canvas is on;
• preserves existing edited copies of those canvas items.

How to verify:

• ✅ Regular Table Booking, Cancellation via Agent, and Restaurant Reservation Reschedule via Agent appear in the canvas library.
• ✅ Make a Regular Table Booking, Canceling Appointment via Agent, and Rescheduling a Restaurant Reservation via Agent appear as their scenarios.
• ✅ A test chat can check availability, create a test reservation, find it by phone, reschedule it, and cancel it.

How to test that everything works

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

Test availability

1. Ask: "Can I reserve a table for two tomorrow at 7 PM?"
2. The agent says: "Give me a moment to check available slots right now. I'll get back to you shortly."
3. Confirm that the result names the restaurant location and that the 12-hour times match the venue's availability and local time zone in SevenRooms.

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 does not collect payment details.

Test reservation creation

1. Choose one of the offered times, provide the guest name and phone number, and approve submission.
2. The agent says: "I'm submitting your booking right now. Please give me a moment, and I'll get back to you shortly."
3. Confirm that the new reservation appears in SevenRooms with the selected date, time, party size, name, and phone.

Test chat lookup

1. Start a new chat and ask to find or cancel the test reservation.
2. The agent says: "Give me a moment to double-check if I have information about your bookings, I will get back to you shortly."
3. If needed, provide the same phone number used for the reservation.
4. Confirm that the agent presents the upcoming test reservation. If several reservations use that phone, it should list them and ask which one you mean.

Test cancellation

1. Select the test reservation and confirm that it should be cancelled.
2. The agent says: "Give me a moment, I will cancel your booking right now."
3. Confirm in SevenRooms that the reservation is cancelled.
4. Ask the agent to search again. The cancelled reservation should no longer appear in the upcoming list.

Test reservation rescheduling

1. Ask to move an upcoming test reservation to a different date or time.
2. The agent finds the reservation, checks live availability, and asks you to confirm the complete move.
3. After confirmation, the agent says: "Give me a moment, I will reschedule your reservation right now."
4. Confirm in SevenRooms that the same reservation now has the selected date, time, and party size.

Use a replacement slot that the agent just offered. Payment-required slots are excluded and cannot be used for rescheduling.

Scenarios

The integration ships with three editable scenarios. Booking and cancellation come from Newo's standard canvas library; rescheduling is supplied by this integration. The agent uses changes after the next Publish All.

What gets added on Publish All

Intent	Scenario
Regular Table Booking	Make a Regular Table Booking
Cancellation via Agent	Canceling Appointment via Agent
Restaurant Reservation Reschedule via Agent	Rescheduling a Restaurant Reservation via Agent

These intents and scenarios are a reference implementation. You can edit them in the canvas UI and publish your changes.

Updates do not overwrite your edits. Once you edit an intent or scenario, future integration updates will not replace your edited copy. To receive a newer shipped default, delete the edited copy from the canvas and click Publish All. The original is restored from the library, after which you can reapply your changes.

Why trigger phrases matter

Each scenario contains exact sentences that start an integration action. You may translate a phrase into the guest's language while preserving its meaning, as the standard scenarios direct, but do not otherwise shorten, paraphrase, or remove it.

Scenario 1 — Make a Regular Table Booking

Runs when a guest wants to reserve a table for a regular-size party.

1. Gather the preferred date and time.
2. Ask for the number of guests.
3. Route large parties according to the restaurant's standard large-reservation policy.
4. Say the availability trigger phrase and wait for live options.
5. Let the guest choose one of the returned options.
6. Gather the guest's name and phone number.
7. Ask permission to submit the reservation.
8. Say the reservation trigger phrase and wait for the final result.

Triggered by intent: Regular Table Booking.

Trigger phrases (do not edit):

• "Give me a moment to check available slots right now. I'll get back to you shortly." — checks live availability.
• "I'm submitting your booking right now. Please give me a moment, and I'll get back to you shortly." — creates the reservation.
• "Thanks. I'm submitting your booking right now. Please wait a moment, I'll get back to you shortly." — retries submission after a clarification.

What the agent reads to know the result:

• Availability panel — the open times for the requested date, time, and party size; only times shown there may be offered.
• Booking action status panel — the outcome of the latest submission; the agent waits for success before confirming the reservation.

Safe customization:

• ✅ Reword greetings, questions, and confirmations around the trigger phrases.
• ✅ Add restaurant-specific questions before final confirmation.
• ✅ Adjust tone and supported languages.
• ❌ Remove or paraphrase a trigger phrase.
• ❌ Let the agent claim a reservation is confirmed before the booking action status reports success.

Scenario 6 — Canceling Appointment via Agent

Runs when a guest explicitly asks to cancel an appointment, reservation, or booking.

1. Say the lookup trigger phrase and wait for the booking result.
2. Present the matching reservation, or list all matches and ask the guest to choose.
3. Reconfirm the selected day and time and ask for final cancellation approval.
4. Say the cancellation trigger phrase.
5. Confirm cancellation only after the booking system reports success.

Triggered by intent: Cancellation via Agent.

Trigger phrases (do not edit):

• "Give me a moment to double-check if I have information about your bookings, I will get back to you shortly." — loads and presents upcoming reservations.
• "Give me a moment, I will cancel your booking right now." — cancels the selected reservation.

What the agent reads to know the result:

• Existing bookings result — the guest's upcoming reservations, refreshed from SevenRooms by phone when available.
• Cancellation result — whether the selected reservation was cancelled successfully or requires human assistance.

Safe customization:

• ✅ Reword the questions used to choose and reconfirm a reservation.
• ✅ Add restaurant-specific cancellation-policy wording.
• ✅ Adjust tone and supported languages.
• ❌ Remove or paraphrase a trigger phrase.
• ❌ Skip explicit confirmation of the selected date and time.

Scenario 31 — Rescheduling a Restaurant Reservation via Agent

Runs when a guest wants to move an existing reservation to another date, time, or party size.

1. Use current upcoming reservations or ask for the reservation phone number.
2. Say the lookup trigger phrase and wait for refreshed reservations.
3. Present matching reservations and require the guest to select exactly one.
4. Gather the replacement date, preferred time, and party size.
5. Say the availability trigger phrase and offer only the live returned times in 12-hour format.
6. Read back the original reservation and complete replacement details, then ask for explicit final confirmation.
7. Say the rescheduling trigger phrase and wait for the current result.
8. Confirm the move only after the result reports success. On an error, explain that the original reservation is unchanged.

Triggered by intent: Restaurant Reservation Reschedule via Agent.

Trigger phrases (do not edit):

• "Give me a moment to double-check if I have information about your bookings, I will get back to you shortly." — refreshes upcoming reservations.
• "Give me a moment to check available slots right now. I'll get back to you shortly." — checks live replacement availability.
• "Give me a moment, I will reschedule your reservation right now." — moves the selected reservation after explicit confirmation.

What the agent reads to know the result:

• Existing bookings result — the guest's upcoming reservations and the provider identity needed to move one safely.
• Availability panel — the current replacement times for the requested date, time, and party size.
• Reschedule action state — whether the current move is processing, needs a correction, succeeded, or failed without changing the original reservation.

Safe customization:

• ✅ Reword questions used to identify the original reservation and gather replacement preferences.
• ✅ Add restaurant-specific policy explanations before final confirmation.
• ✅ Adjust tone and supported languages while keeping each trigger promise unmistakable.
• ❌ Remove, merge, or paraphrase a trigger phrase.
• ❌ Skip the exact-slot selection or explicit final confirmation.
• ❌ Claim success before the reschedule action state reports it.

Trigger phrases reference

Phrase (verbatim)	Fires	Scenario
"Give me a moment to check available slots right now. I'll get back to you shortly."	Availability lookup	Make a Regular Table Booking; Rescheduling a Restaurant Reservation via Agent
"I'm submitting your booking right now. Please give me a moment, and I'll get back to you shortly."	Reservation creation	Make a Regular Table Booking
"Thanks. I'm submitting your booking right now. Please wait a moment, I'll get back to you shortly."	Reservation retry after clarification	Make a Regular Table Booking
"Give me a moment to double-check if I have information about your bookings, I will get back to you shortly."	Reservation lookup	Canceling Appointment via Agent; Rescheduling a Restaurant Reservation via Agent
"Give me a moment, I will cancel your booking right now."	Reservation cancellation	Canceling Appointment via Agent
"Give me a moment, I will reschedule your reservation right now."	Reservation rescheduling	Rescheduling a Restaurant Reservation via Agent

Example dialogs

Example 1 — Book a table

Guest: Can I book a table for two tomorrow at 7 PM?

Agent: Give me a moment to check available slots right now. I'll get back to you shortly.

Agent: I found availability at 7 PM and 7:30 PM. Which works best?

Guest: 7:30 PM.

Agent: May I have your name and phone number?

Guest: Jamie Lee, +12025550123.

Agent: May I submit the reservation now?

Guest: Yes.

Agent: I'm submitting your booking right now. Please give me a moment, and I'll get back to you shortly.

Agent: Your table is confirmed for tomorrow at 7:30 PM.

Example 2 — Find a reservation in chat

Guest: I need to cancel my reservation.

Agent: Give me a moment to double-check if I have information about your bookings, I will get back to you shortly.

Agent: What phone number was used for the reservation?

Guest: +12025550123.

Agent: I found a reservation for tomorrow at 7:30 PM. Is that the one you want to cancel?

Example 3 — Choose between several reservations

Guest: Please cancel my booking.

Agent: Give me a moment to double-check if I have information about your bookings, I will get back to you shortly.

Agent: I found two upcoming reservations: Tuesday at 6 PM and Friday at 8 PM. Which one would you like to cancel?

Guest: Friday at 8 PM.

Agent: Are you sure you want to cancel the Friday 8 PM reservation?

Guest: Yes.

Agent: Give me a moment, I will cancel your booking right now.

Agent: Your Friday reservation has been cancelled.

Example 4 — Reschedule an existing reservation

Guest: Please move my Friday 7 PM reservation to later that evening.

Agent: Give me a moment to double-check if I have information about your bookings, I will get back to you shortly.

Agent: I found your Friday reservation for two at 7 PM.

Agent: Give me a moment to check available slots right now. I'll get back to you shortly.

Agent: I can offer 8 PM or 8:30 PM. Which do you prefer?

Guest: 8 PM.

Agent: You want to move Friday's reservation for two from 7 PM to 8 PM. Should I make that change?

Guest: Yes.

Agent: Give me a moment, I will reschedule your reservation right now.

Agent: Your reservation is now confirmed for Friday at 8 PM for two guests.

Customizing the agent

• Change tone or wording. Edit greetings, explanations, and confirmations while keeping every listed trigger phrase intact.
• Add restaurant policies. Add deposit, seating, accessibility, or arrival guidance around the existing steps.
• Change feature availability. Turn the matching feature switch off in Module - SevenRooms, then click Publish All.
• Restore defaults or receive newer defaults. Delete the edited intent or scenario from the canvas and click Publish All, then reapply your changes to the restored library version.

Once you edit an intent or scenario, later integration updates do not overwrite that edited copy.

FAQ

Q. Does the agent automatically know about reservations created before the current conversation?

Yes. On a phone call, it loads upcoming reservations after the caller's phone number is identified. In chat, it searches when the guest supplies the reservation phone number.

Q. What happens when more than one reservation uses the same phone number?

The agent lists the upcoming matches and asks the guest which reservation they want. It does not choose one automatically.

Q. Will a cancelled reservation appear in a later search?

No. A successful search refreshes the guest's upcoming list and excludes reservations that SevenRooms marks as cancelled.

Q. What if no reservation is found in chat?

The agent asks the guest to verify the phone number and offers help from the restaurant team. It does not claim that the reservation was cancelled.

Q. Can the guest reschedule an existing reservation?

Yes. The agent finds one reservation, validates the replacement against live availability, and moves it only after explicit confirmation. The original reservation remains unchanged if the move fails.

Q. Can the agent reserve a slot that requires card payment?

Not yet. Those slots are not offered because the integration does not collect payment details or create payment tokens. Direct the guest to the restaurant team or the restaurant's supported online booking experience.

Q. Can one integration instance manage multiple venues?

No. Configure one Venue ID per integration instance.

Q. Do I need to update the temporary access token?

No. The integration obtains and refreshes it automatically from the configured Client ID and Client Secret.

Q. Can I turn off phone-based reservation lookup?

Yes. Turn off Enable Booking Lookup and click Publish All. Cross-session cancellation will then depend on reservations already present in the guest profile or help from restaurant staff.

Common errors and recovery

Availability, booking, lookup, and cancellation all fail

Likely cause: Client ID, Client Secret, or Venue ID is missing, mismatched, or does not have access to the configured venue.

How to recover:

1. Ask your SevenRooms representative to verify all three values and their venue access.
2. Re-enter them in Module - SevenRooms.
3. Click Publish All.

How to verify: run the availability test above and confirm that the returned times match SevenRooms.

The agent stopped reacting after a canvas edit

Likely cause: a required trigger phrase was removed, shortened, or paraphrased.

How to recover:

1. Open the affected scenario on the canvas.
2. Compare its trigger phrases with the Trigger phrases reference table above.
3. Restore every changed phrase.
4. Click Publish All.

How to verify: repeat the relevant test chat and confirm that the agent performs the requested action.

All reservation actions stop after credentials are rotated

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

How to recover:

1. Ask your SevenRooms representative to confirm the active credential pair and its access to the venue.
2. Replace Client ID and Client Secret in Module - SevenRooms.
3. Confirm that API Base URL matches the region of the new credentials.
4. Click Publish All.

How to verify: run the availability test and confirm that live restaurant times are returned.

Chat cannot find a known reservation

Likely cause: the phone number in chat differs from the number stored on the SevenRooms reservation, or Enable Booking Lookup is off.

How to recover:

1. Turn on Enable Booking Lookup.
2. In the test chat, provide the exact phone number attached to the reservation, including the country code when it is available.
3. Repeat the lookup trigger phrase by asking the agent to search again.

How to verify: the agent should present the matching upcoming reservation or ask you to choose among several matches.

Cancellation fails after the reservation was selected

Likely cause: SevenRooms rejected the cancellation or the reservation changed after it was loaded.

How to recover:

1. Confirm the reservation still exists in SevenRooms.
2. Ask the agent to search again so it refreshes the guest's upcoming reservations.
3. Retry once after reconfirming the correct reservation.
4. If it still fails, complete the cancellation in SevenRooms and let Newo support know.

How to verify: SevenRooms shows the reservation as cancelled and the agent confirms success.

Rescheduling fails after final confirmation

Likely cause: the selected replacement slot is no longer current, the reservation was refreshed without its provider identity, or SevenRooms rejected the change.

How to recover:

1. Ask the agent to search for the reservation again.
2. Run a new availability check and choose one of the newly returned times.
3. Reconfirm the complete move and retry once.
4. If it still fails, keep the original reservation and complete the change in SevenRooms.

How to verify: SevenRooms shows the same reservation at the new date and time, and the agent reports the updated details.

Limitations

• One venue per integration instance. Use a separate Newo project or integration instance for another venue.
• Lookup depends on phone matching. The phone supplied by the guest must match the reservation phone.
• Card-required slots are not offered. The integration does not collect or tokenize payment-card details. Guests must contact the restaurant or use its supported online booking experience for those slots.
• One-day availability search. The search radius expands around the preferred time but remains within the requested calendar day.

Support handoff notes

When handing this deployment to support or a partner team, share:

• the restaurant and Venue ID this instance serves;
• whether Enable Availability Check, Enable Reservation, Enable Cancellation, Enable Reservation Rescheduling, and Enable Booking Lookup are on;
• whether Automatically Add Default Scenarios to Canvas ran or the project uses edited scenario copies;
• where the team securely stores the SevenRooms credential owner/contact;
• the result of the availability, reservation, lookup, rescheduling, and cancellation tests above;
• the first recovery action: verify the three SevenRooms values, re-enter them, and click Publish All;
• the second recovery action: compare edited canvas trigger phrases with the reference table.

All settings reference

Every setting the integration adds to Module - SevenRooms in Newo Builder is listed below. Operators normally edit only rows marked ✅. Rows marked ⚠️ are for advanced support use, and 🔒 rows are managed automatically.

Name	Description	Required	Default	Hidden	Edit
sevenrooms_client_id	Client ID supplied by SevenRooms.	Yes	(empty)	No	✅
sevenrooms_client_secret	Client Secret paired with the Client ID.	Yes	(empty)	No	✅
sevenrooms_venue_id	Venue ID for the restaurant this instance manages.	Yes	(empty)	No	✅
sevenrooms_base_url	Selects the SevenRooms API environment used by this instance.	Yes	https://api.sevenrooms.com/2_4	No	✅
sevenrooms_enable_availability	Allows live availability checks.	No	on	No	✅
sevenrooms_availability_search_radius_hours	Hours before and after the requested time included in availability search.	No	3	No	✅
sevenrooms_enable_reservation	Allows new reservation creation.	No	on	No	✅
sevenrooms_enable_cancellation	Allows confirmed reservation cancellation.	No	on	No	✅
sevenrooms_enable_reschedule	Allows a selected reservation to move to a confirmed live replacement slot.	No	on	No	✅
sevenrooms_enable_booking_lookup	Loads and searches upcoming reservations by phone.	No	on	No	✅
sevenrooms_setup_scenarios	Adds booking, cancellation, and rescheduling canvas content.	No	on	No	✅
sevenrooms_venue_group_id	Reserved for future multi-venue support; unused in this version.	No	(empty)	Yes	⚠️
sevenrooms_override_agent_attributes	Installs the standard booking configuration during publish.	No	on	Yes	⚠️
sevenrooms_access_token	Temporary credential refreshed automatically.	No	(empty)	Yes	🔒
sevenrooms_search_booking_schema	Built-in format used to extract a reservation phone number from chat.	No	built in	Yes	🔒
sevenrooms_search_booking_instructions	Built-in instructions for finding the most recently supplied phone number.	No	built in	Yes	🔒
sevenrooms_setup_persona_id	Internal identity used during setup.	No	created automatically	Yes	🔒

Changelog

v0.0.5 — Confirmed reservation rescheduling

• Move an existing reservation safely. The agent identifies one upcoming reservation, checks live replacement availability, and changes it only after explicit confirmation.
• Preserve the original on failure. Missing identity, stale slots, and provider errors do not cancel or overwrite the existing reservation.
• Keep guest profiles current. A successful move replaces the matching stored reservation details while preserving other bookings.
• Hide cancelled reservations after refresh. A new phone lookup replaces stale SevenRooms entries and keeps cancelled reservations out of the upcoming list.
• Show operator-friendly availability. Results include the restaurant location and use the configured business time zone with 12-hour times.
• Editable rescheduling scenario. Publish adds a dedicated reference scenario that reuses the standard phone and restaurant date/time procedures.

v0.0.4 — SevenRooms API contract corrections

• Correct provider requests. Reservation creation now uses the required form encoding, and cancellation omits an unnecessary JSON body.
• Reliable reservation lookup. Phone searches use the documented provider fields, business-local future date filtering, and real reservation response fields.
• Accurate local times. Availability and existing reservations are interpreted using the configured business time zone.
• Nearby alternatives. Availability searches use the configurable radius before and after the requested time.
• Bookable-slot safety. The selected slot's access identifier is preserved for submission, and card-required slots are excluded until payment support is available.

v0.0.3 — Unified booking and cross-session reservation lookup

• Unified availability, reservation, and cancellation behavior. The integration now follows Newo's standard booking actions and result handling.
• Returning reservations load by phone. Upcoming SevenRooms reservations are refreshed when a caller number is identified.
• Chat lookup added. Guests can supply the reservation phone number in chat before cancellation.
• Guest profiles stay current. Successful provider searches replace stale SevenRooms entries while preserving bookings from other systems.
• Standard canvas content. Publish now adds Newo's standard restaurant booking and cancellation scenarios without rewriting them.
• Rescheduling boundary clarified. One-step rescheduling is not supported; cancel and rebook instead.