The method of sending automatic messages differs depending on each OTA. Please check the main OTA sending methods and the current status of automatic messages.
【Airbnb】
Airbnb uses an API to sync messages. In addition to sending automatic messages, you can also exchange messages with guests from the AirHost PMS message list. Messages sent from AirHost PMS will be displayed on all Airbnb message pages.
As a restriction on Airbnb's side, it is prohibited to include URLs, email addresses, phone numbers, emojis, etc. in messages sent before a reservation is confirmed, and if such items are included, sending the message will result in an error. Please be especially careful as the "automatic response message" is sent before the reservation is confirmed. Please note that the term "Booking.com" is also subject to this restriction.
As a prerequisite for centrally managing Airbnb messages using AirHost PMS, you must connect your listing to the PMS in order to receive Airbnb messages in real time. Therefore, if you receive reservations via Neppan, Temairazu, Rakutsu, CSV, etc., messages will not be sent.
*The maximum size of images that can be sent is 3.5MB. If you try to send an image larger than this size, it cannot be sent and an error will occur.
Note 1 (Dec 6, 2024):
Airbnb has a system in place to check whether message content includes inappropriate phrases, such as phone numbers or website links. Since this is a new system, there may occasionally be false positives that prevent the message from being sent.
Currently, there appears to be no definitive way to avoid these false detections. However, if the error occurs repeatedly, rephrasing the message content may help to avoid the issue.
Note 2 (Jun 5, 2025):
This note covers cases where messages in different languages, such as Japanese and English, appear to have been sent for the same reservation.
If the language of a sent message does not match the guest's preferred language, the message may not have been sent by our system but synced from Airbnb.
In addition, if the reservation was already "Accepted" on Airbnb when it was synced to our system, our automatic reply message will not be sent.
【Booking.com】
From March 15, 2022, we have migrated to the Message API provided by Booking.com. As a result, the message specifications are similar to those of Airbnb, and messages will be displayed on all Booking.com message pages.
If you receive reservations via Neppan, Temairazu, Rakutsu, CSV, etc., messages will be sent to the virtual email address issued by Booking.com for each reservation.
[ May/2024 ]
To send a URL in messages on Booking.com, the domain of the URL must first be whitelisted on Booking.com. The relevant domain (for example, www.onestayapp.com for the AirHost pre-check-in URL) needs to be whitelisted at the property level. You can set this in the Booking.com extranet.
*It appears you can apply the setting to all your properties using the "Apply to all properties" option.
Booking.com Setup Help:
If you need help with the setup, please contact Booking.com's support team.
Below is the settings screen.
[ Jul/2024 ]
Starting from June 2024, messages exchanged with guests through Booking.com will not be sent if they contain shortened URLs. For more details, please refer to the Booking.com Help Center or contact their Support Center.
[ Jan/2026 ]
Some content shown in the AirHost message inbox may not appear on the Booking.com message screen. This content comes from the remarks field (Booking remark) that the guest filled in when booking on Booking.com. Currently, when we receive booking remarks from Booking.com, AirHost displays them as a message so that important information is not missed. At present, the message screen does not distinguish between "booking remarks" and "regular guest messages".
Booking remarks are also shown in Reservation details > "Comment".
[ March/2026 ]
If an attached image contains a QR code, sending is rejected, the message shows a "RETRY" status in AirHost, and a sending error occurs.
Please remove the QR code from the image.
【Expedia】
Messaging with Expedia guests has switched to the Message API, as with Airbnb and Booking.com. This allows more stable sending and receiving of messages than before.
Note 1 (Nov 29, 2024):
Currently, Expedia reviews outgoing messages to prevent scam messages from reaching guests. As a result, messages to guests may be delayed by 12 hours or more.
Note 2:
For reservations made through affiliate sites such as Hotels.com (i.e., not booked directly via Expedia), the Message API is not supported. If the reservation information from Expedia includes an email address, messages will be sent and received by email instead of through the Message API.
Note 3 (May 22, 2026):
For reservations via the Expedia Affiliate Network (EAN), the guest's email address and phone number may not be provided due to Expedia's specifications. In addition, EAN reservations do not support sending messages through the Message API, so AirHost's automatic message feature may not be available. In that case, please contact the guest directly from the Expedia platform.
AirHost cannot generate its own proxy email address (masked address) like the ones Expedia provides. These must be provided by Expedia.
【Agoda】
Like Expedia, Agoda links a virtual email address issued by Agoda for each reservation to the reservation information. Messages are sent to this Agoda virtual email address, and Agoda forwards them to the guest.
However, starting in June 2023, Agoda's security standards changed and all URLs in messages are now masked. As a result, the pre-check-in URL sent in AirHost automatic messages could not be delivered to guests.
Replies from guests are not shown in the AirHost inbox. By setting your AirHost account's virtual email address (see company settings) as the notification address for Agoda messages, you can receive a notification in the AirHost inbox when a new message is posted on Agoda. As these are notification emails, you may not be able to see the full message text, but you can use the notification as a cue to check the Agoda message board.
[ 9/25/2023 ]
We were contacted by the Agoda API team, and the AirHost pre-check-in URL has been excluded from masking.
As shown in the example below, the pre-check-in URL is now displayed normally, while other URLs are still masked.
[ Apr/2024 ]
The AirHost pre-check-in URL was excluded from masking in September 2023, but we have received reports that masking is being applied again for some listings.
[ Jul/2024 ]
The AirHost domain is registered in the whitelist.
Masking may occur when the domain is treated as not being in the whitelist. For example, if the URL is written directly after ":" without a space, as below, it may be regarded as a different domain and masked.
[Check in URL]: https://www.onestayapp.com <- There is a space between : and h
[Check in URL]:https://www.onestayapp.com <- There is no space between : and h
Agoda is still investigating this issue, but we recommend adding a space before and after the URL.
[ Feb/2025 ]
Previously, it was possible to obtain the guest's personal email address instead of a virtual email address, but for safety and security reasons, Agoda can no longer provide the guest's email address as reservation information. If the guest does not wish to disclose their email address, it is automatically skipped by the system.
【Rakuten Travel】
Messages for Rakuten Travel are sent automatically through the message function of the Rakuten Travel management screen. Therefore, due to Rakuten Travel's restrictions, there is currently a limit to the number of characters that can be sent in an automatic message.
If sending fails, it is technically difficult to retry, so for properties using Rakuten Travel, please keep messages to 750 characters or less.
If document URLs are long, please use shortened URLs or similar measures.
Additionally, Rakuten Travel does not allow direct contact with guests of package reservations (reservation numbers starting with "WS"), including by email. For this reason, neither automatic nor manual messages reach guests of package reservations.
You can check whether a reservation is a package reservation in the Rakuten Travel management screen under 部屋設定・予約管理 (Room settings / Reservation management) > 予約者の確認・キャンセル・変更処理 (Check, cancel or modify reservations) > 「楽天トラベル」会員データの表示 (Rakuten Travel member data), in the 会員への連絡 (Contact with member) field.
If you use another site controller such as Neppan, Temairazu or Rakutsu, you can send and receive messages by registering your management screen login information. Please see the help page below.
[Message Channel] Enabling Messaging for Rakuten when Linked with Other Site Controllers (PMS)
[ Apr/2025 ]
Currently, auto messages are not sent for Rakuten Inbound reservations.
[ Nov/2026 ]
Before November 10, 2026, messages to package reservations were shown as "sent" in AirHost, but under Rakuten Travel's rules they were not actually received by guests. To avoid confusion, since November 10, 2026, AirHost no longer sends messages to package reservations and instead shows the error "not support sending messages to rakuten package booking (楽天パッケージ予約のため連絡不可)" on the message screen.
【Jalan】
The email address entered by the guest is linked to the reservation information, so messages are sent directly to the email address in the guest's reservation information.
【Ikyu / Yahoo】
The email address entered by the guest is linked to the reservation information, so messages are sent directly to the email address in the guest's reservation information.
If you use another site controller such as Neppan, Temairazu or Rakutsu, you can send and receive messages by registering your management screen login information. Please see the help page below.
[Message Channel] Enabling Messaging for Rakuten when Linked with Other Site Controllers (PMS)
【Rakuten Oyado (formerly Rakuten Vacation Stay)】
Messages are sent using a virtual address provided by Oyado (@guest.vacation-stay.jp), and Oyado forwards them to the guest. As a result, we cannot obtain the guest's actual email address. Replies from guests also go through Oyado and are sent by email to the property email address registered with Oyado.
Due to the specifications of Oyado's API, replies from guests to automatic messages are not reflected in AirHost.
【Traveloka】
The email address entered by the guest is linked to the reservation information, so messages are sent directly to the email address in the guest's reservation information.
【Tripla】
The email address entered by the guest when booking is linked to the reservation information, so messages are sent directly to the email address in the guest's reservation information.
【Rurubu】
For reservations from Rurubu, no email address is provided in the reservation details and there is no Message API, so automatic messages cannot be sent.
【Trip.com】
Please refer to the Message API integration steps.
[ Apr/2025 ]
Messages cannot be sent or received if they contain the term "信用卡" (credit card).
The guest's preferred language is determined by analyzing the Special Request from the Trip.com API and is reflected in the language setting for automatic messages.
【CHILLNN】
The email address entered by the guest when booking is linked to the reservation information, so messages are sent directly to the email address in the guest's reservation information.
【Reservations imported via CSV】
If you import reservations via CSV with the reservation import feature, messages are not sent unless you import the email address. If you map the email address and it is valid, messages can be sent.
【Guest replies to automatic messages】
Automatic messages from AirHost are sent from a virtual email address issued by AirHost for each reservation (via the Message API for Airbnb and Booking.com). When a guest replies to that email, the reply appears under each reservation in AirHost Messages.
【Unified management of inquiries】
In ONE, you can set up a virtual email address in company settings. If you set this virtual email address as the contact address on each OTA, emails from guests sent to it can be received in Messages. (They are not linked to a reservation.)






