Properties, reservations and guest messages
KrossBooking
The account is connected with the existing hotel ID and login. Reservations and conversations sync in, and enabled replies return to the same thread.
How KrossBooking connectsIntegration stack · KrossBooking + EasyPick + WhatsApp
Use KrossBooking for reservations and guest messages, EasyPick for key-locker status and WhatsApp for cleaner or guest coordination.
Who this stack is for
The coordination problem
The answer
Proptonomy reads the stay and guest thread from KrossBooking, checks the EasyPick locker state and coordinates any readiness work in WhatsApp. The reply goes back through the right guest channel only after the operational facts agree.
Properties, reservations and guest messages
The account is connected with the existing hotel ID and login. Reservations and conversations sync in, and enabled replies return to the same thread.
How KrossBooking connectsKey locker, compartment state and pickup code
The AI can check whether the relevant key is in or out and use the active code at the point your access rules allow it.
How EasyPick connectsCleaner, local operator and guest coordination
The person responsible for readiness can confirm timing or return a photo in the chat they already use, with no portal to learn.
How WhatsApp connectsExample workflow
The stack matters only if the same operational record survives the handoff between tools and people.
The guest message is matched to the reservation, room and arrival time so the AI knows which access rule and locker assignment apply.
Before promising access, Proptonomy checks the assigned locker and whether the key is currently present rather than relying on an old note.
If the home or key is not ready, the responsible partner receives the exact unit and deadline and is chased until a confirmed time comes back.
The reply returns to the KrossBooking thread or direct WhatsApp conversation. The code is shared only when the timing, readiness and access policy allow it.
Boundaries
A trustworthy integration explains the non-goals as clearly as the data flow. These boundaries prevent duplicate records and unexpected writes.
Properties and reservations are read, not edited. Guest replies can go back through KrossBooking after the relevant inbox is enabled.
The locker and current code come from EasyPick. Proptonomy uses that live state inside the guest workflow rather than becoming a lock platform.
A code is not sent merely because a guest asked. Reservation validity, timing, readiness and your property rules are evaluated first.
Rollout
The exact credentials differ by system, but the safe operating sequence stays the same.
Connect KrossBooking, EasyPick, 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.
Proptonomy connects with the hotel ID, username, password and emailed two-factor code used for the KrossBooking account. Properties, reservations and guest conversations sync in, and replies can return to the thread.
Yes. The EasyPick connection exposes the relevant locker state and active pickup code so the AI can answer from the current physical state instead of a static instruction.
Yes. Cleaners and local operators can receive briefs, confirm readiness and return photos in their existing WhatsApp chats or groups.
No. Properties and reservations are read from KrossBooking. The write-back in this workflow is the guest reply on the existing conversation, after you enable it.
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.