One canonical record
ChatGPT, Google, your existing system, WhatsApp or your own site — each writes the same booking through one shared path, so your team owns one record, not a pile of exports.
Book from anywhere
A guest might reach you from an AI assistant, a Reserve button on Google, or the reservation system you already run. RAYN takes the booking wherever it begins and turns it into one canonical record of the exact table — attributed to where it came from, attributed to where it came from, with no consumer marketplace in the middle.
Amira · 4 guests · Fri 8:15
01
Search live · booking by keyAI assistants
RAYN speaks MCP — the open protocol AI assistants use to reach live tools. An assistant can search your venues, check real availability and read your booking policy today, key-free. Ask it to book and — with a key you issue — it commits through the exact same canonical path every RAYN channel uses.
Book me a table at The Garden Terrace, Friday 8pm, four of us.
Garden terrace, Fri 20:15 — available for 4.
Held under Amira · ref RAYN-H-A7207C. Deposit link sent by WhatsApp.
Done — Friday at 8:15 on the Garden terrace for four. Your deposit link is on its way by WhatsApp.
02
Profile link live · feed readyReserve with Google
A guest searching your name on Google or Maps can tap Reserve and land in your own RAYN booking flow — the exact-table experience, not a marketplace. You can add it today by putting your RAYN link on your Google Business Profile; the deeper Reserve-with-Google feed is built and validated, ready to switch on the moment Google approves us.
The Garden Terrace
Your booking page · choose the exact table
03
LiveYour existing system
RAYN can start in front of an existing reservation system. With SevenRooms or serVme today, RAYN handles discovery and visual selection, then hands the guest to that system’s own booking widget to complete the reservation. There is no hidden write-back or two-way sync.
Layer mode is an explicit guest-side handoff — Full RAYN runs end to end
One system underneath
ChatGPT, Google, your existing system, WhatsApp or your own site — each writes the same booking through one shared path, so your team owns one record, not a pile of exports.
Every booking is tagged with where it came from, so you can see which channel earns its keep — without a marketplace deciding for you.
A booking that starts on Google or in an assistant is attributed back to its origin and enters the same RAYN booking architecture, without a consumer marketplace sitting between the venue and the guest.
Questions
An assistant can search your venues, check real availability and read your policy today, key-free. To let it commit a booking you issue it a key, and it books through the same deposit-safe canonical path every RAYN channel uses — the deposit is a WhatsApp link, never taken in the chat.
No. The Reserve button on Google opens your own RAYN booking page; the guest completes it on your page, not inside Google. You can add the button today via your Google Business Profile, and the deeper Reserve-with-Google feed is built and switches on when Google approves us as a partner.
No. RAYN can start in layer mode. For SevenRooms and serVme today, RAYN handles the guest journey and then hands the guest to the incumbent booking widget to complete the reservation. Full RAYN can take over later when the venue is ready.
Channel and platform economics are agreed as part of the venue’s RAYN commercial terms. The adapter layer is designed around direct venue journeys rather than a consumer marketplace.
Yes. Every channel and adapter writes the same canonical booking through one shared path, tagged by where it came from, so your team owns one record no matter where the guest started.
See it on your venue
A short walkthrough — we book your venue from an AI assistant and a Google listing, and show both land as one record your team owns.