AI guest messaging for RentalReady
TravelPal connects to RentalReady with the API base URL and access token RentalReady issues once it approves your application. It then reads every conversation in the account, where Airbnb, Booking.com, Vrbo, email, SMS, and WhatsApp messages all arrive together, and answers the guest in GuestSpace, RentalReady's own portal. Anything meant for your team is filed in that same conversation on the staff channel, and a sold early check-in or late checkout becomes the booking's own arrival or departure time.
One connection, running both ways. Every item on it is detailed below.
What TravelPal reads from RentalReady
RentalReady is GuestReady's own property management system, run by professional short-term rental managers with European portfolios.
Rentals arrive keyed to the contract number
RentalReady identifies a property by its contract number, and reservations, conversations, and calendar holds all point at that same number, so a rental keeps its identity in TravelPal through a rename. Name, street address, city, photos, house rules, extra guest information, checkout instructions, earliest and latest check-in, latest checkout, and how many people the rental sleeps arrive with it. Units RentalReady still marks as onboarding are imported as well, and are not treated as taking guests.
The access codes stay behind
RentalReady's rental record holds the physical keys to a building in detail: lockbox and key box codes, lift and building entry codes, the key deposit location in two languages, the self check-in link, and the wifi password. TravelPal drops every one of those fields on the way in, so none of them is part of what the concierge reads before it answers. A guest who asks for a code gets your team rather than a guess: see what the concierge will not say.
Reservations in RentalReady's own vocabulary
There is no status called confirmed on this system: a live booking reads New and a provisional one reads Tentative, and TravelPal treats New as confirmed and Tentative as pending. Each one brings the guest's name, email, phone, and preferred language, adults plus children as the party size, the accommodation amount in the currency it was taken in, and the channel's own reservation reference, so the code the concierge reads back is the one printed on the guest's confirmation. RentalReady also has an Archived status that carries a label and no published meaning, so an archived booking is raised with your team rather than guessed at.
Owner stays and maintenance holds are not guests
RentalReady returns calendar holds in the same list as bookings, each carrying its reason: host stay, maintenance, blocked by host, upselling request. TravelPal leaves them out, so the week an owner spends in their own unit never gets a welcome message, and a booking flagged as the owner's is sent no offers.
The whole conversation, merges included
Threads arrive with every message in them, oldest first, so a booking that has been under discussion for a week is answered from the whole week and not from its latest line. RentalReady also lets two conversations be merged, and a merged thread names more than one booking at once: TravelPal matches all of them instead of losing the thread.
What TravelPal writes back
Every message goes out through RentalReady, never around it, so your own inbox shows exactly what each guest was told.
Guest replies in GuestSpace
RentalReady accepts an outbound message on two channels, its GuestSpace guest portal and a staff-only note, and the send treats the note as its default. TravelPal states the destination on every message it writes, so a reply meant for the guest is never filed somewhere only your staff can read it.
Notes only your team can read
RentalReady keeps a staff-only channel inside the guest conversation, which gives TravelPal somewhere to put what a guest should not see: what an upsell sold and for how much, a question it is holding back for one of your people, and why it stopped answering. All of it sits in the thread your team already has open.
Sold times, written onto the booking
When a guest buys a late checkout or an early check-in, TravelPal sets the departure or arrival time on the RentalReady reservation and touches nothing else on the record: the write carries only that field. The new time reaches your cleaners from RentalReady itself, rather than from somebody remembering to relay it.
Holds your team can identify
A sale that needs a night off the market goes into RentalReady's calendar with its upselling request reason attached, so the hold says who put it there and is not read as maintenance by whoever opens the calendar next.
Connected in four steps
RentalReady switches API access on for your account, and TravelPal does the rest itself.
Ask RentalReady to approve the application
RentalReady grants API access by approved application, so the first step is a note to your RentalReady account manager. They approve it, hand you the API base URL for your account, and run RentalReady's OAuth2 authorization with you once. Ask for read and write on rentals, reservations, and messages, plus read on conversations.
Paste the base URL and the token into TravelPal
Two required fields. TravelPal checks both against your RentalReady account as you save them and tells you at once if either one is wrong. Getting one wrong on this system spends nothing, so a corrected paste can go in right after.
Your portfolio imports and stays in step
Rentals become properties and past bookings are backfilled by check-in date. From then on TravelPal walks RentalReady for whatever changed since its last pass, paced under the seventy requests a minute RentalReady publishes as its ceiling, so a new booking or an edited rental reaches the concierge without anyone re-entering it.
Set the timezone with us
RentalReady's rental record has no timezone field, so each property's zone is agreed with you during onboarding. It is a few minutes of work, and it is what keeps quiet hours, scheduled messages, and checkout reminders right across a portfolio spread over several countries.
The dashboard shows the connection the whole way: connected, last sync, and any error in plain words. The rest of going live is covered in what onboarding involves.
What the RentalReady connection will not do
Every property management system draws its own lines, and the ones RentalReady draws are worth knowing before you switch anything on. TravelPal works inside them rather than around them.
One guest-visible destination, six that can be read
RentalReady carries Airbnb, Booking.com, Vrbo, email, SMS, and WhatsApp traffic into its conversations, and accepts outbound guest messages in GuestSpace, its own portal. Every reply TravelPal sends a guest therefore lands in GuestSpace rather than back inside the channel thread. Whether RentalReady then passes that message onward to the channel the guest wrote from is a question for your RentalReady account manager, and worth settling before you go live.
Stay dates stay where they are
RentalReady records where a booking came from as free text and publishes no value that means a direct booking, so TravelPal does not move check-in or check-out dates on this system. An extra night is passed to your team with the dates and the price already worked out, instead of being rewritten onto a reservation that may belong to a channel.
A hold is released by date range, not by hold
RentalReady's release call clears a window on a unit rather than the one hold TravelPal placed, and clearing the window would also drop a maintenance block sitting inside it. So TravelPal places a hold and never lifts one on its own: your team releases it in RentalReady when the offer expires.
History is read for context, not mined for answers
RentalReady labels every message that is not from the guest as staff, with no name attached, so your own team's words and TravelPal's read identically when a thread is loaded back. TravelPal uses that history to follow a live conversation, and builds your knowledge base from your documents and listing content instead of learning it from past threads.
Where the AI is not sure, it stops and asks your team rather than guessing. That is the same on every system: see the guardrails.
RentalReady integration FAQ
Does RentalReady have to switch API access on for my account?
Yes. RentalReady grants access by approved application, so it takes a note or a call to your RentalReady account manager. They approve the application, give you the API base URL for your account, and complete the OAuth2 authorization with you once. You paste those two values into TravelPal and the connection is up. The base URL is issued per account, which is why it is something they hand you rather than something we can fill in for you.
Where do my guests see TravelPal's replies?
In GuestSpace, RentalReady's own guest portal. RentalReady accepts two destinations for a message, GuestSpace and a staff-only note, so that is where every guest-facing reply goes. TravelPal still reads the Airbnb, Booking.com, Vrbo, email, SMS, and WhatsApp messages arriving in the same conversation, and answers with all of that in front of it. Ask RentalReady whether your account relays a GuestSpace message on to the channel the guest booked through.
Can my team keep private notes in the thread?
Yes. RentalReady has a staff-only channel inside the guest conversation and TravelPal writes to it. What an upsell sold, anything held back for one of your people, and the reason the concierge stopped answering all sit in the thread your team already reads, and no guest sees any of it.
Will TravelPal change a booking in RentalReady?
Partly. It sets the arrival or departure time when a guest pays for an early check-in or a late checkout, and it changes only that field on the reservation. It does not move stay dates. RentalReady records a booking's source as free text with no published value that means a direct booking, so rather than rewrite dates on a reservation that may belong to a channel, TravelPal passes extra-night requests to your team.
Not the system you run?
TravelPal connects to 33 property management systems. These are the ones nearest RentalReady in how widely they are used.
Updated