AI guest messaging for WuBook, Zak and WooDoo
TravelPal answers WuBook guests in the Airbnb thread, at any hour, in the language they write in. You connect it with two keys from the Wired dashboard.
One WuBook connection works in both directions. Each item is explained below.
What TravelPal reads from WuBook
WuBook is Italy-first and European. Its users are independent hotels and small apartment groups that sell rooms by type, not whole units. WuBook says it has more than 22,000 properties.
Rooms become properties
One call brings back every room on the property id you connect. WuBook allows up to 80 rooms on one property. Each room comes with its pictures, its occupancy, and the adults and children it sleeps. Virtual rooms come across too. WuBook lets you sell one physical room under a second setup, and a booking can land on either. Without virtual rooms, a real stay would have no property to attach to. A WuBook room holds capacity, pictures and rates and very little else. The address, the rules and the local detail come from your knowledge base.
Reservations arrive as a pointer, and TravelPal reads the booking
WuBook's push says which reservation changed and nothing else. It sends the same notice whether the booking is new, changed or deleted. So TravelPal fetches the reservation every time and works from the record, not the notice. It reads the room, the dates, the party size, the total, and the currency it was sold in.
Statuses are numbers, and a change is a new booking
WuBook grades a reservation from 1 to 6. Confirmed and accepted mean the guest is coming, and these bookings get a concierge. A booking that waits for approval waits until it is confirmed. Refused and the two cancellation grades are never greeted. WuBook has no modified grade. It treats an amendment as a cancellation plus a new reservation. So a moved stay arrives as a new number, not an edit to the old one. When a booking is canceled, WuBook also names who did it. It is the guest, somebody in your BackOffice, or the distribution channel. Your team gets that reason in WuBook's own words.
The language and the money the booking was made in
WuBook puts an ISO language code on the customer record of the booking. So the first reply to a German guest is in German. TravelPal reads it from the booking and does not guess from what the guest typed. The booking also carries a three letter currency, and TravelPal reads it instead of assuming one. Many WuBook users are in Europe. Treating a euro stay as dollars would misprice every paid extra by the exchange rate.
Availability counts and default rates stay in WuBook
TravelPal does not read availability from WuBook. WuBook sells rooms by type. So a night is a number of units left, not a yes-or-no answer. WuBook does not let TravelPal add a night to a booking. WuBook's documentation says its prices are the standard defaults, not the plan in force. TravelPal prices paid extras from your rules.
What TravelPal writes back to WuBook
Every message goes out through WuBook, never around it. So your WuBook inbox shows exactly what each guest was told.
Replies in the Airbnb thread
WuBook has one guest messaging route, and it is the Airbnb thread on the booking. TravelPal answers there, through WuBook and not around it. So the conversation your team opens in WooDoo is the whole conversation. Nothing goes out by email or SMS, because WuBook has no send for either.
Sales confirmed to the guest, and handed to your team
TravelPal offers an extra service, such as an extra clean, in the Airbnb thread. It uses your prices and confirms the sale there. Nothing can be written onto a WuBook booking that already exists. So the sale is emailed to your team with the stay and the amount attached. On the Flat plan the money is yours: TravelPal takes no share of what it sells. See how the upsells work.
Your rates and your availability are left alone
TravelPal never writes a price or an availability number into WuBook. The availability call sets an absolute count of units you can sell. It does not place a hold. So an undo would write back a number read earlier. A booking that landed in between would be opened again by that undo. TravelPal does not touch this part of WuBook.
Connected in four steps
You create the access details yourself, inside WuBook. TravelPal does the rest itself.
Make the two keys in the Wired dashboard
wubook.net/wauth/wauth/dash/wired/ gives you both. One is the Permanent Token, which does not expire. The other is the wr_ JSON API key. There are two because WuBook runs two APIs under one account. The token does not work for the key's half. You need no partner form and no approval. You can make both now.
Copy the property id
This is the number under Hotel ID in the WuBook Account panel. One WuBook account can hold several properties. Each one is its own connection here, with its own rooms and its own reservations.
Name your Airbnb channel, then paste the messaging callback
Open wubook.net/woodoo/channels/. Take the id of the Airbnb connection that has message handling switched on, and enter it. TravelPal turns on the reservation push for you. WuBook has no method for the messaging callback. So you paste our URL onto the API key in the Wired dashboard by hand, once.
Fill in what a WuBook room does not hold
WuBook stores a room's capacity, pictures and rates. It does not store the address, the check-in and check-out times, the house rules or the time zone. You enter these once during setup, and the concierge has them from the first message. Settle the time zone first. WuBook carries none, and every scheduled message is timed from it.
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 WuBook connection will not do
Know the limits of WuBook before you turn anything on. Every property management system has its own limits. TravelPal works inside them, not around them.
Airbnb is the only rail WuBook can message on
WuBook's guest messaging covers the Airbnb connection only. Booking.com, Expedia, Vrbo and your direct bookings still arrive as reservations, and TravelPal reads all of them. But WuBook has no route to those guests. So TravelPal stays quiet on them and does not quote a paid extra it cannot deliver. If most of your nights come from Booking.com, think about this before you connect.
Message history older than a week comes back blank
WuBook's own documentation says messages older than a week appear blank and should be saved in advance. So the backfill on the day you connect reaches about seven days, not a year of conversations. What sat in those threads before that cannot be recovered from WuBook by anyone. Everything from the day you connect is kept. So connect before your busy season, not in the middle of it.
Nothing edits a reservation that already exists
WuBook can create a booking, confirm one and cancel one. It has no call that changes the dates or the times on a live booking. This is the same choice as the missing modified grade. An amendment on WuBook is a cancellation plus a new reservation. A booking also carries an arrival hour and no departure hour at all. So TravelPal offers no paid late checkout on a booking that came from WuBook. It moves nothing on that record.
The thread labels a message guest or property, and nothing finer
WuBook labels every message it hands back as guest or property. Property is a side, not a sender. A reply typed by your team in WooDoo, WuBook's own automation, and TravelPal all carry that label. Two things follow. First, TravelPal treats nothing on the property side as a fact to learn. This keeps your team's own words out of your knowledge base. Second, the label cannot tell TravelPal that a colleague has stepped in. So the handover to a person runs on your rules and your quiet hours. The only write in WuBook's whole messaging surface is a send into that Airbnb thread. So there is nowhere to leave a note meant only for your team. Held questions and sale notes reach your team in your own chat and by email instead.
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.
WuBook integration FAQ
Is Zak the same thing as WuBook?
Yes, and so is WooDoo. Zak is the property management side. WooDoo is the channel manager. WuBook is the account they both sit on. One set of credentials from that account covers all three. So whichever name is on your login, this is the connection you want. If your account holds more than one property id, each id connects on its own.
Can TravelPal answer my Booking.com guests through WuBook?
No. Guest messaging on WuBook runs through the Airbnb connection. The API has no email or SMS send. So WuBook cannot reach a Booking.com, Expedia or direct guest. Those reservations still arrive, and your team still works them. TravelPal does not greet or quote a guest it has no way to answer.
Do I need WuBook's permission to connect TravelPal?
No. You make the Permanent Token and the JSON API key yourself at wubook.net/wauth/wauth/dash/wired/. You take the Airbnb channel id from wubook.net/woodoo/channels/. There is no partner application. One step is manual on WuBook's side, because WuBook has no method for it. You paste our messaging callback URL onto the API key in that same dashboard, once.
Will TravelPal change my reservations, rates or availability in WuBook?
No. WuBook has no call that edits the dates or times of an existing booking. Its availability call sets an absolute count of units you can sell and does not place a hold. So TravelPal writes to neither. What a guest buys is confirmed in the thread. It is handed to your team with the stay, the time and the amount.
Not the system you use?
TravelPal connects to 33 property management systems. Below are the systems closest to WuBook in how widely they are used.
Updated
WuBook is a trademark of its owner. TravelPal is not affiliated with or endorsed by WuBook.