AI guest messaging for Channex.io
TravelPal connects to Channex with a key issued for your own account and answers guests in the one chat Channex carries: the channel's own thread on Booking.com, Airbnb, and Expedia. Connect it only if Channex is your channel manager and your bookings live in it. If a property management system sits above Channex and holds your stays, connect that one instead, because that is where a checkout time or an extra night has to be written.
One connection, running both ways. Every item on it is detailed below.
What TravelPal reads from Channex.io
Channex is run by small property management companies and independent hotels that push their own rates and availability to the booking sites, with no property management system sitting above it.
Properties, one per premises
Channex asks for one property per premises, so a short-term rental apartment maps one property to one unit, and anything hotel shaped has several bookings sharing a single entry. Title, address, coordinates, description, facilities, and the property photos come across and become what the concierge answers from, alongside your own knowledge base. Check-in and check-out times are read from the property's default hotel policy, and where a property carries several policies and names no default, TravelPal leaves the times unset rather than pricing an early check-in against a guess.
Bookings, in the three states Channex publishes
A booking arrives as a revision that is new, modified, or canceled, and TravelPal reads the booking's current state rather than whichever revision happened to land. Each one carries the channel's own reservation code, the one printed on the guest's Booking.com or Airbnb confirmation, plus the arrival hour where the channel sent one and the language the customer booked in, so the first reply is already in it. A cancellation is that status and nothing more: no hour on it and nobody named, so TravelPal stops talking to that guest and invents neither. Channex keeps no guest record of its own, so a second stay by the same person arrives as a stranger until TravelPal matches it from what it already knows.
Whole threads, and Airbnb inquiries with no booking behind them
Channex hands a conversation back newest message first, so TravelPal turns it around and reads it in the order it happened, picking a stay up mid-thread rather than from the newest line. Channex also represents an Airbnb inquiry as a message thread with no booking attached, which is a guest asking about a stay that does not exist yet. TravelPal reads those as exactly that, a question with no reservation behind it, rather than filing them as bookings that never arrive.
The rooms' own money, not the booking total
A Channex booking total adds services and non-inclusive taxes on top of the rooms. TravelPal reads what the rooms themselves cost, so a breakfast or a cleaning service on the booking is never counted as an upsold night, and it keeps the currency the booking was taken in rather than assuming one.
What TravelPal writes back
Every message goes out through Channex.io, never around it, so your own inbox shows exactly what each guest was told.
Replies in the channel's own chat
Channex carries one rail, the channel's guest chat, and TravelPal answers in it, so a Booking.com guest reads the reply inside Booking.com and an Airbnb guest inside Airbnb. There is no email and no text message route here at all, so an upsell goes where the guest is already reading, in that same thread and at your prices.
First contact without waiting for the guest
A booking nobody has written in yet has no thread in Channex. TravelPal opens the conversation against the booking itself, so the pre-arrival message and the arrival details go out on your schedule rather than waiting for the guest to speak first, and the guest's reply lands back in that same place.
One account-wide subscription, not one per property
TravelPal subscribes itself to new bookings, revisions, and guest messages across the whole Channex account rather than property by property, so a unit you add next month is covered with nobody going back in to wire it up. Disconnecting removes that subscription again, so nothing is left pointing at us after you stop.
Connected in four steps
Channex.io switches API access on for your account, and TravelPal does the rest itself.
Ask Channex to open production access
Production API keys are not self-serve: Channex issues them for an account, so a live connection starts with one note to your Channex contact saying you want TravelPal reading your bookings and answering guest chat. We take part in that conversation with you. Staging keys are open to any user on staging.channex.io, so the connection can be running there in the meantime.
Create the key
Channex, then Organization, then API Keys, then Create new API Key. The key does not expire and it is shown once, so copy it while it is on screen.
Paste the key, pick the environment, invent a secret
Three fields. The environment is staging or production, and an unset one stays on staging, so a half-finished setup cannot message a real guest. The secret is any long random string you make up: Channex sends its updates without a signature of its own, so TravelPal registers your string with them and turns away any delivery that does not carry it. A wrong key is rejected on the spot and costs nothing but a retry.
Switch on Messages, then let the import run
Guest chat is a Channex app your account installs on a property, so turn it on for the properties you want answered. Your properties import in full, the first import pulls the stays arriving in your date window, and nothing else inside Channex changes. It is covered by the same flat price per unit: 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 Channex.io connection will not do
Every property management system draws its own lines, and the ones Channex.io draws are worth knowing before you switch anything on. TravelPal works inside them rather than around them.
Three channels have chat, and the rest have none
Channex carries guest messages for Booking.com, Airbnb, and Expedia only. A Vrbo booking or a direct booking sitting in the same Channex account has no thread to write into, and Expedia Affiliate Network bookings sit outside the messages API as well. TravelPal does not improvise another route for those guests, so it declines to offer, price, or schedule anything it cannot actually deliver to them.
The chat is a separate paid Channex app, installed per property
Messages is an app your account buys and installs on a property, and Channex turns the chat away for a property that does not have it. TravelPal treats that as an answer rather than an outage: the property still imports, its bookings still arrive, and those guests are simply not spoken to until the app is on.
A booking cannot be changed from here
Channex passes bookings through from the channel and does not alter them, so a paid late checkout or an added night is not written onto the reservation the way it would be inside a property management system. TravelPal agrees the change with the guest in the thread and hands it to your team with the stay attached, and the booking itself moves through the channel's own alteration flow.
The thread belongs to the channel, so nothing in it is team-only
Every message Channex carries is the guest's own channel conversation, and there is no team-only note beside it, so a question TravelPal holds for a person and a note about what a guest bought reach your team in your own channel and by email instead. Channex announces a guest's message and only a guest's message, so when one of your people answers in the Channex inbox nothing reaches TravelPal, and handoff to a person runs on your rules and your quiet hours rather than on overhearing your team.
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.
Channex.io integration FAQ
Is Channex the right connection for my bookings?
Only if Channex is your own channel manager and your bookings live in it. Channex sits underneath a property management system and mirrors what the channels send, so if you run a property management system, connect that one instead: it holds the truth about the stay, and it is where a time or a date change has to be written. Teams that push their own rooms straight to the channels through Channex, with nothing above it, are exactly who this connection is for.
Which guests can TravelPal reach through Channex?
Booking.com, Airbnb, and Expedia guests, in the channel's own chat thread. Those are the three channels Channex carries messages for, so a Vrbo guest or a direct booking in the same account has no thread here and TravelPal will not offer or schedule anything for a guest it cannot reach. Expedia Affiliate Network bookings are outside the messages API as well.
Does Channex have to switch anything on for me?
Yes, two things. Production API keys are not self-serve: Channex issues them for your account, so the connection starts with a note to your Channex contact, and we take part in that conversation with you. Guest chat is the Messages app, which your account installs on each property you want answered. Staging keys are open to any user on staging.channex.io, so you can watch the connection work before either is settled.
Can TravelPal change a booking in Channex?
No. A booking in Channex belongs to the channel that sent it, and alterations run through that channel's own flow. TravelPal agrees a late checkout or an extra night with the guest in the thread, at your prices, and hands the detail to your team with the stay attached. It does not write a new date or time onto the reservation, and it never tells a guest a change is done when it is not.
Not the system you run?
TravelPal connects to 33 property management systems. These are the ones nearest Channex.io in how widely they are used.
Updated