They choose their table, book over WhatsApp and arrive recognised — while the reservation still lands safely in serVme.
Integration · serVme
Keep serVme. Add the guest layer in front.
If your venue already runs serVme, there is no reason to rip it out. RAYN sits in front as a WhatsApp, visual booking and intelligence layer — while serVme stays the system of record for every confirmed reservation underneath. You start where it matters most and widen at your own pace.
RAYN in front · serVme as the record — one booking flow from enquiry to confirmed reservation
The challenge
serVme runs the reservation. The guest journey is still yours to build.
serVme manages the booking record and the operational side of reservations for venues across the region. What it does not do is give the guest a way to choose their exact table, turn a WhatsApp enquiry into a structured booking, or read the demand and spatial signal behind the room.
Spatial intent is invisible
Guests cannot choose the window, the booth or the terrace before they arrive — table position stays unseen.
WhatsApp handled by hand
The busiest channel in the region still relies on staff typing back and forth, not one structured booking path.
Demand goes unread
The room has no live read on which tables, zones and time-bands are driving revenue and which are left idle.
Guest data stays in the tool
Preference, channel and occasion are not captured as intelligence the venue owns and can act on.
How the layer works
A guest and intelligence layer, in front of serVme.
RAYN does not change what serVme does. It handles the guest-facing journey and the intelligence, connects through an adapter, and writes the confirmed booking back to serVme as the record. Nothing gets ripped out.
It sits in front
RAYN owns the guest journey — discovery, visual booking and WhatsApp — while the floor team keeps the tool they trust.
serVme stays the record
Every confirmed reservation lives in serVme underneath, so there is one source of truth and nothing to reconcile.
It adds the journey and the signal
Visual booking, WhatsApp Concierge and intelligence come in on top, giving guests and the venue what the reservation tool did not.
An adapter approach
RAYN connects to serVme through an adapter, structuring demand from website and WhatsApp and passing the booking back cleanly.
Adopt in phases
Begin read-only or with a single channel, prove the value, and widen to the full layer only when it has earned its place.
One unified guest view
Website and WhatsApp demand feed one booking record with preference and channel attached, so the guest is seen as one guest.
What you gain
The three layers RAYN adds on top.
Each sits in front of the serVme setup you already run. The guest experience becomes more deliberate, and the venue gains signal it did not have before.
WhatsApp Concierge
The enquiry becomes a booking
What lands in WhatsApp turns into a full booking — table, deposit and occasion — in the same thread.
Explore Visual DiscoveryGuests choose their spot
The window, the booth or the terrace, chosen before arrival, with per-seat rules behind every choice.
Explore RAYN BrainRead the room
Demand, spatial signal and guest value, read from your own data and turned into the next move.
ExploreOutcomes
What changes when the layer goes in.
Demand, spatial performance and guest value become visible, and the booking data belongs to the venue, not a third-party tool.
The layer goes in front in phases, serVme keeps the record, and the venue moves up only when the upside is proven.
Questions
RAYN and serVme, answered.
Do we replace serVme?
No. serVme stays your system of record and keeps every confirmed reservation underneath. RAYN sits in front as a guest and intelligence layer — the floor team keeps the tool they already trust, and RAYN adds the journey and the signal on top.
How does RAYN sit in front of serVme?
RAYN handles the guest-facing journey — visual booking, WhatsApp and intelligence — and connects to serVme through an adapter, so the confirmed booking is written back to serVme as the record. Your team's booking habits on the floor do not have to change.
What does RAYN add that serVme does not?
A visual way for guests to choose their exact table, a WhatsApp path that turns an enquiry into a structured booking, and an intelligence read on demand, spatial signal and guest value — captured as data the venue owns rather than left inside the reservation tool.
Do we have to move everything at once?
No. Adoption is phased. You can begin read-only or with a single channel such as WhatsApp, prove the value while serVme keeps the record, and widen to the full layer only when it has earned its place.
Where does the confirmed booking live?
In serVme. RAYN structures the demand from website and WhatsApp, attaches preference and channel, and writes the confirmed reservation back to serVme, so there is one record and no second source of truth to reconcile.
See it on your venue
Keep serVme. See where RAYN fits in front of it.
A short walkthrough — we show you how RAYN sits on top of your serVme setup, what the guest experience gains, and which phase fits your room. Nothing gets ripped out.