Chapter 01 / The big idea

Every task is a dynamic group chat.
That ends when the task ends.

Before · personal WhatsApp

The hotel's running on someone's phone.

Staff coordinate operations from personal accounts in groups that never close. When someone leaves, the context leaves with them.

FB Day Shift 🍳

Where are the keys for the wine fridge?? 🔑

1214:22

Engineering — All

Mario: birthday cake 🎂 4pm staff lounge!

314:18

Suite 1204 (group)

Priya: AC not cooling, guest annoyed

714:31

Mom ❤️

Don't forget to call Aunt Reena

13:02

No audit trail. A complaint at 2 a.m. lives only in someone's chat history.

Context bleeds. Deliver Ice Bucket, birthday cakes and broken ACs in the same scroll.

Walks out the door. When Mario quits, eight years of chat context goes with his phone.

→ MessageBox

With MessageBox · task-as-chat

Each task spins up its own room. With everyone who needs to be there.

The chat is opened by the task, populated by the system, and archived the moment the work closes — with every message preserved.

ENG-7741 · Suite 1204

● In progress · Mario R.

14:48SLA 6m

FB-9982 · Deliver Ice Bucket

Resolved · Ice Bucket delivered, 14:24

Closed

HK-3318 · Lost & Found

@Aishwarya logged · pearl earring

14:18

PM-441 · HVAC quarterly

Scheduled · Fri 09:00

queued

One thread per task. Searchable forever. Read by the next shift like a book.

System events inline. Created, assigned, escalated, closed — all in the same scroll.

Closes when the work closes. No zombie groups. No "anyone still in this chat?"

Chapter 02 / The unfair advantage

Your team already knows how to use it.
They've been using it for years.

F.01 — Local history

Cloud-backed.
Phone-resident.

Despite being cloud-based, MessageBox keeps a local cache on every phone. Open the app on a flight, scroll the history. Same as WhatsApp.

● Local · 2.4 GB Synced 14:52 E2E

F.02 — Search

Lightning. Because it's local.

Three years of staff history, searchable in <100 ms because the index lives on the device.

⌕ pool pump leak

→ 12 hits across 3 years · 47 ms

F.03 — All chat types

1-to-1.
Groups. Channels.

A quick DM to the FOM. A department broadcast. A task room with seven people. The same UI patterns staff already know.

M

Mario R.DM

EN

Engineering · All42

#

ENG-7741task

F.04 — All the frills

Star. Pin. Reply.
Forward. Mute.

Every interaction users expect from a modern messenger — emoji reactions, quoted replies, message info, voice notes, mute. Nothing missing.

⭐

📌

↩

↪

😀

🔇

📋

ⓘ

Chapter 03 / Coordination

Pull people in.
Or quietly watch.

Mentions

Tag a name.
It shows up in their own queue.

Drop @someone into any task chat and they get a notification — plus a dedicated "mentioned me" view, so nothing slips when 200 tasks are flying around.

MR

Mario R. mentioned you in ENG-7741 “@Lana can you keep them comfortable for 15 min?”

14:33

PV

Priya V. mentioned you in HK-3318 “@FOM the lost item is from the suite that just departed”

13:58

AC

Amit C. mentioned you in FB-9982 “@Bar wine fridge key — was it returned to the cabinet?”

12:14

Watchers

Subscribe to a task without being on it.

The duty manager doesn't need to be assigned to every ticket — but might want to know how the late-night ones are going. One tap to watch. A separate view for everything you're watching.

ENG-7741 · AC complaint, Suite 12043 messages · last activity 2m ago

New

HK-3318 · Lost pearl earring, Suite 9068 messages · awaiting guest reply

Watching

FB-9982 · VIP dinner, lobby restaurant23 messages · ETA 19:00

Watching

Chapter 04 / Why move off WhatsApp

A consumer messenger
was never going to be this.

20M+

Staff chats handled · per month

Hotels send around 20 million staff-side chat messages a month through MessageBox. That's twenty million pieces of operational truth — guest complaints, shift handovers, room photos, status changes — that do not live on a personal phone, in a consumer cloud, or under someone's WhatsApp Web tab at home.

It's the product the audit team didn't know they wanted, in a UI the floor team already knows how to use.

S.01 · Encryption

At rest. In Transit. By default.

All messages encrypted in transit and at rest. Per-tenant keys, optional customer-managed keys for enterprise.

S.02 · Off-boarding

Mario quits.
The chat stays.

When a staff member leaves, their device is wiped, their account revoked, and every conversation they were part of stays in the property's archive.

S.03 · Audit posture

SOC2 · ISO 27001 · GDPR.

What an auditor sees: timestamps, signed events, no off-platform shadows. What a guest's lawyer sees: a clean record. Same artefact, both audiences.

Chapter 05 / The full kit

Sixteen frills,
because the small things are the product.

The full messaging surface, written out.

16 features · all standard

StarSave for later

PinTop of conversation

ReplyQuote & respond

ForwardSend to another chat

ReactionsEmoji feedback

MutePer-chat or global

CopyClipboard, formatted

InfoRead receipts & meta

Chat ListsCreate multiple lists

Voice notesTap-and-hold

PhotosFrom camera or gallery

FilesPDFs, invoices, plans

Mentions@ a name, anywhere

WatchersSubscribe silently

SearchLocal · sub-100ms

Last SeenView user last seen time

⌘

— A 30-minute walkthrough is enough

Stop running your hotel
on someone's personal phone.

We'll set up a sandbox tenant for your property and create one department's groups for free. Pilot two weeks. No contract.

Book a slot Schedule a demo ↗ WhatsApp us · +1 601 843 9486 ↗ LINE chat us ↗ Or write to hello@messagebox.ai

Hotels

Facility Management

Resources

WhatsApp habits. Hotel-grade discipline.

Every task is a dynamic group chat.
That ends when the task ends.

The hotel's running on someone's phone.

Each task spins up its own room. With everyone who needs to be there.

Your team already knows how to use it.
They've been using it for years.

Cloud-backed.
Phone-resident.

Lightning. Because it's local.

1-to-1.
Groups. Channels.

Star. Pin. Reply.
Forward. Mute.

Pull people in.
Or quietly watch.

Tag a name.
It shows up in their own queue.

Subscribe to a task without being on it.

A consumer messenger
was never going to be this.

At rest. In Transit. By default.

Mario quits.
The chat stays.

SOC2 · ISO 27001 · GDPR.

Sixteen frills,
because the small things are the product.

The full messaging surface, written out.

Stop running your hotel
on someone's personal phone.

Cookies — the essential kind, and the optional ones.

WhatsApp habits. Hotel-grade discipline.

Every task is a dynamic group chat.That ends when the task ends.

The hotel's running on someone's phone.

Each task spins up its own room. With everyone who needs to be there.

Your team already knows how to use it.They've been using it for years.

Cloud-backed.Phone-resident.

Lightning. Because it's local.

1-to-1.Groups. Channels.

Star. Pin. Reply.Forward. Mute.

Pull people in.Or quietly watch.

Tag a name.It shows up in their own queue.

Subscribe to a task without being on it.

A consumer messengerwas never going to be this.

At rest. In Transit. By default.

Mario quits.The chat stays.

SOC2 · ISO 27001 · GDPR.

Sixteen frills,because the small things are the product.

The full messaging surface, written out.

Stop running your hotelon someone's personal phone.

Every task is a dynamic group chat.
That ends when the task ends.

Your team already knows how to use it.
They've been using it for years.

Cloud-backed.
Phone-resident.

1-to-1.
Groups. Channels.

Star. Pin. Reply.
Forward. Mute.

Pull people in.
Or quietly watch.

Tag a name.
It shows up in their own queue.

A consumer messenger
was never going to be this.

Mario quits.
The chat stays.

Sixteen frills,
because the small things are the product.

Stop running your hotel
on someone's personal phone.