Mozrest is a restaurant reservation channel manager that connects booking platforms to restaurant reservation software. This guide covers connecting Mozrest to Newo.ai so the AI Employee can check real-time table availability, book reservations with full guest details, and cancel existing reservations on behalf of diners. Because Mozrest sits between the AI Employee and the reservation system, this integration works with any restaurant using a Mozrest-connected reservation platform — no direct integration with the underlying system is required.

Supported restaurant systems

The Mozrest integration is compatible with any restaurant using one of Mozrest's connected reservation software platforms. Mozrest currently connects with 50+ reservation systems, including:

Access Collins, Apparta, BokaBord, CoverManager, Dineout, DiningCity, easytable, Eat App, Eat2eat, Eventlin, Foodii, Formitable, Gastronaut, Guestonline, Hostme, i-host, inline, Menüpp, Minitable, MojStolik.pl, Nextable, Noona, Ontopo, Precompro, Quandoo, Reservandonos, RESERViSiON, Reservours, Resfor, Resmio, resOS, Resto Guru, Rezervem, Riservi, RSRVIT, serVme, SevenRooms, simpleERB, Simpra, Superb, Tablein, Tableo, TableOnline, Weeloy, Zenchef, Zjedz.my, Zonal

For the latest partner list, see Mozrest's partners page.

Prerequisites

Before you begin, confirm the following:

An active Mozrest account with API access
Your restaurant configured in Mozrest with areas or locations set up
Mozrest connector credentials configured at the platform level

Create the Mozrest project

Before configuring attributes, add the Mozrest integration module to the customer's Builder. Follow the steps in Create a new project using these values:

Field	Value
`Idn`	`mozrest`
`Title`	`mozrest`
`Registry`	`production`
`Module`	`mozrest_integration`

Ensure Auto update enabled is turned on, then click Create.

Once the project is created, click the three dots icon next to it and select Force Update Project to pull the latest module version.

Then click Publish all.

Connect Mozrest in the Newo Platform

Open the customer's Builder in Newo.ai.
Go to Attributes.
Verify or set the following attributes, then click Save + Publish All.

Attribute	Required	Description
`project_business_time_zone`	Yes	Restaurant timezone (e.g., `America/New_York`)
`project_business_name`	Yes	Restaurant name
`project_attributes_private_dynamic_restaurant_google_restaurant_id`	Yes	Restaurant identifier used by Mozrest
`mozrest_enable_slot_check`	No	Enable availability checking. Default: `True`
`mozrest_enable_booking`	No	Enable booking capability. Default: `True`
`mozrest_enable_cancellation`	No	Enable cancellation capability. Default: `True`

On publish, the setup automatically creates the Mozrest and HTTP connectors, injects booking, availability, and validation payload schemas for the AI Employee, and enables the configured booking, availability, and cancellation features.

🗒️ NOTE

The integration will not function without a valid restaurant ID in project_attributes_private_dynamic_restaurant_google_restaurant_id. Confirm this value is populated before publishing.

Supported features

The integration supports the following capabilities:

Check availability — Date, time, party size, and timezone-based slot search
Book reservation — Full guest details with AI-powered area selection
Cancel reservation — Cancels a booking by booking_id
Area/location management — Available areas are fetched from Mozrest during the availability check and cached for the session
AI area matching — An LLM matches the guest's stated preference (e.g., "outside" or "by the window") to the closest available area
Party size handling — Passed to both availability and booking APIs
Large group detection — Configurable minimum party size threshold for special handling
Booking window validation — Maximum days in advance is configurable via a project attribute

The following are not supported:

Reschedule reservation — Use cancel + rebook as a workaround
Waitlist management — If no slots are available, the AI Employee can only suggest alternative times from the availability results
Multi-restaurant support — Single restaurant per integration instance

How availability and area matching work

When the AI Employee checks availability, Mozrest returns a list of restaurant areas (e.g., patio, main dining, bar) along with open slots. These areas are cached per session.

When the guest books, an LLM (Gemini 2.5 Flash) matches the guest's area description to the closest available area before creating the reservation. The model uses a low temperature setting (0.2) for deterministic, consistent results.

🗒️ NOTE

The area field is required in the booking payload. If the guest does not specify a preference, the AI Employee should ask or suggest the areas returned from the availability check.

Required guest information for booking

All of the following must be collected before a reservation can be created:

First name
Last name
Email address
Phone number (E.164 format, e.g., +15551234567)
Date and time
Party size
Area preference

Notes (for special requests) are optional.

Test the integration

After publishing, verify each capability using the Newo conversation interface (chat or voice):

Setup — Publish the project and confirm connectors are created and schemas are injected.
Availability — Ask "Do you have a table for 4 tomorrow at 7 PM?" and verify that available slots are returned with area information.
Booking — Complete a reservation conversation and verify the booking appears in Mozrest with the correct guest details and area.
Cancellation — Request cancellation of a reservation and verify it is removed from Mozrest.

⚠️ CAUTION

This integration performs real operations in Mozrest. Reservations created or cancelled through the AI Employee are reflected immediately in the live restaurant system.

Troubleshooting

If the integration is not responding as expected:

Confirm the Mozrest connector is properly configured with valid credentials.
Verify project_business_time_zone is set to a valid IANA timezone string (e.g., America/Chicago).
Confirm project_attributes_private_dynamic_restaurant_google_restaurant_id is populated with a valid restaurant ID.
Check that the relevant feature flags are enabled: mozrest_enable_slot_check, mozrest_enable_booking, mozrest_enable_cancellation.
Confirm the integration was re-published after any configuration changes.

FAQ

Q: How does the AI Employee select the restaurant area? During availability checking, Mozrest returns a list of areas (e.g., patio, main dining, bar). These are cached per session. When the guest books, an LLM matches the guest's area description (e.g., "outside" or "by the window") to the closest available area.

Q: What if the guest doesn't specify an area preference? The area field is required in the booking payload. The AI Employee should ask the guest for their preference or suggest the areas returned from the availability check.

Q: Can I connect multiple restaurants? Each integration instance supports one restaurant. For multiple restaurants, create separate integration instances.

Q: How should phone numbers be formatted? Phone numbers are expected in E.164 format (e.g., +15551234567).

Q: Does the integration support large group reservations? Yes. The availability payload schema includes a configurable minimum party size threshold for special handling of large parties.

Q: How far in advance can reservations be made? The maximum booking window is configurable via a project attribute. The availability validation schema enforces this limit.

Q: Does the integration handle waitlists? No. If no slots are available, the AI Employee can only suggest alternative times from the availability results.

Housecall Pro integration