SevenRooms Review 2026: Pricing, Features & Complete Restaurant Setup Guide
SevenRooms is the platform. Performance marketing, WhatsApp automation, and proper tracking are what make it work. This guide covers both halves — strategic clarity for operators and technical implementation for teams.
Updated May 2026
Live UAE benchmarks
Interactive calculators
Published: May 2026 |
Last Updated: May 2026 |
Reading Time: 20 min
If you're wondering whether SevenRooms is just a reservation tool or a full restaurant growth platform, the short answer is: it's an all-in-one hospitality CRM and operations system that helps restaurants manage reservations, guest data, marketing automation, and personalised customer experiences from a single platform used by 15,000+ venues globally including Jumeirah, Zuma, and Nobu. Pricing starts at ~$499/mo per venue with zero per-cover fees; full suite with WhatsApp runs $600–900/mo. This guide breaks down how SevenRooms works, its key features, full pricing structure, pros and cons, integrations, how it compares to OpenTable, and whether it's the right fit for your restaurant — backed by 91 days of live UAE fine-dining data including an 81% reservation-to-visit rate, 98% WhatsApp open rates, and a benchmark showing a 40% paid media cut drives a 69% reservation collapse across every channel.
Pricing
SevenRooms Pricing 2026
SevenRooms doesn't publish pricing publicly. Based on operator-reported data and third-party directories, here's what a single UAE venue realistically pays:
Core Plan
Platform / Venue
~$499/mo
Annual contract. Reservations, waitlist, floor management, CRM, reporting. Zero per-cover fees on direct bookings.
Not in base plan. Required for automatic no-show tagging, high-risk classification, and slot auto-release. Most operators discover this is missing when they try to configure no-show automation.
Full Suite — Single Venue
Core + Marketing + WhatsApp
$600–900/mo
Realistic all-in cost for a UAE fine-dining venue. Under 0.1% of revenue at scale. No per-cover fees on any direct booking.
vs OpenTable: OpenTable charges $149–499/mo base plus $1–$1.50 per network cover. At 2,000 covers/month, that's $2,000–$3,500/mo in fees alone — before the subscription. SevenRooms charges $0 per cover. Note: OpenTable ended its two-way integration with SevenRooms in 2025 — the choice is now mutually exclusive.
81%Avg reservation-to-visit rate
98%WhatsApp open rate
−54%Walk-ins drop when paid media cuts
10–20×Paid vs organic CTR multiplier
🧮 What are no-shows costing you?
Based on our experience with high-end restaurants in Dubai — calculate your monthly exposure in under 30 seconds.
Monthly no-shows
300
covers lost
Revenue lost/mo
AED 105K
from no-shows
Recoverable
AED 70K
with fixes in place
ROI vs WA add-on
191
recoverable ÷ ~AED 367/mo
Benchmark based on UAE fine-dining operations. Actual results vary by venue type and implementation.
For founders, GMs, and marketing directors. What SevenRooms can do, why paid media and reservations are inseparable, and which WhatsApp path fits your operation.
01 · PlatformSevenRooms Features: What the Platform Is — and Isn't
Restaurants embed the SevenRooms widget on their website or link to its hosted booking page. Guests complete the reservation. SevenRooms manages the floor, builds guest profiles, and powers marketing automation — from post-visit emails to WhatsApp broadcasts. Every guest record belongs to the restaurant, not the platform.
Core Strengths
Guest CRM depth. Zero per-cover fees on direct bookings. Native WhatsApp (EMEA/APAC). Google Reserve integration. First-party data your restaurant owns — not the platform.
Platform Limits
Doesn't generate demand. No native UTM capture. No custom booking form fields (requested, not yet built). Auto-Tags for no-shows require a paid add-on. GTM needs Superuser to implement.
Right Fit
Hotel F&B, fine dining, multi-outlet groups that generate their own demand. Not ideal if you depend on marketplace discovery — OpenTable serves that need. Under 60 covers needing budget-friendly WhatsApp: Eat App or Servme.
Most operators discover Custom Auto-Tags are missing only when they try to configure no-show automation. Contact your CSM before assuming this is active on your account.
Capability
SevenRooms
OpenTable
Eat App / Servme
Resy / Tock
Guest data ownership
Full
Platform retains
Full
Good
WhatsApp integration
Native EMEA/APAC
None
In base plan
None
Per-cover fees (direct)
$0
$1–$1.50/cover
$0
$0
Marketplace discovery
Limited
Best — 22K+ venues
Minimal
US-centric
UAE / GCC presence
Jumeirah, Atlantis +70
Growing
Dubai-founded
Minimal
OpenTable ended its two-way integration with SevenRooms in 2025. The choice is now mutually exclusive — switching means rebuilding your guest CRM from scratch.
02 · DemandThe Paid Media Flywheel
The finding that surprises most operators: cutting paid media doesn't just affect digital bookings — it collapses every channel simultaneously, including walk-ins that have no direct link to any platform. Paid campaigns sustain local search visibility, GBP impressions, and the ambient awareness that drives spontaneous dining decisions.
Show-Up Rate by Booking Source — UAE Benchmarks
SourceShow-up rateRatePriority action
Walk-In
95–98%Preserve floor capacity
Phone / Staff
85–92%Add WhatsApp reminder
Google Reserve
60–70%24hr + 2hr WA reminders
Direct website
55–65%Deposit on peak shifts
Paid social (broad)
5–20%Full WA nurture sequence
Instagram reach
0–15%WA confirm + deposit
Data from 91 days of SevenRooms actuals at a Michelin-recognized fine-dining venue in UAE. Numbers indexed vs peak period. Combined context: budget reduction + Ramadan + regional market disruption.
Channel
Peak Period
Post Budget Cut
Change
Total reservations
Index 100
Index 31
−69%
Walk-ins / day
Index 100
Index 47
−54%
Staff-assisted bookings
Index 100
Index 25
−75%
Google Reserve bookings
Index 100
Index 31
−69%
Media spend
Index 100
Index 59
−41%
A 41% spend reduction produced a 69–75% decline across every channel — including walk-ins that have no direct link to any booking platform. Paid media drives the full demand flywheel, not just direct digital bookings. Seasonality sets the ceiling; campaigns determine how much demand is captured.
Meta → Google cross-channel effect (same period)
On days with active Meta spend, a measurable share of users subsequently made a branded or category Google search — evidencing a real awareness pipeline between the two platforms. On a near-zero spend day, the cross-channel volume dropped to a fraction of peak-spend days, confirming the dependency. Pausing Meta doesn't just reduce Meta bookings — it reduces Google search intent too.
Key Takeaway
Maintain a minimum 5:1 paid media to platform cost ratio. Cutting campaigns to fund the platform is the most common and most expensive mistake in this category.
03 · WhatsAppSevenRooms WhatsApp Integration: Choosing the Right Path
WhatsApp achieves ~98% open rates on transactional messages versus 20–25% for email. In UAE, GCC, India, and Southeast Asia, it's the dominant communication channel for your guest base. The question is not whether to use WhatsApp — it's which integration model fits where you are.
When to use SevenRooms WhatsApp
You want transactional automation live within 1–2 weeks with no dev work
Your priority is reducing no-shows via confirmation reminders
You want CRM-segmented marketing broadcasts to opted-in guests
Budget: $100/month, zero per-message transactional cost
Start here. Transactional reminders alone — confirmation, 24hr, 2hr — recover a meaningful share of no-shows at zero per-message cost. This pays for itself before the first marketing campaign.
What you get
✓Booking confirmation (instant, free)
✓24-hour reminder with Confirm/Cancel button
✓2-hour same-day reminder
✓Marketing broadcasts to opted-in segments
−No chatbot or real-time availability check inside WhatsApp
−No payment collection inside WhatsApp
Setup: Meta Business verification (1–3 weeks) + 2 new SIM numbers never registered on WhatsApp + submit to SevenRooms EMEA AM. Billing leeway: July 1 start available.
When to use a Meta Business Partner (e.g. Infobip)
You want the full booking journey inside WhatsApp — availability check, confirmation, payment
You handle high-volume group events where pre-payment and pre-order are critical
You're already proven on SevenRooms WhatsApp and want to unlock chatbot automation
You have developer resource to build and maintain the SevenRooms API integration
Do not start here. The integration complexity is significant and the SevenRooms sync requires custom API work. Establish SevenRooms WhatsApp first, validate the channel, then upgrade.
✓Booking confirmed and QR ticket sent inside the chat
✓Deposit collected via payment link without leaving WhatsApp
✓Pre-order and dietary preference collection for group events
✓~80% of bookings handled with zero staff intervention
Group event benchmark: 15-min booking process vs 45+ min via phone. 40% higher prepayment rate vs email-based group booking.
The Decision Rule
Start with SevenRooms WhatsApp. Run for 90 days. If WhatsApp proves its value in reduced no-shows and reactivation revenue, and you have developer resource, then scope the Meta Business Partner integration. The chatbot is the upgrade — not the starting point.
04 · No-ShowsNo-Show Management: What Works and What Requires a Paid Add-On
UAE premium dining venues run 15–30% no-show rates without controls in place. The configuration stack below is separated by what you can do immediately and what requires your CSM.
✅ Self-serve (no CSM)
Settings → General → Venue Settings
Click Reservations category
Scroll to Reservation Confirmation
Uncheck Auto-Confirm Reservations
Click blue Save Changes
Bookings arrive as "Booked" not "Confirmed." Guests confirm via reminder email. Unconfirmed slots remain visible for staff action. Verify reminder emails are live before enabling.
Update booking policy text: Settings → Guest Facing Language → Policies → Default Booking Policy → edit → Save and Publish. Also update the Reservation Widget Title to prompt guests to read the policy.
Settings → General → Venue Settings → Reservations → Additional Configurations → "Do not allow multiple reservations for the same guest" → click Same Shift → Save Changes.
SevenRooms cannot auto-cancel existing duplicates — staff must delete them manually. This setting only blocks future ones.
Clients tab → search guest → Edit Profile → Tags → type "Black List" → Save. Tag surfaces on the reservation card. Not an automatic block — pair with Auto-Confirm off so staff intercept before confirmation.
WhatsApp confirmation flows naturally filter fake-name and bot bookings — numbers that don't exist or can't receive WhatsApp fail the confirmation step automatically.
Custom Auto-Tags are not in the base plan. Most operators discover this only when they try to configure no-show automation. Contact your CSM before assuming anything is active.
Custom Auto-Tag fires when a reservation is marked No-Show — appending a tag to the guest's CRM profile automatically. Without this, no-show tracking depends entirely on staff manually updating statuses after every service.
Second rule: 2 no-shows in 90 days → "High Risk" tag. Third → "Blacklist" + mandatory staff confirmation required before any future reservation is accepted. Combined with Auto-Confirm off, this creates targeted friction for persistent no-show guests.
With Auto-Confirm off, unconfirmed bookings accumulate on the floor plan. Auto-Tag logic can trigger a slot release after a defined window of no guest response — typically 24 hours before service — freeing it for the waitlist without staff intervention.
Fastest Lever
Deposits on Friday/Saturday dinner and parties of 6+. In UAE fine-dining operations, no-show rates have been observed dropping from 15% to under 1% the week deposits go live. No automation matches the behavioural effect of money committed.
Part 2 — Technical Implementation
For digital marketing managers, in-house tracking specialists, and agency teams. GTM setup, pixel architecture, event mapping, WhatsApp flows, and keyword-level optimization.
05 · Tracking SetupGTM, Meta, Google Ads & Snap — Step by Step
Prerequisite — Superuser access required: Only Superuser-level contacts in SevenRooms can install the GTM container ID. Standard account managers cannot. Identify the Superuser at your venue (usually the contract signatory) and have them open a SevenRooms support thread to install the GTM ID before any other tracking work.
Route all Meta ads to your restaurant domain first — not directly to a SevenRooms URL. The Pixel fires on landing and Meta's fbclid is captured.
Deploy UTM-append tag in GTM — reads fbclid from the URL on first landing, stores in a 30-day first-party cookie.
Re-append to SevenRooms URL on Reserve click — tag dynamically reconstructs the booking URL with fbclid, allowing Meta to match the confirmation PageView back to the ad click.
Meta Pixel fires Purchase on SR confirmation page — via the GTM container installed by your Superuser contact.
Common issue: Pixel fires PageView on SevenRooms but Landing Page Views = 0 in Ads Manager. Root cause: fbclid stripped at the domain boundary. Fix: restaurant domain first + UTM-append tag. Verify in Meta Events Manager → Test Events.
SevenRooms channel URL paths give native source attribution: /fb for Facebook, /ig for Instagram, /goog for Google — append UTMs on top for campaign-level detail.
Superuser installs GTM container in SevenRooms — prerequisite for everything below.
Add GA4 Configuration Tag with your Measurement ID to the SevenRooms GTM container. Trigger: All Pages.
Add GA4 Event Tag for reservation_completed on the confirmation page URL.
Import as Google Ads conversion — in Google Ads, import the GA4 event as a primary conversion. Set Smart Bidding (Target CPA or ROAS) against this event.
Without this, Smart Bidding optimises against Reserve Button Click — a proxy intent event on your website, not a completed booking. The signal diverges from actual revenue over time.
Failure 2: Cross-domain race condition. The Snap base pixel init lives inside the Page View tag in GTM. On SevenRooms' domain, the PURCHASE tag fires before init completes — silent failure.
Fix for Failure 1 — remap to standard Snap events:
Funnel Stage
GTM Trigger
Correct Snap Event
1-min page engagement
Timer — 60 sec
ADD_CART
Reserve button click
Click on CTA
SIGN_UP
Reservation completed
CE — SR confirmation page
PURCHASE
Fix for Failure 2 — GTM Tag Sequencing:
Open the PURCHASE tag in GTM → Advanced Settings → Tag Sequencing
Check "Fire a tag before this tag fires"
Select the Snap Page View tag as Setup Tag
This forces snaptr() init to complete before PURCHASE executes
Always verify in Snap Events Manager Test Events — not GTM Preview. GTM Preview reports tags as fired even when the underlying JavaScript call silently fails on a foreign domain.
When the SevenRooms widget is embedded on your restaurant website, it runs inside an iFrame with its own isolated JavaScript context. Reservation completion events fire inside the iFrame's dataLayer — invisible to your website's GTM container.
Solution 1 (recommended): Direct all paid media to the SevenRooms hosted URL. All conversion tracking runs through the SevenRooms GTM container. Cleanest path, no additional code.
Solution 2: Add a postMessage listener Custom HTML tag to your website's GTM. Catches SevenRooms' iFrame completion signal and re-pushes to your website's dataLayer. Enables tracking through the embedded widget but requires developer or advanced GTM work.
# Meta / Instagram
[SR_URL]/fb?utm_source={{campaign.id}}&utm_medium={{placement}}&utm_campaign={{campaign.name}}&utm_content={{ad.name}}
# Google Ads (enable auto-tagging in account settings)
[SR_URL]/goog?utm_campaign={{campaignid}}&utm_term={{keyword}}
# Snap Ads
[SR_URL]?utm_source=snapchat&utm_medium=paid_social&utm_campaign=[CAMP]
Replace [SR_URL] with your full SevenRooms reservation URL. These parameters appear per booking row in the Reservations Export, enabling ROAS calculation without additional tooling.
Not all keywords that drive reservations drive visits. Reservations look like conversions in Google Ads — even when the guest doesn't show up. The metric that matters is reservation-to-visit rate per keyword group.
Keyword Category
Visit Rate
CTR (Paid pos 1–3)
Lead Intent
Required Action
Branded (restaurant name)
60–70%
12–18%
Warm
Standard confirmation + same-day reminder
Category + location
40–55%
8–14%
Medium
WhatsApp confirmation + 24hr + map link
Award / credential
35–50%
6–12%
Medium
WhatsApp + menu preview + dress code
Landmark / discovery
5–15%
8–15%
Cold
Full WhatsApp nurture — treat as lead not booking
Competitor alternative
30–45%
7–13%
Medium
WhatsApp with differentiator message
The landmark keyword insight: At a high-end Dubai restaurant, landmark and location-discovery keywords generated the highest reservation volume but some of the lowest visit rates — under 10% in peak campaign periods. Organic position on primary category terms sits around position 8, yielding ~0.8% CTR (~7 clicks/month). Paid position 1–3 on those same terms drives 8–15% CTR. That is the 10–20× multiplier that justifies running paid search even with existing organic rankings. Cold-intent keywords become viable only once the WhatsApp follow-up sequence is live.
Monthly Optimization Rule
Pull SevenRooms Reservations Export (filter: Complete) + Google Ads search terms report. Calculate visit rate per keyword group. Any keyword below 15% for two months: deposit gate or WhatsApp nurture required before budget increase.
07 · Message FlowsWhatsApp Message Architecture
Each touchpoint has a specific job. Sending the wrong message at the wrong time is as damaging as not sending at all.
Restaurant name, date, time, party size
Google Maps link to the exact branch — critical for venues where building address differs from restaurant entrance, or where the guest found you via a landmark search
Direct contact number for changes
Dress code if applicable
The map link measurably reduces "wrong branch" no-shows. Guests who booked via landmark keywords often have imprecise location knowledge. Deliver the pin in the first message.
Date and time reminder
Menu preview or signature dish highlight
Parking or arrival instructions
Confirm / Cancel button — guests who cancel 12+ hours out free the slot for the waitlist. The confirmation reply also validates the number is real, surfacing fake bookings before service.
Brief: "Your table is tonight at [time]"
Updated Google Maps link + parking/valet info
Direct WhatsApp contact for last-minute questions
Keep short. The guest knows the booking exists. You're reducing the friction of arrival, not selling the experience again.
3-option tap: Excellent / Good / Could Be Better
Excellent → immediate Google review link (40–60% review conversion when the link is one tap away)
Could Be Better → route to manager follow-up within 24 hours
At UAE fine-dining venues, a 4.9★ average across 1,000+ reviews correlates with 86%+ GBP interaction rate. Unanswered reviews — especially 1★ and 2★ — are a velocity-weighted ranking signal. Reply to all reviews within 48 hours.
One message the following day. Acknowledge plans change. Offer easy rebooking. No guilt, no explanation request. A segment of no-shows are genuine logistical failures — delayed flights, wrong address, family emergency. They will rebook if re-contacted within 24 hours with zero friction.
Response time benchmark: In UAE F&B, leads contacted within 15–30 minutes of generating a booking or inquiry convert significantly better than those contacted hours later. Automate immediate response for any WhatsApp lead generation campaign.
08 · Data & AudiencesReservation Export, Audience Building & Optimization
Upload email + phone to Meta Custom Audiences + Google Customer Match. Build 1% lookalike from confirmed visitors. Most valuable first-party audience you have.
No-shows + cancellations → Exclusions
Upload as suppression lists. Stop paying to reach people who already didn't convert. Use separately for WhatsApp re-engagement campaigns.
Lapsed guests (60+ days) → Reactivation
Segment from CRM by last visit date. WhatsApp broadcast with a specific reason to return. Consistently lower cost than new guest acquisition.
Custom attribution field — not yet available: A mandatory "How did you hear about us?" dropdown (Google Search, Google Maps, Instagram, Facebook, TripAdvisor, XiaoHongShu, Dianping, WeChat, Travel Agency, Concierge, Comecome, Friend Recommendation) was formally requested from SevenRooms. Response: feature does not exist, logged as a product request. UTM tracking via GTM remains the only first-party source attribution workaround.
FAQSevenRooms Frequently Asked Questions
SevenRooms is an all-in-one hospitality CRM and operations platform that helps restaurants manage reservations, guest data, marketing automation, and personalised customer experiences from a single platform. It covers reservations, waitlist management, table management, email and WhatsApp marketing, guest feedback, and loyalty — with full data ownership and no per-cover fees on direct bookings.
SevenRooms does not publish pricing publicly. Third-party data and operator reports indicate the core platform starts at approximately $499 per month per venue on an annual contract. The WhatsApp Messaging add-on costs approximately $100 per month. Custom Auto-Tags for no-show automation are a separate paid add-on not included in the base plan. A full single-venue setup including core platform, marketing module, and WhatsApp typically runs $600–$900 per month.
SevenRooms is better when you generate your own demand: full guest data ownership, zero per-cover fees on direct bookings, native WhatsApp integration, and a deeper CRM. OpenTable is better when marketplace discovery fills your seats — it has a 22,000+ venue network for new diner acquisition. Note: OpenTable ended its two-way integration with SevenRooms in 2025, making the choice now mutually exclusive.
Yes. SevenRooms offers a native WhatsApp Messaging add-on (approximately $100/month) available in EMEA and APAC markets. It automates booking confirmations, 24-hour reminders with Confirm/Cancel buttons, 2-hour same-day reminders, and marketing broadcasts to opted-in guest segments — all at zero per-message cost for transactional messages. Setup requires Meta Business verification and two new SIM numbers not previously registered on WhatsApp.
All paid traffic should land on your restaurant domain first — never directly on a SevenRooms booking URL. A UTM-append tag in GTM captures fbclid/gclid on first landing and re-appends campaign parameters to the SevenRooms URL when the guest clicks Reserve. Conversion pixels fire on the SevenRooms confirmation page via a GTM container installed by your Superuser contact. Without this stack, campaigns have no optimization signal and no attribution.
fbclid is dropped at the cross-domain boundary when the user navigates from your domain to SevenRooms. Meta fires a PageView on the reservation page but can't match it back to the ad click. Fix: route ads to your restaurant website first and use the GTM UTM-append tag to carry fbclid to the SevenRooms booking URL.
Two separate issues. First: Snap ignores custom freeform event names — remap to PURCHASE, ADD_CART, SIGN_UP. Second: cross-domain race condition — the Snap base pixel init in your Page View tag doesn't complete before PURCHASE fires on SevenRooms' domain. Fix: GTM Tag Sequencing, set Page View as Setup Tag for PURCHASE. Verify in Snap Events Manager Test Events, not GTM Preview.
No. Custom Auto-Tags — required for automatic no-show tagging, repeat-offender classification, and unconfirmed-slot auto-release — are a paid add-on not in the standard plan. Contact your CSM to scope and enable before configuring any no-show automation.
Paid campaigns sustain local search visibility and GBP impressions, which drives the organic awareness that produces walk-in decisions. In UAE restaurant data, a ~40% paid media reduction produced a 54% decline in walk-in traffic despite walk-ins having no direct link to any booking platform. The flywheel drives all channels simultaneously.
Reporting → Reservations Export → Filters → Status (4-tier) = Complete → Local Date = Is in range + enter dates → Run → gear icon → Download → Excel Spreadsheet → All Results → Download. Includes guest contacts, visit date, party size, booking source, spend (if POS-integrated), and UTM attribution from the booking URL.
Need help implementing this for your restaurant?
We run the full stack — SevenRooms, GTM tracking, Google Ads, Meta, Snap, WhatsApp automation, and audience building — for high-end restaurants in the UAE and GCC.
