AI guest messaging for Channex.io
TravelPal connects to Channex with a key made for your own account. It answers guests in the chat of Booking.com, Airbnb, and Expedia.
One Channex.io connection works in both directions. Each item is explained below.
What TravelPal reads from Channex.io
Small property management companies and independent hotels use Channex. They send their own rates and open dates to the booking sites. No property management system sits above Channex. If a property management system holds your stays, connect that system instead.
Properties, one per premises
Channex asks for one property for each premises. A short-term rental apartment is one property with one unit. Anything shaped like a hotel has several bookings that share one entry. The title, address, coordinates, description, facilities, and photos come across. The concierge answers from them, together with your own knowledge base. Check-in and check-out times come from the property's default hotel policy. If a property has several policies and none is the default, TravelPal leaves the times unset. It does not price an early check-in on a guess.
Bookings, in the three states Channex publishes
A booking arrives as a revision that is new, modified, or canceled. TravelPal reads the current state of the booking, not just the last revision that arrived. Each booking carries the channel's own reservation code, the one on the guest's Booking.com or Airbnb confirmation. It also carries the arrival hour, where the channel sent one. It carries the language the customer booked in, so the first reply is in that language. A cancellation is only a status. It has no hour and no name, so TravelPal stops writing to that guest and invents neither. Channex keeps no guest record of its own. A second stay by the same person arrives as a stranger.
Whole threads, and Airbnb inquiries with no booking behind them
Channex returns a conversation with the newest message first. TravelPal turns it around and reads it in the order it happened. So it picks up a stay in the middle of a thread, not from the newest line. Channex also shows an Airbnb inquiry as a message thread with no booking. That is a guest asking about a stay that does not exist yet. TravelPal reads it as a question with no reservation behind it. It does not file it as a booking that never arrives.
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. A breakfast or a cleaning service on the booking is never counted as an extra night sold. It keeps the currency of the booking and does not assume one.
What TravelPal writes back to Channex.io
Every message goes out through Channex.io, never around it. So your Channex.io inbox shows exactly what each guest was told.
Replies in the channel's own chat
Channex carries one route, the channel's guest chat, and TravelPal answers in it. A Booking.com guest reads the reply inside Booking.com. An Airbnb guest reads it inside Airbnb. There is no email and no text message route here. So an upsell goes where the guest already reads, in that same thread, at your prices.
First contact without waiting for the guest
A booking nobody has written to yet has no thread in Channex. TravelPal opens the conversation on the booking itself. The message before arrival and the arrival details go out on your schedule. The guest does not need to write first. The guest's reply lands back in that same place.
One account-wide subscription, not one per property
TravelPal subscribes to new bookings, revisions, and guest messages for the whole Channex account, not property by property. A unit you add next month is covered, and nobody has to set it up. Disconnecting removes the subscription, so nothing still points at us after you stop.
Connected in four steps
Channex.io turns on API access for your account. 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. Say you want TravelPal to read your bookings and answer 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 run there in the meantime.
Create the key
In Channex, go to Organization, then API Keys, then Create new API Key. The key does not expire. It is shown once, so copy it while it is on the screen.
Paste the key, pick the environment, invent a secret
There are three fields. The environment is staging or production. If you leave it unset, it 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 at once and costs only a retry.
Switch on Messages, then let the import run
Guest chat is a Channex app that your account installs on a property. Turn it on for the properties you want answered. Your properties import in full. The first import pulls the stays that arrive in your date window. Nothing else inside Channex changes. The same flat price per unit covers it: what it costs.
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 Channex.io connection will not do
Know the limits of Channex.io before you turn anything on. Every property management system has its own limits. TravelPal works inside them, not 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 in the same Channex account has no thread to write into. Expedia Affiliate Network bookings are also outside the messages API. TravelPal does not invent another route for those guests. So it declines to offer, price, or schedule anything it cannot 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. Channex turns the chat away for a property that does not have it. TravelPal treats that as an answer, not an outage. The property still imports and its bookings still arrive. Those guests are not written to until the app is on.
A booking cannot be changed from here
Channex passes bookings through from the channel and does not change them. So a paid late checkout or an added night is not written onto the reservation. A property management system would write it. TravelPal agrees the change with the guest in the thread. It hands it to your team with the stay attached. The booking itself changes 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. There is no team-only note beside it. So TravelPal tells your team in your own channel and by email instead. This is how it passes on a held question or a note about what a guest bought. Channex announces a guest's message, and only a guest's message. When one of your people answers in the Channex inbox, nothing reaches TravelPal. So TravelPal passes a guest to a person by your rules and your quiet hours. It does not work by overhearing your team.
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.
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. If you run a property management system, connect that one instead. It holds the truth about the stay, and a time or a date change must be written there. This connection is for teams that send their own rooms straight to the channels through Channex. Those teams have nothing above Channex.
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. A Vrbo guest or a direct booking in the same account has no thread here. TravelPal will not offer or schedule anything for a guest it cannot reach. Expedia Affiliate Network bookings are also outside the messages API.
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. The connection starts with a note to your Channex contact. 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. You can watch the connection work there before either is settled.
Can TravelPal change a booking in Channex?
No. A booking in Channex belongs to the channel that sent it. Changes run through that channel's own flow. TravelPal does not offer a late checkout or an extra night on a booking that came from Channex. It does not write a new date or time onto the reservation. It never tells a guest a change is done when it is not.
Not the system you use?
TravelPal connects to 33 property management systems. Below are the systems closest to Channex.io in how widely they are used.
Updated
Channex.io is a trademark of its owner. TravelPal is not affiliated with or endorsed by Channex.io.