Interact

The message thread shows the booking, the folio, and the door log.

A guest WhatsApps about early check-in. The agent sees their reservation, their loyalty tier, their purchase history, and that their door code activated fourteen minutes ago. Every channel. One operational record.

Interact · Act 1

The message with context no inbox has

The guest texts. The agent sees $4,200.

A guest WhatsApps the hotel asking about late checkout. The message arrives on the same record as their three-night booking, their Gold loyalty tier, their $4,200 lifetime value, and last Tuesday's $78 spa charge. The agent answers in twelve seconds. No tab-switching. No "can you spell your last name?"

A returning guest emails about airport transfers. The system matches the sender to the contact record from their stay last March. The agent sees the noise complaint, the comped breakfast, and the 4-star review. The reply starts with context, not questions.

Message thread with operational context panel showing booking, folio, loyalty, and door access data alongside the conversation

Duve shows the message. This shows the message, the minibar charge, and the door that never opened.

The difference between a messaging inbox and a messaging inbox on an operational database.

Every channel writes to one record

The call recording sits next to the folio.

The guest calls the next morning. The phone system shows the agent the guest's name, their booking source, and yesterday's WhatsApp thread before they pick up. The AI receptionist handles "What time is checkout?" at 2am without waking the front desk.

The guest's WhatsApp from Tuesday, the email from Thursday, the call recording from Friday morning, and the $78 spa charge from Wednesday afternoon. One scroll. The spa charge matters because the guest is asking about the bill. A messaging platform without the folio cannot answer that question.

Contact timeline showing chronological messages across WhatsApp, email, and phone interspersed with operational events (charges, door access, loyalty updates)

A guest messages "the AC isn't working" via WhatsApp.

The front desk creates a support ticket directly from the message thread. The ticket carries the guest's contact record, booking details, and communication history into the Desk support queue.

The support agent has full context without asking the guest to repeat anything. The message, the booking, and the work order share one record.

Pricing

What it costs

Each communication channel is a separate line item. Business email at EUR 4/$5 per month. The messaging inbox at EUR 13/$15 per month. Voice at EUR 13/$15 per month plus minutes. Video at EUR 13/$15 per month. The unified contact timeline is free with any channel.

A hotel running the messaging inbox, business email, and voice for 10 front desk staff pays approximately $350-430 per month. Every message lives on the same record as the booking, the folio, and the loyalty tier.

Guest messaging platforms like Duve cost $120-200 per month. They show the message. They do not show the minibar charge next to it.