Skip to content
Start free
A guest welcomed into a warm, full RAYN venue dining room.

Guests

The guest remembered, and brought back.

One guest record built from real visits — the memory a venue’s people carry, kept in one place — feeding review recovery and campaigns that go out in the venue’s voice, and only ever with your approval.

Book a 15-minute walkthroughSee the guest layer

One record

The memory of your best guests shouldn’t leave when a person does.

The regular’s table, the anniversary, the wine they always ask for — today that lives in a host’s head and walks out the door with them. RAYN keeps it in one record the venue owns, built from how guests actually behave, feeding every greeting, recovery and campaign downstream.

01

Guest Intelligence

The guest, remembered.

A good host remembers the regular, the celebration, the table someone always asks for and the dish they never skip — but that memory lives in people, and it leaves when they do. RAYN keeps it in one record, built automatically from every booking and pre-order — wherever the guest came from, your site, WhatsApp, Instagram or a call — with no point-of-sale to wait on, and puts it in front of the host the moment they arrive.

Just seatedTable 20

Sarah Kettering

Severe allergy

Tree nuts — anaphylaxis, carries an EpiPen.

Ordered vs allergy

Pistachio Parfait — contains nuts, which the guest flagged.

Occasion

BirthdayPartner’s birthday — surprise dessert with pastry.

Pre-ordered

2×Tasting Menu

1 dairy-free
Ordered so far

AED 3202 items

Pistachio Parfait · Champagne by the glass

Tonight

Guest asked to hold the birthday dessert until the main is cleared. · Alex

2 covers · Terrace · Alex · 20:00
RAYN·H·A7207C

A RAYN Host Station card. Guest details illustrative; the surface is live.

  1. A RAYN guest record — total visits, average spend and return score — and the automated flows it drives: pre-visit prep, post-visit review routing, birthday triggers and lapsed re-engagement.
  2. The Guest Intelligence overview — guests tracked, value segments, and a banner flagging spend as booked estimates until POS data verifies it.
  3. A guest’s commercial posture — reliability, no-show rate, preferred channel and a deposit recommendation, read from real booking history.
  • Recognised at the tableThe host sees who’s coming and what they’re known for — the zone they return to, their last table and rating, an allergen to flag, the anniversary this month — the moment the booking lands, not after the meal.
  • Built from behaviour, no POSCommitted spend, the dishes a guest pre-orders and the occasions they come back for — read from real bookings and pre-orders, with no point-of-sale integration to wait on.
  • Segmented, and kept currentVIP, Whale, Regular, At Risk, Dormant and New — recalculated every day as guests return, feeding every greeting, recovery and campaign downstream.

02

Reviews & Recovery

Fix it in private. Celebrate it in public.

A short rating ask goes out after the visit, over WhatsApp and email, then routes by the answer. A low score opens a private recovery case for your team — before it can harden into a public review; a high score is guided to Google or TripAdvisor. You make it right first, and only then ask to be seen.

  1. The RAYN reviews view — Google and internal ratings, response rate, and every review filtered by needs-reply and detractors, each with a reply action.
  2. The reputation overview — a reputation score, average rating, 30-day sentiment and how many reviews are still unanswered.
  3. Guest recovery — open recovery cases and a recovery policy bounding the actions and comp/refund caps an operator can log before a manager must approve.
  • Ask, then route by the answerA one-tap rating ask after the visit — and a poor score never sees a public-review link. It goes to your team, not to Google.
  • Recover privately, firstA low rating opens a case with a severity, an SLA and a real-time alert to your recovery contact — the apology lands before the moment becomes a public page.
  • Earn the review, keep the feedbackOnly once the case is resolved does the public-review invite go out — and the feedback a guest gives you writes into their record for next time.

03

Guest Marketing & Reactivation

Win them back — in your voice, on your say-so.

A soft night, lapsed regulars, a segment quietly drifting away — RAYN spots it from real visit history, drafts the win-back in your venue’s own voice, and holds it for you across WhatsApp and email. Nothing goes out without consent and a frequency cap, and every booking it earns traces back to the send.

  1. The RAYN reactivation console — live reactivation signals, a queue pending review, and next-best actions the engine prepares in WhatsApp with a review step kept before anything goes live.
  2. Marketing readiness across the estate — which venues have the engine switched on, guests reachable and consent rate, with a note that live delivery still needs the estate send config in place.
  3. The new-campaign builder — pick a channel (WhatsApp, email or both) and a campaign type such as lapsed guests, birthday or high value.
  • Detect and draftLapsed regulars and soft nights surface from real visits and value segments; the message drafts itself in your brand voice, ready to review.
  • Approved before it sendsYou release each campaign yourself; the always-on win-back journeys you approve once, then they run — and now stop chasing a guest who’s already rebooked.
  • Consented, capped, attributedEvery send checks consent and a frequency cap first, and the bookings that follow trace back to the send that earned them.

Questions

RAYN Guests, answered.

Where does the guest record come from?

From real visits — bookings, party size, spend, the table and zone, the dishes a guest pre-orders, declared allergens, occasions and the feedback they give all attach to one record. It is built from how guests actually behave, not from guesswork, and needs no point-of-sale integration.

How does review recovery avoid public complaints?

A short rating ask after the visit routes by the answer: a low score opens a private recovery case for your team — a prompt, personal apology — and the public-review invite is held back until that case is resolved, while a high score is guided straight to Google or TripAdvisor.

Will RAYN message guests on its own?

Ad-hoc campaigns wait for a person to approve each one. The always-on win-back journeys you approve once as a play, then they run automatically — always inside consent, a frequency cap and quiet hours, and they stop chasing a guest who has already rebooked. Nothing ever sends to a guest who has not consented.

Who owns the guest data?

You act on it: a venue only ever sees the guests linked to its own bookings and visits — enforced at the database level — and contact details are restricted to owner and manager roles. The record travels with the guest across the RAYN venues they visit, so the concierge, host station and campaigns never disagree about who someone is.

See the guest layer on your venue.

A walkthrough takes fifteen minutes — the guest record, review recovery and campaigns, on your own guests.

Book a 15-minute walkthrough