AI that answers your Hostfully inbox
TravelPal answers your guests in the Hostfully thread for their stay. It connects with an API key from Agency Settings and your agency UID.
One Hostfully connection works in both directions. Each item is explained below.
What TravelPal reads from Hostfully
Vacation rental property management companies that run their properties, their booking site, and their digital guidebooks on Hostfully. Hostfully says it has more than 62,000 properties.
A property, built from all three of its records
Hostfully keeps the facts about the building, the written descriptions, and the amenity list in three places. TravelPal pulls all three into one property and the AI answers from it. That includes the address, room and bed counts, and amenities. It also has the check-in window, the checkout hour, and the minimum and maximum stay. It also includes the property time zone, so quiet hours follow local time. Hostfully has no field for house rules, so rules come from your knowledge base.
Leads, filtered down to real stays
Hostfully keeps bookings, inquiries, holds, owner blocks, duplicates and its own sample records in one record type. It is called a lead. TravelPal sets up a guest only when the lead is a booking and its status is booked. So a held date gets no greeting, and an owner block is not treated as an arrival. Each real one brings the channel it came from and the channel's own confirmation code. It also brings the party count and the guest's preferred language.
One thread per stay, with every sender named
Hostfully keeps one thread for each booking, not one for each guest. So the history is the conversation about that stay, not everything a person ever wrote. Each message shows who sent it. It can be the guest, someone at your agency, the owner, or Hostfully's own platform automation. It can also be an Airbnb user the channel does not name. A platform receipt is never mistaken for one of your people.
Money lives in the order, so TravelPal reads the order
The rent, cleaning fee, other fees, services and any adjustment sit on a separate order. The order is behind the lead. TravelPal reads that order for the stay it is working on. It keeps Hostfully's own line ids and reads a refund as a refund, not as a second sale. So a refunded extra is not counted twice in your upsell numbers.
What TravelPal writes back to Hostfully
Every message goes out through Hostfully, never around it. So your Hostfully inbox shows exactly what each guest was told.
Replies on whichever of the two rails can reach the guest
Hostfully sends a direct message when the lead came from Airbnb, Vrbo, or Booking.com. It sends email for everyone else. TravelPal picks between the two from the lead's own channel, not from a setting. A guest who booked on your own booking site gets email. An Airbnb guest stays inside Airbnb. Hostfully returns its own status on each send, and TravelPal treats accepted as accepted, not as delivered. See how the messaging works.
Paid time changes, written to the lead and then checked
TravelPal sells a late checkout or an early check-in at your prices. A paid one changes the arrival or departure time on the lead. The time is in the lead's own pre-arrival details, the same field your guest would fill in. TravelPal then reads the lead back. It calls the sale done only if the new time is really there. So your cleaning schedule never runs from a change that did not save.
Extra nights through Hostfully's own alteration
An added night on a direct booking goes through Hostfully's alteration call. It checks the property's own availability and rebuilds the order at your rates. No availability override is sent, and TravelPal reads the dates again afterward instead of trusting the response. Bookings owned by a channel are refused. A lead from a channel Hostfully has not published is refused too. A channel TravelPal cannot name is never treated as direct.
The stay link as a Hostfully variable
Create one custom data field in Hostfully and TravelPal keeps each stay's private guest link in it. Hostfully lets its own message templates use custom variables. So you can put the link into the scheduled messages you already send, in your own words.
Connected in four steps
Hostfully turns on API access for your account. TravelPal does the rest itself.
Ask Hostfully to open the API
API access is a paid add-on on the Hostfully plan. Hostfully turns on production access for an agency by email. One note to your account manager covers both. Use the same note to ask for personal-data access on the key. A key needs it before it can change a guest's stated arrival or departure. Everything after that you do yourself.
Copy the key and the agency UID
You make the key in Hostfully, under Agency Settings. Paste it into TravelPal together with your agency UID. Hostfully gives you the UID; you do not create it. The key does not expire and there is nothing to rotate. A mistyped paste costs one retry and no lockout.
Run on the sandbox first
Hostfully asks every integration to start on its sandbox. TravelPal points there until you switch the environment to production. You can read a full set of answers against test leads before any live guest sees one.
Switch to production and the properties import
TravelPal subscribes to Hostfully's booking and inbox events itself and imports your properties. From then on, every booked lead gets its own private guest link. If you disconnect, TravelPal removes those subscriptions from your agency and leaves none behind.
TravelPal shows the connection at every step: connected, last update, and any error in plain words. To see the other setup steps, read what onboarding involves.
What the Hostfully connection will not do
Know the limits of Hostfully before you turn anything on. Every property management system has its own limits. TravelPal works inside them, not around them.
SMS and WhatsApp can be read, not answered
These messages show in the Hostfully inbox and TravelPal reads them. But Hostfully's send has only two types: a channel direct message, and email. So a guest who texted is answered by the type Hostfully can deliver. A guest with no email address on a channel without direct messages is held for your team. TravelPal does not write to them somewhere they will not look.
The calendar is read, never written
TravelPal reads every night from Hostfully. It reads price, availability, and minimum stay. It also reads whether the night is closed to arrivals or departures. Hostfully has no separate calendar write. To hold a night, TravelPal would have to create a block record and later delete it. That delete is the same action that removes real bookings, so TravelPal does not use it. A sale that needs a night is checked against the calendar and then confirmed by the alteration itself.
No place in the thread for a note to your team
Both of Hostfully's message types are visible to the guest. The only notes on a lead are two free-text boxes, and a save replaces everything in them. That would erase what your staff last typed. TravelPal does not write in them. It also never sends a guest-visible message to reach your team. What a person needs to see goes to your own channel and by email, and the thread waits.
Time writes depend on how your key is cleared
A guest's stated arrival and departure are personal data in Hostfully. A key without that access accepts the change and quietly leaves the lead as it was. This is why TravelPal reads the lead back after every time change. If the time did not move, you are told the write failed. You are not shown a late checkout that exists only on our side.
When TravelPal's AI is not sure, it stops and asks your team instead of guessing. This rule is the same on every system: see the safety guardrails.
Hostfully integration FAQ
Does Hostfully have to switch anything on before I connect?
Yes, and it takes one email. API access is a paid add-on on the Hostfully plan. Hostfully turns on production access for an agency by hand when you ask. Your account manager can settle both in the same thread. In that note, also ask for personal-data access on the key. That is what lets TravelPal change a guest's arrival or departure time. After that you make the key yourself in Agency Settings and paste it into TravelPal.
Which Hostfully guests can TravelPal reply to?
Airbnb, Vrbo, and Booking.com guests get a direct message inside the channel thread. Every other guest is answered by email, including guests who booked on your own Hostfully booking site. SMS and WhatsApp messages can be read in the Hostfully inbox, but Hostfully's send does not carry them. So TravelPal answers those guests by direct message or email, whichever it can deliver. It does not turn a text into something else.
What happens to my inquiries, holds, and owner blocks?
Nothing. Hostfully stores all of them as leads next to real bookings. A lead can read as booked when nobody has booked. TravelPal sets up only a lead that is a booking with the status booked. Inquiries, holds, owner blocks, duplicate copies, and Hostfully's own sample record are skipped, not greeted.
Can TravelPal see the door codes in my Hostfully account?
No. Hostfully shares lock and door codes through its API. TravelPal never calls that part of it and never subscribes to its updates. The house manual is kept out of what the AI reads for the same reason. Managers type codes and wifi passwords into that free-text box. Hostfully's own wifi fields and guidebook links are left out on the same rule. So are the owner notes on a property. What a guest is told about getting in comes from what your team publishes for guests in TravelPal. It does not come from Hostfully's code list.
Does connecting Hostfully cost extra with TravelPal?
No. The flat $25 per unit per month covers the connection, the messaging, and the upsells. TravelPal takes no commission on what it sells for you. The API add-on on your Hostfully plan is Hostfully's own charge, and TravelPal does not add to it.
Not the system you use?
TravelPal connects to 33 property management systems. Below are the systems closest to Hostfully in how widely they are used.
Updated