Reservation and guest-message system of record
Guesty
Properties, reservations and guest conversations provide the stay context. Approved replies return to the Guesty thread the guest already uses.
How Guesty connectsIntegration stack · Guesty + Enso Connect + WhatsApp
Use Guesty for reservations and messages, Enso Connect for guidebooks and verification, and WhatsApp for guests and partners, coordinated by Proptonomy.
Who this stack is for
The coordination problem
The answer
Proptonomy joins that context without replacing any of the three. It reads the reservation and guest thread from Guesty, uses the guidebook and boarding-pass state from Enso Connect, and coordinates the operational work in WhatsApp. Access details stay behind Enso's verification gate.
Reservation and guest-message system of record
Properties, reservations and guest conversations provide the stay context. Approved replies return to the Guesty thread the guest already uses.
How Guesty connectsGuidebook, check-in journey and verification gate
Guidebooks, policies and check-in steps become property knowledge. The live Boarding Pass determines whether sensitive access information can be shared.
How Enso Connect connectsGuest, cleaner and vendor coordination
The AI can brief partners in their existing chats, collect photos or confirmations and ask the operations team for approval in its own group.
How WhatsApp connectsExample workflow
The stack matters only if the same operational record survives the handoff between tools and people.
The Guesty conversation supplies the reservation, property and dates. Proptonomy checks the matching Enso Boarding Pass before composing the answer.
If verification is incomplete, the reply explains what remains instead of revealing a code. If it is complete, the answer uses the check-in steps synced from Enso.
If the key is missing or the home is not ready, the right cleaner or local operator is briefed on WhatsApp with the reservation context and asked for a confirmed time.
The confirmation returns to the original guest thread. The task and partner conversation remain attached to the same operational record for the team.
Boundaries
A trustworthy integration explains the non-goals as clearly as the data flow. These boundaries prevent duplicate records and unexpected writes.
Proptonomy does not become the channel manager or change reservation economics. Guesty remains the source for the stay and the guest thread.
The Boarding Pass, verification and guidebook remain in Enso. Live boarding-pass changes are previewed and require staff approval.
Partners keep using their existing chats. Proptonomy carries the context and outcome between the conversation and the reservation.
Rollout
The exact credentials differ by system, but the safe operating sequence stays the same.
Connect Guesty, Enso Connect, WhatsApp with the credentials or partner flow described on each integration page.
Check that properties, reservations, partner chats and external records resolve to the same operational entity before any write action is enabled.
Let the AI read current traffic, draft answers and show proposed actions. Correct property knowledge and routing while nothing is sent automatically.
Turn on the inboxes and actions the team trusts, while sensitive categories and less-tested properties remain behind approval.
FAQ
Direct answers, written to stand on their own in search and AI results.
No. Guesty remains the reservation and guest-message system of record, and Enso remains the guest-facing Boarding Pass and guidebook. Proptonomy coordinates the answering and work between them.
No. Proptonomy reads the live Enso Boarding Pass before sharing access information. If verification is incomplete, it tells the guest what is still required and holds the code.
Yes. Cleaners and handymen can be briefed and chased in their existing WhatsApp chats or groups, with photos and confirmations reflected back into the task.
Replies to a Guesty-originated conversation go back through Guesty once that inbox is enabled. Direct WhatsApp conversations remain on WhatsApp.
We will show what connects, what remains read-only and how the first real workflow runs.
Sign up in 30 seconds and we will set your team up in the next onboarding batch.