Coastal resort, golf and spa
A resort front desk that runs on WhatsApp — without replacing the PMS
Thalassa Crest wanted guests to book, get reminders, reach the concierge, approve charges and leave feedback from the app they already have open. What it did not want was another system to migrate to. The conversation layer sits on top of the PMS and booking engine the resort already runs.
- Hospitality & Golf
- PMS Integration
- Multilingual
- Managed by Arino One
Add a channel, not another source of truth
A resort this size already runs a property management system, a booking engine and channel manager connections into the OTAs — and all of it works. The usual way "add WhatsApp" gets sold is as yet another platform, with its own guest database and its own inbox. That leaves the front desk reconciling two versions of the truth, and the guest talking to whichever one happens to be stale.
- 01
A PMS that already works
The resort runs a property management system, a booking engine and channel manager connections into the OTAs. None of it was up for replacement.
- 02
Two versions of the truth
Most "add WhatsApp" products arrive with their own guest database and their own idea of who is arriving tomorrow, leaving the front desk reconciling exports.
- 03
Requests trapped on the phone
Towels, a dinner reservation, a tee time — every small request still meant a phone call to a desk that was already busy.
- 04
Charges approved at a desk
A spa treatment or room charge required a card reader or a queue at checkout, rather than a tap in a thread the guest already had open.
- 05
An international guest mix
Guests write in French, German, Italian and Spanish. Staffing a language desk for every shoulder season was never realistic.
- 06
Feedback nobody answers
Post-stay surveys sent by email after departure were, predictably, ignored.
The guest journey, end to end
The architecture is deliberately dull. A reservation is created, the source system fires a webhook, Arino One matches the guest and starts the WhatsApp conversation. Rooms, rates, folios and guest records never move: the PMS stays the single source of truth and the conversation layer reads from it and writes back what the guest decides.
Booking confirmation
The reservation fires a webhook from the PMS, booking engine or OTA. Seconds later the confirmation lands in WhatsApp with dates, room and a link to amend.
Pre-arrival with buttons
A few days out, interactive buttons ask for arrival time, early check-in or an airport transfer — answered with a tap instead of a phone call.
In-stay concierge
The same thread carries every request during the stay: housekeeping, restaurant reservations, tee times, activities.
Spa booking in chat
Treatments are booked inside the conversation against live availability, with the confirmation written back to the resort's systems.
Payment approval
A room or spa charge is approved with a one-time code in WhatsApp, then written back to the folio in the PMS. No app, no card reader, no queue.
Post-stay feedback
A short prompt goes out on the channel the guest has used all week — which is why it actually gets answered.
- Normalized PMS webhook
- Interactive buttons
- Live concierge inbox
- Spa availability in chat
- One-time-code payment approval
- Automatic translation
- Consent & opt-out
- Campaign analytics
A live concierge inbox, inside the tools staff already use
No one had to learn a new product. The point of the project was that the front desk's day looked the same, only with a faster channel attached to it — and with the reservation context sitting beside every message.
Real-time concierge inbox
Every inbound message lands in the staff dashboard the team already opens each shift, in real time, with reservation context attached.
Assignment and shift handover
Threads can be assigned, handed over at shift change and picked up by whoever is free — no request quietly owned by nobody.
Multilingual by default
A guest writes in French; the concierge reads and replies in English; the guest receives French. The team staffs for the languages it has.
Operator visibility
Delivery and read rates, response times by shift, and where threads stall — plus targeted campaign sends to consented segments only.
Because the PMS remains authoritative, nothing in the inbox can drift from what the front desk sees in the reservation system.
What the deployment delivers
- WhatsAppPrimary guest channel, live
- No migrationPMS and booking engine unchanged
- Webhook inBooking.com, Cloudbeds, Mews or direct
- Real timeConcierge inbox for the whole shift
- MultilingualGuest writes any language, staff reply in theirs
- EU-hostedGDPR tooling and consent built in
- Live demoOpen to walk today
See it running
A short video set on YouTube: how the layer sits on top of the PMS, the full guest stay, the live concierge inbox, and the operator view behind it.
- PositioningDoes This Replace Your Hotel's PMS? (No — Here's How It Actually Works)Watch on YouTube →
- Guest JourneyThe Entire Guest Stay, Run Through WhatsAppWatch on YouTube →
- ConciergeReal-Time WhatsApp Concierge: Guest Messages, Staff See It InstantlyWatch on YouTube →
- MultilingualOne WhatsApp Inbox, Every Guest LanguageWatch on YouTube →
- Operator ViewBuilt for Hotel Operators: Analytics, Campaigns & Multilingual SupportWatch on YouTube →
A faster front desk, on systems the resort already owns
Requests that used to occupy the phone now resolve in a thread, charges are approved without a queue at checkout, and post-stay feedback arrives where the guest is already reading. The resort kept its PMS, its booking engine and its OTA connections intact — the only thing that changed is that guests can now reach it the way they message everyone else.
Questions about this deployment
Does this replace the resort's PMS?
No. The conversational layer connects to the existing PMS or booking engine through a webhook — reservations, room inventory, billing and guest records all stay exactly where they are. Arino One adds the WhatsApp conversation on top; it doesn't touch or duplicate what the PMS already owns.
Does it work with Booking.com, Cloudbeds, or Mews?
Yes — the integration is a normalized webhook, not a point integration built for one provider, so it accepts a reservation from any PMS or OTA that can send a webhook, including Booking.com, Cloudbeds, Mews, or a resort's own direct booking engine.
Is guest messaging like this GDPR compliant?
Consent and preference come first — guests opt in to WhatsApp messaging as part of the booking flow, can opt out at any time, and the instance is EU-hosted with GDPR tooling built in, the same as every other Arino One instance.
How long does it take to go live?
The messaging layer connects to an existing PMS/booking engine via webhook in days, not months — the resort's underlying systems require no migration or downtime.
Try Thalassa Crest yourself
The full journey is running as an interactive demo. Book a stay, message the concierge and approve a charge exactly as a guest would.
This is a live demo environment — nothing is real, no bookings, no charges. Walk the journey with the on-screen demo details; no real reservation or phone number needed.
Dedicated instance
Thalassa Crest runs on its own Arino One instance, not a shared tenant.
GDPR-aligned
Opt-in captured at booking, opt-out honoured at any time, retention controlled.
Regional hosting
EU, NA and APAC hosting options for data residency requirements.
Managed by Arino One
Provisioned, operated and supported end to end by Arino One.