GuestOs

Overview

Most hotels in 2026 still run guest services on paper, phone calls, and disconnected tools. A guest wants room service — they call. The order is misheard, lost, or delayed. They want to book a snorkeling excursion — they pick up a brochure in the lobby. They want to extend checkout — they queue at reception. The technology that runs the rest of their life stops working the moment they walk into the resort.

GuestOs fixes this. It's a hospitality operations platform that runs the entire guest lifecycle — from arrival through every service request to departure — through a single connected system. Guests get a native-feeling app experience with zero downloads. Staff get three real-time dashboards that replace the phone-and-clipboard chaos. Management gets visibility into operations that previously lived in heads and post-it notes.

The platform is built around three structural choices that distinguish it from legacy hospitality software: zero app friction (no app store, no signup, no password), WhatsApp as the front door (the messaging app every guest already has open), and property-isolated architecture (each hotel runs its own backend so problems never cross properties).

Who GuestOs is for

• Resorts (150+ rooms) running complex multi-service operations — dining, spa, excursions, transfers — that currently live on radios and paper tickets.
• Boutique hotels that want to deliver a five-star digital experience without a five-star IT budget.
• Hotel chains needing a consistent guest platform across multiple properties without forcing every property to use the same PMS.
• Hospitality operators in MENA serving international guests in their native languages — Arabic, English, French, Russian, Mandarin — without manual translation.

Quick Start

GuestOs is deployed per property — it's not a self-service signup. The path from interest to live operation is a structured rollout, designed to minimize disruption to your current operations while moving fast enough to deliver value within weeks.

Step 1 — Try the live demo

Start at concierge.brivox.tech/demo. It's a fully-functional GuestOs instance with sample data — order room service, browse experiences, explore the resort map, walk through checkout. Open it on your phone for the most accurate impression of how guests will experience it.

Step 2 — Book a discovery workshop

The Brivox team meets with your operations leadership to understand your property: service categories, departmental structure, PMS in use, current pain points, and what "great guest experience" means for your specific brand.

Step 3 — Receive a tailored deployment plan

Within a week of the workshop, you receive a deployment plan covering: the GuestOs configuration for your property, PMS integration approach (webhook, manual, or expanded mapping), service flows to configure, timeline to live, and pricing for both Foundation and Extended tiers.

Step 4 — Controlled rollout

Once approved, deployment runs through four phases — described in detail in Implementation Phases. Most properties go live within 3-6 weeks from kickoff to first guest using the system.

How It Works — The Guest Journey

GuestOs is best understood by following a guest through their stay. The entire arc — from before they arrive to after they depart — flows through six structured steps.

Step 1 — Arrival confirmation

When a guest's arrival is confirmed in your PMS, GuestOs receives the event. This can happen via PMS webhook (the cleanest integration), a manual trigger from reception staff, or an API call from any system already tracking arrivals. The event contains the minimum data GuestOs needs: guest name, room number, stay dates, language preference, and contact channel.

Step 2 — Secure token generation

GuestOs generates a unique UUID token linked to this specific stay. The token is one-time-use, scoped to the guest's room and dates, and expires automatically when the stay ends. There's no permanent credential created — every stay generates a fresh token.

Step 3 — WhatsApp magic link delivery

A personalized welcome message is sent to the guest's WhatsApp number through the WhatsApp Business API. The message is in the guest's preferred language and contains a single tappable link. No password setup. No app to download. No account to create.

Welcome to The Meridian, Mr. Ahmed —
your room is ready.
Tap to unlock your guest experience.

meridian.guestos.app/login?t=a3f9-e12c...

Step 4 — Instant session on tap

When the guest taps the link, GuestOs validates the token (signature, expiry, scope), creates a session, and renders the home screen personalized to that guest. The whole flow from tap to seeing the resort dashboard is under two seconds. No forms, no logins, no friction.

Step 5 — The full resort at their fingertips

From the home screen, the guest has access to everything the property offers: dining, spa bookings, excursions, room service, housekeeping requests, an interactive map, and a live tracker showing the status of anything they've ordered. The experience runs as a PWA — installable to the home screen if they want, or just a tab in their browser.

Step 6 — Departure flow

When the guest is ready to leave, the departure screen offers a stay summary, luggage pickup coordination, late checkout requests, and a one-tap notification to reception that they're departing. No queueing at the front desk for simple coordination tasks. After departure, the token expires; the guest's access ends cleanly.

The Guest App — Five Screens, Purposefully Designed

The guest app is intentionally focused. Five screens, each doing one thing well. The design philosophy is "every screen has a purpose; if a screen doesn't earn its place, it doesn't exist."

1. Home — The Hub

The first screen after the magic link tap. Personalized by guest name, room, and language. Shows live service status with one-tap quick actions, an active order tracker with real-time ETAs, the daily itinerary timeline if you've scheduled experiences, a resort services grid, and a "beyond the resort" carousel for external experiences.

Optional PWA install prompt for guests who want the home-screen icon. The experience works identically whether installed or not.

2. In-Room Dining

Full categorized menu with food photography. Add to cart, schedule delivery (ASAP or specific time slot), choose destination (room number or beach sunbed number — yes, the system knows your sunbeds by number). Orders route instantly to the Kitchen KDS the moment they're placed.

The menu is configured per property — Brivox doesn't ship a "standard" menu. Your chefs decide what appears, the photography, the categories, and the dietary tags.

3. Experiences & External Services

Curated cards for everything beyond the property itself: excursions, yacht charters, safari tours, scuba diving, ground transfers, day trips. Each card has clean date pickers, guest count selectors, and an optional notes field. Requests route automatically to the right team — your in-house concierge, an external partner, or a hybrid based on the experience type.

4. Interactive Resort Map

A custom-illustrated SVG map of your property with pinch-zoom and pan. Interactive pins for every meaningful location — restaurants, pools, the spa, kids' club, beach access points. Tapping a pin opens a detail sheet with hours, photos, and direct booking actions where applicable. Category filters let guests find what they need quickly.

A pulsing "Your Room" pin orients the guest spatially the moment they open the map. The map works offline — once loaded, it doesn't need a connection to navigate.

5. Departure & Review

Clean checkout flow. Stay summary grouped by category (dining, spa, experiences, etc.). Luggage pickup request with time selection. Late departure request with reception approval workflow. One-tap notify-reception button when they're walking out the door. Optional review prompt — collected at the right moment, before they've forgotten the details.

Staff Dashboards — Three Surfaces, One System

The guest app is only half of GuestOs. The other half is the three real-time dashboards your staff use to actually run operations. Each dashboard is designed for its team's specific workflow — not a generic admin panel adapted for different roles.

Reception Dashboard

The operations center. Where the property's pulse is visible at a glance.

• Active Dispatch Board — every live request from any guest, auto-routed to the right department, with elapsed-time timers and SLA alerts when response times approach thresholds.
• Guest Directory — every active guest at the property with room, arrival date, departure date, language, and VIP status visible immediately.
• WhatsApp Access Generator — one-click resend of magic links to any guest who lost theirs or needs a fresh session.
• AI Concierge Log — live feed of requests being auto-handled by the system versus those being escalated to staff. Used to identify patterns and improve routing rules over time.

Kitchen KDS (Kitchen Display System)

Designed specifically for kitchen workflow — large fonts readable from across a kitchen, color-coded urgency, and zero keyboard input required.

• Live Order Tickets — every active order with elapsed timer; ticket color shifts from green through amber to red as the SLA approaches.
• Delivery Destination — room number or beach sunbed number printed on every ticket so the runner knows exactly where to go.
• One-Tap Status Update — chef taps "in progress" when cooking starts, "ready" when plated, "delivered" when handed off. Guest sees each status change live.
• Audio + Visual Alerts — sound and flash for every new order. No order missed, even on the busiest service.

Management Dashboard

The analytics layer. Built for GMs, ops directors, and ownership — not for operators.

• Operations Analytics — daily, weekly, monthly activity across all departments. Volume, response times, peak hours, service mix.
• SLA Performance — average response time per department with breakdowns by service type. Identifies which teams are meeting commitments and which need help.
• Guest Behavior Insights — most-ordered dishes, most-popular experiences, usage patterns by guest nationality and demographic. The data that informs menu changes and partnership decisions.
• Exportable Reports — one-click export for any period in formats suitable for ownership reporting, board decks, or regulatory submissions.

WhatsApp Integration

WhatsApp is GuestOs's front door. The choice isn't aesthetic — it's structural. In MENA, the GCC, and most of the world that matters to international hospitality, WhatsApp is the messaging app every guest already has open. Using it as the entry point means zero friction at the most important moment of the stay.

How the WhatsApp flow works

GuestOs uses the official WhatsApp Business API through approved messaging partners. Every property gets a verified business number (or uses one you already have). The platform sends three types of messages:

1. Welcome / Magic Link — sent on arrival confirmation with the tappable session link.
2. Service Confirmations — order placed, order in kitchen, order out for delivery, order delivered.
3. Important Updates — service delays, special offers from the property, departure reminders.

What it doesn't do

GuestOs does not use WhatsApp for two-way conversational guest support. The platform is designed around the app experience, not chat. WhatsApp delivers the link and important notifications; everything else happens inside the PWA. This is deliberate — chat-based hospitality systems consistently underperform structured ones for complex multi-service operations.

PMS Integration

Your Property Management System is the authoritative source of guest data. GuestOs is designed to live alongside it, never replace it. The integration approach scales based on your PMS's capabilities and your operational preferences.

Integration patterns supported

Manual triggers (simplest)

Reception staff confirms arrival in GuestOs manually after checking the guest in to the PMS. Two steps instead of one, but no technical integration required. Works with any PMS, including legacy systems without modern APIs.

Webhook-based (recommended)

Your PMS fires a webhook to GuestOs whenever an arrival is confirmed. The arrival event includes guest details and triggers the GuestOs flow automatically. Most modern PMSs support webhook configuration; the Brivox team configures the integration during implementation.

Expanded PMS mapping (Extended tier)

Deep bidirectional integration where GuestOs receives more than just arrival events — room status changes, billing events, departure confirmations, room change notifications. Enables tighter coordination with PMS-managed workflows.

PMSs we've integrated with

GuestOs has shipped integrations with Opera, Protel, Mews, Cloudbeds, RoomRaccoon, and several regional PMSs common in the MENA market. If your PMS isn't on this list, the integration is scoped during discovery based on its API capabilities.

Security & Reliability

Guest data is sensitive. Names, room numbers, stay dates, dietary restrictions, payment patterns — this is information that requires both security in the technical sense and operational discipline in the business sense. Every architectural decision in GuestOs prioritizes both.

Auto-expiring sessions

No guest credential is permanent. Every magic link is one-time-use and scoped to a single stay. When the stay ends, the token expires. There is no "guest account" that persists between visits — every visit generates a fresh session. This eliminates an entire class of credential-leak risks.

PMS as source of truth

GuestOs never overrides PMS data. If your PMS says a guest has checked out, GuestOs respects that even if our own state was different. This boundary is structural — it prevents the dangerous patterns where a guest-facing system gets out of sync with the system that owns billing and operations.

Manual fallback always available

If anything fails — WhatsApp delivery, the PWA, the PMS webhook — reception staff can complete every operation manually through the dashboard. No guest is ever stranded because a digital system glitched. The fallback is part of the design, not an afterthought.

Property-isolated architecture

Each hotel runs its own GuestOs backend instance. A bug, outage, or compromise affecting one property cannot reach another. For chains, this is critical — the cost of cross-property contamination far outweighs the operational overhead of separate instances.

Transport and storage encryption

TLS 1.3 on all traffic. AES-256 encryption at rest. Webhook payloads from PMSs are signed with HMAC and verified before processing. WhatsApp messages flow through Meta's official infrastructure, which provides end-to-end encryption to the guest's device.

Deployment Tiers

GuestOs ships in two tiers — Foundation and Extended — designed to match different operational complexities. Most properties start with Foundation and grow into Extended over time.

Foundation tier

Everything needed to run guest operations through GuestOs end-to-end.

• Guest App: Arrival flow, service requests, dining, interactive map, departure
• Dashboards: Reception + Kitchen KDS
• Services: Core resort services (dining, room service, housekeeping)
• Integrations: Manual triggers or webhook-ready PMS connection
• Security: Magic links + property-isolated backend
• Launch: Controlled rollout with internal soft-launch period

Extended tier

Foundation plus the capabilities most properties grow into within their first six months.

• Guest App: Custom flows per property (loyalty integration, multi-language depth, branded experiences)
• Dashboards: Foundation + Management dashboard with analytics
• Services: Core + external partners (excursions, transfers, third-party experiences)
• Integrations: Expanded PMS mapping with bidirectional sync
• Security: Property-specific hardening (custom auth flows, additional logging, audit trail extensions)
• Launch: Foundation rollout + training program + formal handover package

Which tier to start with

Implementation Phases

GuestOs deployments run through four structured phases. The total time from kickoff to a first guest using the system is typically 3-6 weeks; full operational maturity is usually reached within the first 60 days.

Phase 1 — Discovery Workshop

A working session with your operations leadership. The Brivox team maps your property structure: service categories, departmental hierarchy, guest journey priorities, current pain points, and operational philosophy. Output: a written configuration plan you approve before any technical work begins.

Phase 2 — Property Configuration

Brivox configures GuestOs for your specific property: dining menus with your photography, service flows matching your departments, the illustrated resort map drawn for your property, dashboard permissions per role, operational routing rules, and language packs for the markets you serve.

Phase 3 — Team Onboarding

Reception, kitchen, and (for Extended tier) management teams are walked through their workflows. Training is hands-on with the actual configured system, not a generic demo. Each team practices in a controlled internal launch — staff playing guests, real workflows, but no real guests yet.

Phase 4 — Live Refinement

First real guests use the system. The Brivox team observes the first operating window closely — first weekend, first peak season, first major event — and tightens edge cases that surface only under real conditions. After this stabilization period, your team operates GuestOs independently with standard support.

Customization

No two properties operate identically. GuestOs is built with the assumption that every deployment will need customization, and the platform is structured to absorb customization without forking.

Configurable without code

• Service catalog — what services appear in the guest app and how they're categorized
• Dining menus — items, photos, categories, dietary tags, pricing
• Routing rules — which requests go to which department, with which SLAs
• Language packs — translations and locale-specific content
• Branding — colors, logos, typography, splash screens
• Dashboard permissions — who sees what, who can do what
• WhatsApp templates — the welcome message, the service confirmations, the departure reminder

Custom development

Beyond configuration, properties with unique workflows can commission custom modules:

• Bespoke experiences for unusual amenities (private islands, helicopter transfers, wellness retreats)
• Custom integrations with loyalty programs, CRMs, or revenue management systems
• Property-specific dashboards beyond the standard three
• Branded native apps wrapping the PWA (for chains that require app-store presence)

Custom development is scoped separately during discovery and quoted explicitly. All customizations are designed to remain compatible with future GuestOs platform updates.

Frequently Asked Questions

Do guests really not need to download anything?

Correct. GuestOs is a Progressive Web App delivered through a WhatsApp link. The guest taps, the PWA opens in their browser, and they have full access. They can optionally "install" it to their home screen with one tap, but it works identically whether installed or not.

What if a guest doesn't use WhatsApp?

The magic link can be delivered via SMS, email, or printed as a QR code on a welcome card in the room. WhatsApp is the default because it has the lowest friction for most international guests, but the underlying token mechanism is delivery-agnostic.

Does GuestOs replace our PMS?

No. GuestOs sits alongside your PMS, receives arrival events from it, and respects it as the authoritative source of guest data. Replacing a PMS is a separate (and much larger) project that GuestOs is not designed for.

How long does implementation take?

Typically 3-6 weeks from kickoff to first guest using the system, with the bulk of that time in property configuration and team training. Smaller properties with simpler service catalogs deploy faster; larger resorts with extensive experience catalogs take longer.

Can we customize the system for our brand?

Extensively. Branding (colors, typography, splash screens), service catalog, menus, routing rules, dashboard permissions, and WhatsApp message templates are all configurable. Bespoke development for unique property needs is available on top of the standard platform.

What happens to guest data after they leave?

The session token expires at departure. Guest interaction data — orders, requests, satisfaction signals — is retained according to your property's data retention policy and aggregated for the Management Dashboard analytics. Individual PII is handled according to GDPR and local data protection regulations applicable to your property.

Can it run multiple languages?

Yes. The platform auto-detects guest language from PMS data or device locale, and serves the full app experience in that language. Standard language packs include English, Arabic, French, Russian, German, Spanish, Italian, and Mandarin. Additional languages are available on request.

What's the pricing model?

Pricing is determined per property based on size, tier (Foundation or Extended), services included, PMS integration complexity, and customization scope. Contact Brivox for a tailored proposal — there's no public price list because no two properties are operationally identical.

Is there a multi-property version for chains?

Yes. For chains, GuestOs can be deployed with shared analytics across properties while maintaining property-isolated operational data. Each property runs its own instance; the management layer aggregates for chain-level visibility.