AI guest messaging for AvaiBook by idealista
TravelPal answers every AvaiBook guest in the one place AvaiBook keeps a conversation, which is the booking itself. It reads your accommodations and each bookable unit inside them, your bookings and the unit calendars, and it sells upgrades at your prices in that same thread. AvaiBook decides how a message is carried: their own Airbnb documentation describes a reply written in AvaiBook arriving in the guest's Airbnb thread.
One connection, running both ways. Every item on it is detailed below.
What TravelPal reads from AvaiBook by idealista
AvaiBook is what property management companies across Spain, Portugal and Italy run when they want the channel manager, the booking engine and the card payments from one vendor, idealista.
Units, not just accommodations
AvaiBook books a unit inside an accommodation, so a rooms accommodation with five bookable units becomes five properties in TravelPal, each named for its unit and carrying its own calendar and its own guests. Check-in and check-out times, the descriptions, each unit's capacity and minimum stay, and the photos come across with them. Two things are left out on purpose: AvaiBook's features list, which arrives with no published key to what its entries mean, and its booking conditions text, which is your cancellation contract and not your house rules. Reading a cancellation clause to a guest as a house rule is worse than saying nothing, so both belong in your knowledge base, where you control the wording.
Bookings, and only the ones that are already stays
AvaiBook has four booking states, and two of them are not a stay yet: one waiting for you to accept an on-request booking, one waiting on the guest's money. TravelPal gives a concierge to confirmed bookings and holds the rest until they turn into something. Every booking also says where it came from, so one taken on your own site, through your booking engine or keyed into the AvaiBook app is handled as direct, and a partner booking is not. AvaiBook names that partner in free text rather than from a fixed list, so the channel is recorded exactly as AvaiBook spells it.
One history per booking, three fields per message
AvaiBook keeps a single message history on the booking, and every message in it is three things: a date, which side sent it, and the text. There is no subject and no author name. TravelPal pages through the whole history in order before it writes anything, so a concierge joining a stay halfway through does not ask a guest what your team answered yesterday.
Unit calendars, published as occupied periods
AvaiBook publishes date ranges rather than individual nights, and it does not say which ranges are bookings and which are your own blocks. TravelPal therefore treats the last day of every period as taken. An extra night is offered only when it is certainly free, which costs the occasional checkout night and never sells a night somebody already has.
What TravelPal writes back
Every message goes out through AvaiBook by idealista, never around it, so your own inbox shows exactly what each guest was told.
One send surface, whatever the guest booked on
AvaiBook has a single way to reach a guest: post into the booking conversation. TravelPal uses that and invents nothing around it, no side email and no SMS of our own, so everything a guest was told sits in the AvaiBook record your team already reads. AvaiBook caps a message at 3,200 characters, so answers are written to fit rather than arriving cut in half.
Nights held on the unit's own calendar
Where a sale needs a night held, TravelPal writes the block on that unit's calendar inside AvaiBook, so your team sees the hold in the system they already work in. TravelPal never clears a block. AvaiBook's release takes a date range rather than the identity of one block, and a hold of ours reads the same as your maintenance block, so removing one is a decision for a person who knows which is which.
Sales arrive with the unit named
A guest who buys a late checkout or an extra night pays on their own private link, and the sale reaches your team naming the accommodation, the unit inside it and the new time. An AvaiBook booking carries no charges, extras or line items, so the money never appears on the booking record and TravelPal does not pretend otherwise. TravelPal takes no cut of it either: what upsells earn is yours.
Connected in four steps
AvaiBook by idealista switches API access on for your account, and TravelPal does the rest itself.
Ask AvaiBook to switch API access on
Access is granted account by account, so this starts with one email to your AvaiBook contact. They set you up in their pre-production environment first, email you the credentials, run their technical check, and then switch the key on against your live account. AvaiBook publishes a reply time of 24 to 72 hours on that first email.
Mint a full-access key, not the narrow one
The account holder creates the key on AvaiBook's API tools page. AvaiBook offers two scopes: full access, or rates and availability only. Choose full access. The narrow key connects, passes every check and imports your accommodations perfectly, and then refuses every guest message, which is the kind of thing nobody finds until a guest is waiting.
Paste the key into TravelPal
One field, plus an optional address if you want to point at AvaiBook's pre-production environment and watch a real thread before it touches live guests. AvaiBook's key is a standing one with no daily budget to burn, so a mistyped paste costs a retry and nothing else.
Units import, and your local time is set with you
Your accommodations and their units become properties, and every booking from then on gets its own private guest link. Because AvaiBook publishes no time zone on a property, we confirm the local zone with your team on that same call, before anything is scheduled.
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 AvaiBook by idealista connection will not do
Every property management system draws its own lines, and the ones AvaiBook by idealista draws are worth knowing before you switch anything on. TravelPal works inside them rather than around them.
A booking cannot be edited once it exists
An AvaiBook booking can be created, confirmed or rejected, and that is the whole list. So a paid late checkout or an added night is never written onto the AvaiBook booking. TravelPal sells it, takes the money, holds the night on the unit calendar and hands your team the change with the stay attached, and a person makes it real in AvaiBook.
AvaiBook publishes no time zone for a property
Their property record carries the address, the city, the region, the country and the coordinates, and stops there. Nothing should be scheduled off a guessed zone, so your portfolio's local time is set with your team when you connect. It decides quiet hours, when a good-morning message goes out, and when the late checkout offer closes.
Nothing is announced, so TravelPal goes and looks
AvaiBook has no event feed, so arriving bookings and arriving guest messages are found by checking on a schedule rather than by being told, and a guest is answered on the next check rather than in the same second. A change to an existing booking is found the same way: AvaiBook can list bookings by check-in date and by creation date, and offers no way to ask what changed since yesterday.
Your team's replies and ours look the same
AvaiBook marks a message as from the guest or from the property side, and attaches no author name. A reply one of your people types in AvaiBook therefore cannot be told apart from TravelPal's. Two consequences, both deliberate: a thread is handed to a person by your own rules and your quiet hours rather than by the AI noticing a colleague mid-thread, and because AvaiBook has no line in the conversation that the guest cannot see, held questions and sale notes reach your team in your own channel and by email instead.
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.
AvaiBook by idealista integration FAQ
Do I need AvaiBook's permission to connect TravelPal?
Yes, and it is one email. AvaiBook turns API access on account by account: they set you up in their pre-production environment, email you the credentials, run their technical check and then switch the key on against your live account. AvaiBook publishes a reply time of 24 to 72 hours on that first contact. Your account holder mints the key afterwards, on AvaiBook's own API tools page.
Which AvaiBook API key should I create?
The full-access one. AvaiBook lets you scope a key to rates and availability only, and that key behaves perfectly at connection time: it authenticates, and every accommodation and unit imports. It then refuses every guest message. Nothing in the import will tell you, so choose full access when you mint it.
My accommodation has several rooms. Does that work?
Yes. AvaiBook books a unit inside an accommodation, and TravelPal follows that, so each bookable unit becomes its own property with its own calendar, its own guest and its own thread. Five rooms under one roof are five stays, never one shared conversation.
Can TravelPal move a checkout time on an AvaiBook booking?
No. AvaiBook's bookings can be created, confirmed and rejected, and there is no update call, so nothing connected to AvaiBook rewrites one. TravelPal sells the late checkout, charges the guest, holds the night on the unit calendar where that is needed, and sends your team the stay and the new time. One of your people applies it in AvaiBook, which takes seconds and keeps a person on the schedule change.
Does connecting AvaiBook cost extra?
Not beyond the flat monthly price. AvaiBook books a unit rather than a building, and TravelPal runs one concierge per unit, so that is what a unit means on the bill.
Not the system you run?
TravelPal connects to 33 property management systems. These are the ones nearest AvaiBook by idealista in how widely they are used.
Updated