Guest chat is not your property system
Night desks already live in WhatsApp because guests do. That does not make the thread the reservation. CoPulse is engagement: a Project inbox, agents, and campaigns. It is not a property management system, channel manager, or point of sale. RFPs that ask chat to hold room inventory stall after the demo.
- Category, not a pre-arrival recipe
- Jobs will live on playbooks
- How-tos will live on guides
What this post is for
This is a 2026 note for operators who want one product to be front office, housekeeping, and the OTA contract. Confirmations, pre-arrival, dining upsells, and reviews will get their own playbook and guide URLs later. This page stays the category split.
Shift handoff is not room inventory
A guest messages the number on the key folder. Night audit cannot see the afternoon thread because it lived on a supervisor’s personal phone. That is an engagement failure. A sold-out date that chat invents is a PMS failure. Solving the first with CoPulse does not retire the second.
Put the property number on the Organization. Let inbox handoff name the person on duty. Keep slot truth — room, rate, availability — in the PMS you already run. Autonomous success is sends and reads, not “checked in.”
What CoPulse will not pretend
Connecting a channel does not replace the front-office system. SMS is a Setup channel, not a promise here. Wallet meters usage. When hospitality playbooks ship, they will own booking and stay jobs. Do not clone them onto this slug.
Where to go next
Use the industry hub now. Use /industries/hospitality/playbooks when those leaves exist.
Keep the guest thread across shifts
Connect a Project channel and meter the wallet — without pretending this is the PMS.
Start free