A restaurant reservation should be easy for the guest and predictable for the team. With Synqyo, you can place a booking widget on your own website and connect it to a rolling booking window. Guests reserve without leaving your site, while new dates become available automatically as each day passes.
This combination solves two separate problems. The widget gives guests a clear place to book. The rolling window controls when they can book. Together they give you one reservation flow that stays useful without publishing a new link every week.
What a rolling booking window does
A fixed booking page covers dates you choose once. That works for a special dinner or a tasting event, but ordinary restaurant service never really ends. A rolling window is designed for that ongoing schedule: its date range moves forward with the current day.
You choose a start offset and an end offset. The start offset is the earliest day a guest can reserve, and the end offset is the furthest day shown. For example, a window from 1 to 30 days ahead prevents same-day reservations and always lets guests book up to a month in advance. Tomorrow, the whole range moves forward by one day.
Existing reservations are not lost when the window moves. A table booked for next Tuesday stays booked even after that date is no longer at the leading edge of the bookable range.
How to set up restaurant reservations
- Create a Persistent booking. From the dashboard, choose Persistent booking so the reservation page uses a rolling date range instead of expiring.
- Choose the booking horizon. Set how many days from today reservations begin and how far into the future guests can see.
- Add your service hours. Enter lunch and dinner hours, choose the reservation duration, and add breaks for times when the kitchen is closed.
- Set the capacity. Use the maximum people per slot to represent how many guests you can accept at the same time, based on your tables and service capacity.
- Publish the widget. Open Embed widget, customise it, copy the generated code, and add it to your restaurant website.
A practical example
Imagine a neighbourhood restaurant serving dinner from 6 p.m. to 10 p.m. Reservations last 90 minutes, and the dining room can comfortably seat 12 new guests every half hour. The restaurant accepts bookings from tomorrow through 30 days ahead.
The manager creates a persistent booking, sets the rolling window to start 1 day ahead and end 30 days ahead, then adds the dinner hours and capacity. A guest visiting the restaurant website can open the widget, choose a date and time, enter their details, and submit the reservation. When a slot reaches capacity, it is no longer available to additional guests.
The next morning, yesterday drops out and a new date opens at the far end of the range. The manager does not need to recreate the schedule, replace a link, or reinstall the widget.
Make the widget feel like part of your restaurant
The embed controls let you tailor the booking experience before copying the code:
- Launcher label: use a direct invitation such as “Reserve a table.”
- Window title: name the restaurant or service, such as “Book dinner at Rosa.”
- Colour and icon: match your website and choose the food or restaurant icon.
- Calendar or menu layout: choose how guests browse the available times.
- Guest journey: decide whether diners enter their details or choose a slot first.
- Confirmation copy: explain what happens after the reservation is submitted.
The generated snippet is a small script tag. Add it once to the site template or the page where guests normally look for opening hours and contact details. The launcher stays in the corner of the page and opens the reservation flow in a focused window.
Use capacity as an operational limit
Capacity should describe what your team can serve, not simply the number of tables in the room. If accepting 20 guests at 8 p.m. would overload the kitchen, publish fewer places for that interval. You can create a steadier arrival pattern by combining a sensible slot interval, reservation duration, and maximum number of guests per slot.
Remember to block recurring closures and breaks. If lunch ends at 2:30 p.m. and dinner begins at 6 p.m., keep that gap unavailable. The same applies to weekly closing days, staff meetings, and private events.
Choose a booking horizon that fits your service
There is no single correct window for every restaurant. A small casual venue might open bookings 14 days ahead, while a destination restaurant may need 60 or 90 days. A start offset of zero allows same-day booking; an offset of one or two days gives the team more preparation time.
Start with a conservative range, watch how guests use it, and adjust it from the dashboard. Because the widget points to the persistent booking rather than a fixed set of dates, those changes appear without replacing the embed code.
One direct channel, less routine administration
A restaurant booking widget will not run the dining room for you, but it removes a repetitive layer of work. Guests can reserve from the place where they already found your menu and opening hours. Your team gets a structured booking instead of translating calls, emails, and direct messages into a separate diary.
Most importantly, the booking page stays current. Set the service pattern once, let the rolling window open each new date, and keep one recognisable “Reserve a table” button on your website.
Put direct reservations on your website
Create a persistent booking, set your restaurant hours and publish the widget.
Create your booking