Room types, reservations and calendar context
Resly
An API key supplies who is staying where and when. The connection is read-only and does not edit Resly records.
How Resly connectsIntegration stack · Resly + WhatsApp + Gmail
Use Resly for room types and reservations while Proptonomy answers and coordinates guests through WhatsApp and Gmail without writing back to Resly.
Who this stack is for
The coordination problem
The answer
Proptonomy reads room types and reservations from Resly, then uses its own WhatsApp and Gmail connections for conversation and coordination. Resly stays read-only. The AI can answer from the stay context, dispatch work and keep chasing it without pretending the PMS has a messaging write-back it does not have.
Room types, reservations and calendar context
An API key supplies who is staying where and when. The connection is read-only and does not edit Resly records.
How Resly connectsFast guest and partner conversations
Guests, cleaners and maintenance partners can be answered or briefed in their own language on the channel already on their phone.
How WhatsApp connectsEmail from the address guests already recognise
Selected inbox threads are matched to the correct property and reservation, and approved replies leave from the connected Gmail address.
How Gmail connectsExample workflow
The stack matters only if the same operational record survives the handoff between tools and people.
The phone number, email address or booking reference is matched against the current Resly reservation so the AI can identify the stay.
Dates, room type, arrival state and property knowledge are combined with the conversation instead of relying on a generic chatbot response.
If the guest needs a person on site, the cleaner or vendor is briefed through WhatsApp or email and followed up against a task and deadline.
The guest receives the completion message in WhatsApp or Gmail. The reservation context remains read-only in Resly.
Boundaries
A trustworthy integration explains the non-goals as clearly as the data flow. These boundaries prevent duplicate records and unexpected writes.
Room types and reservations sync into Proptonomy, but the AI does not edit those records or write a conversation back into Resly.
A WhatsApp message is answered on WhatsApp and a Gmail thread from the connected mailbox, preserving the conversation the guest sees.
New inboxes begin in observe mode. Your team reviews what would be sent and enables automatic replies only where it is comfortable.
Rollout
The exact credentials differ by system, but the safe operating sequence stays the same.
Connect Resly, WhatsApp, Gmail 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. The Resly connection is read-only for room types, reservations and calendar context. Guest conversations use connected Proptonomy channels such as WhatsApp and Gmail.
It first uses the guest phone number and current reservation data. If there is no confident match, it asks for a booking reference before using reservation-specific information.
Yes. Connect the mailbox you want the operation to use. Proptonomy matches the thread to the reservation and sends approved replies from that address.
Yes. A guest request can become a task and a partner brief on WhatsApp or email, with automatic follow-up until the partner confirms completion.
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.