Forwarding confirmation emails

1. Open Settings in the side rail.
2. Scroll to Forward reservations by email.
3. Click Generate forward-email address. Copy it.
4. Set up forwarding from each platform (see below).

The address is one-per-account, not per-property. Forwards work across every team you’re in.

If you disable the address, update your platform rules. Disabling it doesn’t touch the forwarding rules you set up on Airbnb, VRBO, or Booking.com. They keep sending to an address that no longer routes anywhere, so that mail is silently ignored. Re-enabling gives you a new address, so you’ll need to point those rules at the new one.

• Airbnb. Airbnb doesn’t forward natively. Use a Gmail (or your provider’s) filter: from [email protected] → forward to your PreArrive address. Most email providers support this in a few clicks.
• VRBO. Account → Notifications → Email forwarding. Add the address.
• Booking.com. Extranet → Inbox → Settings → Forwarding. Add the address.

Per email, we extract the reservation code, guest name, and guest email. We do not store the email body. The extracted fields and the From / Subject metadata live on the inbound_emails table for debugging; the raw body is never persisted.

If SPF or DKIM fails on the email (i.e., someone’s spoofing Airbnb), we refuse to process. The spoofing check is the reason we ask you to forward to a unique per-account address. We only enrich on a clean pass on both, so we also skip anything that arrives without those authentication results at all.

One practical effect: a normal Gmail or Outlook filter that forwards the message re-signs it, so it passes and parses fine. But if you route the mail through some other server or relay first, that hop can break SPF/DKIM, and then we won’t auto-fill the guest. The sign of this is a synced reservation whose guest name and email stay as placeholders even though you forwarded the confirmation. If that happens, forward straight from your own mailbox rather than through an intermediate relay.

We match by reservation code. If you also have calendar sync running, the synced reservation’s placeholder guest gets replaced with the real name + email automatically.

If no synced reservation matches (you haven’t connected the calendar for that property yet), the email is logged but no reservation is created. Connect the calendar first, or use direct entry.