AI guest messaging for Pxsol hotels
TravelPal connects to Pxsol with one API key you create in your own dashboard, then answers guests on the conversation channels Pxsol runs: WhatsApp, Facebook, Instagram, the website widget, and email. It reads each hotel, its check-in clocks, and its local time zone, and it learns about reservations by asking Pxsol on a schedule rather than waiting to be told. Every reply goes out as the Pxsol user you attach the key to, so your inbox always shows who said what.
One connection, running both ways. Every item on it is detailed below.
What TravelPal reads from Pxsol
Pxsol is run by independent hotels across Latin America, Argentina first among them, and by its own count it is in more than 1,800 properties.
A Pxsol hotel becomes one property
Name, address, coordinates, description, photos, amenities, and the hotel's own check-in and check-out clocks come across and become what the concierge answers from. Pxsol keeps room types as a separate resource, and a single reservation can hold up to five rooms of different types, so a forty-room hotel arrives as one property rather than forty.
Reservations arrive because TravelPal asks
Pxsol does not announce a booking to outside software: its live updates are a browser connection built for its own dashboard. So TravelPal sweeps Pxsol for reservations created or changed, hotel by hotel, and reaches back over Pxsol's widest documented window of 370 days on the first pass.
Seven statuses, read the way a front desk means them
Confirmed, checked in, and checked out all read as a live stay. Pending is carried as pending rather than rounded up to booked. A cancellation stops the concierge, and so does a no-show: a guest who is not coming should not keep getting messages. The seventh is a status Pxsol itself sends and calls unknown, and TravelPal will not greet anybody on one, so the stay is flagged for your team instead of guessed at.
Local time, taken from the hotel record
Pxsol carries a time zone on the hotel, written the long way as America/Argentina/Mendoza, and TravelPal uses it for quiet hours and for the cutoffs on what gets offered. A record holding a bare offset such as -03:00 is not accepted as a zone: an offset does not follow daylight saving, and a clock that drifts by an hour moves every cutoff with it.
What TravelPal writes back
Every message goes out through Pxsol, never around it, so your own inbox shows exactly what each guest was told.
Replies on the channel the guest is already using
Pxsol conversations run on WhatsApp, Facebook, Instagram, the website widget, and email. The send carries the words and nothing else: Pxsol resolves the platform, the company, the recipient, and the author from the conversation itself, so a WhatsApp guest stays on WhatsApp and a widget guest stays on the widget. TravelPal cannot move a guest from one of those channels to another, and does not try: guest messaging answers where the conversation already is.
Every send is signed by the user you chose
A Pxsol API key acts as the user it is attached to, and a send also assigns that conversation to them, taking it off whoever on your team was holding it. Make a dedicated Pxsol user for TravelPal before you make the key and both of those read correctly: the thread shows TravelPal answered and TravelPal has it, instead of a colleague's name on a message they did not write.
A message counts as sent only when Pxsol says so
Pxsol answers a send with sent or failed, and the common cause of failed is the WhatsApp 24-hour window closing on a guest who has not written in a day. TravelPal records only what Pxsol confirms, so a message nobody received never appears in your history as delivered.
One attempt, never a second
Pxsol gives a conversation message no way to mark two identical sends as one, so a retried reply would reach the guest twice. TravelPal sends once. Where Pxsol reports a failure the thread goes to your team rather than back into the queue.
Connected in four steps
The credentials are yours to create inside Pxsol. TravelPal does the rest itself.
Create a Pxsol user for TravelPal
The key you are about to make acts as a Pxsol user, and every action it takes is attributed to that person. Make a dedicated one first, so both your inbox and your audit trail stay honest about what the concierge did.
Make the key
Integrations, then Integraciones Generales (API Keys), then Create API Key. Grant it hotel-read, booking-read, and conversation-write. Abilities are ticked per key in Pxsol, and a key missing one is refused at the moment it is used rather than when you paste it, so it is worth checking the boxes twice. Pxsol shows the token once.
Paste it into TravelPal
One field, checked against your hotel list the moment you save. The key is static: TravelPal sends it exactly as issued on every call, so there is no token to mint and nothing to refresh on a schedule. A second field for the environment is optional: leave it empty for production, or set staging to point at Pxsol's staging gateway.
Hotels import, then the sweep begins
Every hotel your key reaches becomes a property, with its description, photos, amenities, and check-in clocks already filled in from Pxsol. From then on TravelPal sweeps each of them for reservations created or changed. See what it costs.
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 Pxsol connection will not do
Every property management system draws its own lines, and the ones Pxsol draws are worth knowing before you switch anything on. TravelPal works inside them rather than around them.
Pxsol's own channels reach a guest; a travel site's thread does not
Pxsol conversations run on WhatsApp, Facebook, Instagram, the website widget, and email, and there is no Airbnb or Booking.com thread inside Pxsol to answer in. Pxsol does not publish which channel a booking came from either. So a guest who booked through a travel site and writes inside it stays with your team, in that site's inbox: reaching them somewhere else is a different act, not a fallback, and TravelPal will not make that call for you.
TravelPal answers a conversation, it does not open one
Pxsol documents no way to look up a guest's conversation from their reservation, and a reservation read never returns a phone number. The conversation has to exist before TravelPal can write in it, which in practice means the guest writes to you first on one of your Pxsol channels. Scheduled first messages to a guest who has never written are not something this connection does.
A whole hotel is a single property
One Pxsol reservation can hold several rooms of different types, so the only thing that can name the place a stay belongs to is the hotel. It arrives with one check-in time, one check-out time, and one time zone, and whatever you write for that property is written once for the whole building. Room types are not separate places, so the concierge cannot tell a suite guest something different from a standard double guest.
Nothing a guest buys lands on the Pxsol booking
Pxsol's reservation verbs are cancel, change state, add a memo, attach a card, and send a message. None of them moves a stay's dates or its arrival and departure times, and availability is published per room type and rate plan rather than per property. So TravelPal does not quote a night from Pxsol and does not write a sold late checkout onto the reservation: the sale is recorded on our side and handed to your team to enter.
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.
Pxsol integration FAQ
Do I need Pxsol to turn anything on before TravelPal can connect?
No. You create the API key yourself, under Integrations and then Integraciones Generales (API Keys). Two things are worth doing in order. Create a dedicated Pxsol user for TravelPal first, because the key acts as that user and every action is attributed to them. Then grant the key hotel-read, booking-read, and conversation-write when you make it, because Pxsol shows the token only once.
Which guests can TravelPal answer on Pxsol?
Guests who reach you on a Pxsol conversation channel: WhatsApp, Facebook, Instagram, the website widget, or email. Pxsol carries no Airbnb or Booking.com thread, so a guest who booked on a travel site and writes inside it is answered by your team in that site's own inbox.
Will my team see what TravelPal told a guest?
Yes, with a name on it. Every reply goes out through Pxsol rather than around it, so the whole thread sits in your own Pxsol inbox, attributed to the user your key belongs to and assigned to them. The two places in Pxsol a guest cannot see, the reservation memo and the message that emails the hotel, are addressed by reservation number while a conversation is addressed by its own unrelated number, so TravelPal does not write a team note into the thread. Notes on a sale, and anything held for a person, reach your team in your own channel and by email.
How does TravelPal find out about a new reservation in Pxsol?
It asks. Pxsol announces nothing to outside software, so TravelPal sweeps each hotel your key reaches for reservations created or changed. The widest window Pxsol documents is 370 days, so a far-future booking made before that and never touched since is only picked up once something about it changes.
Not the system you run?
TravelPal connects to 33 property management systems. These are the ones nearest Pxsol in how widely they are used.
Updated