Books over WhatsApp and chooses a seat visually — completing in the SevenRooms widget while you are on contract, or fully in RAYN once you switch.
Integration · SevenRooms
The complete reservation platform, and it works with SevenRooms.
RAYN is a complete reservation platform: it runs the book and the floor through the Host Station — a reservation grid, a live floor plan, table assignment, combinations, shifts and turn times — with conversational booking over WhatsApp, visual seat selection and guest intelligence. If your venue is mid-contract on SevenRooms, RAYN can handle guest discovery and visual table selection, then hand the guest to your SevenRooms widget to complete the booking — so you can start today and switch RAYN’s own engine on when the contract ends.

RAYN for discovery, conversation and visual selection · the SevenRooms widget completes the booking while you are on contract
The challenge
Guest intent starts before it reaches the reservation book.
SevenRooms manages reservations well. But demand often begins somewhere it does not capture cleanly — a WhatsApp message, a request for a specific table, a pre-arrival question — and that intent gets handled by hand, or lost. RAYN’s platform is built for exactly that.
Guests message the venue directly, and staff reconcile those conversations into the book manually.
Which table a guest wants — terrace, booth, a specific view — rarely survives the journey into a structured record.
Occasions, dietary notes and upgrade requests arrive across channels rather than one booking record.
The room sees the reservation, but not the demand signal and preferences that could shape the visit.
How the hand-off works
RAYN’s platform, with the SevenRooms widget completing the booking.
While you are on contract, RAYN owns discovery, the WhatsApp conversation and visual table selection, then deep-links the guest into your own SevenRooms booking widget to finish. The reservation is completed in, and lives in, SevenRooms — RAYN does not push a record into SevenRooms behind the scenes. It is an honest hand-off, not a hidden write-back.
RAYN runs the guest journey
Booking, WhatsApp and pre-arrival are RAYN — the platform the guest actually experiences.
The SevenRooms widget completes it
When the guest is ready, RAYN hands them to your SevenRooms booking widget with a link back to RAYN; the booking is made and kept in SevenRooms.
No hidden write-back
RAYN does not send a reservation into SevenRooms over an API — the guest completes it in SevenRooms’ own widget, so there is nothing to reconcile.
Or run RAYN end to end
Switch on RAYN’s own reservation engine and the Host Station runs the book and the floor directly — the floor plan and guest data are already in place.
Adopt at your pace
Start with discovery and the concierge in front of SevenRooms, prove the value, and move to RAYN’s own engine when the contract ends.
One guest view
Preferences, occasions and value build across visits, giving the room a richer read than the reservation line alone.
What you gain
The platform SevenRooms does not run.
Discovery, the concierge and the Host Station are RAYN, each capturing intent the reservation line alone cannot.
Seat intent, captured
Guests choose their table, booth, cabana or zone visually before they arrive — so seat intent is captured, not guessed.
Explore ↗WhatsApp ConciergeConversation into a booking
Turn your busiest enquiry channel into a structured booking path, with guest context attached.
Explore ↗Host StationRun the floor
The reservation grid, the ledger and a live floor plan — assign and combine tables, and run shifts and turn times.
Explore ↗Outcomes
What changes with RAYN.
RAYN runs the book, the floor and the guest experience; SevenRooms completes the booking only while you are still on contract.
Run discovery in front of SevenRooms today, and move to RAYN’s own book and floor when the contract ends — no rip-and-replace.
Questions
RAYN for SevenRooms, answered.
Is RAYN a complete reservation platform, or only an add-on for SevenRooms?
A complete reservation platform. RAYN runs the book and the floor through the Host Station — reservation grid, floor plan, table assignment, combinations, shifts and turn times — with visual booking, a WhatsApp concierge and guest intelligence. If you are mid-contract on SevenRooms, RAYN can also work with it via a guest-side hand-off.
How does RAYN work with SevenRooms while we are on contract?
RAYN handles discovery, the WhatsApp conversation and visual table selection, then hands the guest to your own SevenRooms booking widget to complete the reservation. The booking is made and kept in SevenRooms — RAYN does not write a record into SevenRooms behind the scenes.
What does RAYN add that SevenRooms does not?
Visual seat and zone selection before arrival, conversational booking over WhatsApp, a Host Station that runs the floor, and guest intelligence built across visits — preferences, occasions and value the venue owns.
Is this a migration project?
No. Start with discovery and the concierge in front of SevenRooms, keep SevenRooms completing the booking, and switch RAYN’s own reservation engine on when the contract ends. No migration while you are on contract.
Where does the booking end up as the record of truth while we are on SevenRooms?
In SevenRooms. RAYN hands the guest to the SevenRooms widget to complete the reservation, so SevenRooms keeps the record. When you move to RAYN’s own engine, the booking lives in RAYN.
See it on your venue
Keep SevenRooms for now. See RAYN’s full platform.
A short walkthrough — we show you RAYN’s Host Station, visual booking and concierge, how the hand-off to your SevenRooms widget works while you are on contract, and how RAYN’s own engine takes over when it ends.