Resort Buggy

Talk to every guest in their own language.

Guests write in theirs, your front desk reads it in yours — translated on the resort’s own server by default.

Guest chat on a phone: a guest writes in French and reads the resort's English replies translated, with the original text under each message

The guest’s side: French in, French out.

The WhatsApp number on the welcome card is a single point of failure.

One shared handset behind the desk. A guest writes in Russian at 23:10; whoever holds the phone pastes it into a translator, types an answer, pastes it back. The morning shift never sees the thread — it lives in one device’s history, behind one login, in whatever language the last person left it in.

Purpose-built guest chat replaces the handset, not the humans: every conversation translated both ways as it happens, tied to the villa and the stay, visible to the whole team. Guest messages are translated on the resort’s own server by default.

How it works

The same conversation, from both sides of the desk.

1

The guest writes in their own language

From the chat tab, a guest types the way they think — “Write in your own language” is the whole instruction. No number to save, no messaging app to install.

2

Your team reads it in theirs

The front desk sees the message in English with the guest’s original underneath, and replies in English — the guest reads the answer in French. Both sides keep the original in view.

3

The thread belongs to the stay

The conversation is pinned to the villa and the stay dates, with read receipts. Night shift and morning shift open the same history — nothing lives on one shared handset.

The guest's phone: writing in French, reading replies in French with the English original underneath

The guest’s phone

The front desk's phone: the same conversation in English, pinned to Ocean Villa 12 and its stay dates, with one-tap Maintenance work-order chips

Your front desk

What it does today

Twelve languages in guest chat

Guests write and read in their own language, your team in theirs — translated live in the thread, both directions.

Private by default

Guest messages are translated on the resort’s own server by default.

The original stays visible

Every translated message carries the original text underneath it, on both sides — so nothing important hides behind a translation.

Read receipts

Both sides see when a message has been read — no more wondering whether the request about the towels ever reached anyone.

One thread per stay

Each conversation is tied to the villa and its stay dates. Any team member who opens it sees the full history, whatever the shift.

Complaint to work order

A maintenance complaint in chat becomes a work order in one tap — the blocked drain goes straight onto the housekeeping board.

It works alone — and with the rest of the stay

Chat runs on its own. The same app can also carry the rest of your guest operation, whenever you’re ready.

A ride on the way: the driver approaching on the live island map with an arrival estimate
Ride complete screen with a one-tap five-star rating

And when you’re ready for dispatch: the same guest app requests a buggy, tracks it live to the pickup, and takes a one-tap rating when the ride ends — chat sits one tab over the whole time.

Priced per villa. Piloted for free.

Pricing is per villa, per month, with a free pilot before any commitment and payment by simple bank transfer. The tiers are on the pricing page.

Go deeper

For the criterion-by-criterion comparison of the shared handset and purpose-built guest chat, read Guest Messaging for Resorts: Where the WhatsApp Number on the Welcome Card Breaks. For the four options a property actually chooses between — a shared inbox, WhatsApp Business API, PMS messaging, or purpose-built — read four guest messaging options compared — and the operations glossary defines the terms.

Common questions

Do we need to run buggies to use this?
No — chat works on its own, and most properties start staff-side. The guest app does include a ride option alongside chat, so guests will see a ride tab even if your fleet isn’t on the system yet. Nothing about messaging depends on it.
How is this different from SMS or the WhatsApp number at the desk?
It isn’t a texting tool. No guest phone numbers are collected and none of your staff’s personal numbers are exposed — guests scan the villa card and chat opens in the browser. The conversation is one per-stay thread every staff member can see, translated live in both directions, instead of a message history locked inside one handset.
Where does the translation happen?
Guest messages are translated on the resort’s own server by default.
How many languages does it support?
Twelve in guest chat. A guest picks theirs once — or just starts typing — and every message in the thread is translated both ways from then on. The staff side is a separate list, chosen for who you employ rather than who you host: the staff app runs in seventeen languages, and checklist text is translated into twelve of those seventeen.
What happens when a guest writes at 23:10?
The message sits in the thread, translated and marked unread, until someone answers. Morning shift opens the same conversation night shift saw — with the full history — instead of a pasted-together screenshot on a shared phone.
Do guests need to install anything?
No. Guests scan the QR card in their villa and chat opens in the browser, in their language. No app store, no account setup — see how villa QR cards work.

See both sides of a translated conversation, live.

A 20-minute walkthrough of guest chat — the guest’s phone and your desk, translating in both directions as you watch.