Loading…
This device has forgotten your details. On a shared computer, close the browser window too \u2014 that is the only way to be certain.
Loading…
How the guest app lays out this section's pages.
A section with no matching pages is hidden automatically.
Saved as a TEXT block. Richer block types are supported by the API.
The guest app reads these at runtime — components never change, only the token values.
Usage is counted when a guest pays, not when they type the code in.
Leave the last day empty for a one-day event. Guests stop seeing it the day after it ends — nothing to remember to delete.
Each template adds a section with starter pages as drafts, so nothing reaches guests until you publish.
Shown under the name on the card.
The guest reads this on the place's own screen. Say what a concierge would say.
This is what the guest's map app is given when they tap Get directions.
Optional. Adds a "Book a table" button.
Leave blank and the app falls back to a house photograph.
Courses, and the dishes under each one. This is what a guest reads on the place's screen; leave it empty for somewhere you only recommend.
On for your own restaurant and bar — each dish gets an Add button and the order reaches your team. Off for a place down the road: the guest reads the menu and orders at the table.
Must be http(s). Guests leave the app when they tap through.
Leave the price empty for "Price on request". Zero would read to a guest as free.