Listing and message disclosure

1. Listing disclosure. Put the actual rules, fee consequences, and any rental-agreement terms in the listing where the guest can review them before booking.
2. Message-thread disclosure. Send a short Airbnb message that says the PreArrive packet mirrors the listing terms and does not require an app or account.
3. Signed acknowledgment. Send the PreArrive link after booking so the guest taps each rule and fee and draws a signature before check-in.

The certificate proves what the guest acknowledged. It does not make undisclosed terms enforceable by itself. Enforcement, collection, and reimbursement are decided by the platform, insurer, court, facts, and supporting documentation.

In the packet editor, open Disclosure. PreArrive generates a listing block and a message-thread template from the same live packet data the guest will sign.

• Paste the listing block into Airbnb Additional Rules or the listing description.
• Paste the message template into the Airbnb message thread when you send the signing link.
• Review warnings for mandatory fees, deposits, taxes, pet-count changes, guest-count changes, and off-platform collection language.
• Complete the host checklist so the sending workflow records that you checked the disclosure path.

Airbnb’s host guidance says hosts may ask guests to sign a contract, but the actual contract terms must be disclosed in the listing and included in the message thread. Airbnb also says it cannot help enforce special policies in that contract.

That is why PreArrive’s packet copy should match the listing copy. If a clause appears only after booking, the guest may be able to decline it and ask for cancellation. Treat the PreArrive packet as the acknowledgment layer, not as a place to add surprise terms.

Verify current platform policy before publishing new legal, fee, or claim copy:

• Airbnb guest contracts for hosts
• If a host asks you to sign a contract
• Off-Platform and Fee Transparency Policy