← Help center

Troubleshooting

The shortlist of issues hosts hit most. If yours isn’t here, message us.

The guest says they didn’t get the email

  1. Open the reservation. Check that the email address is right.
  2. Click Resend on the reservation — same link, no new token.
  3. Ask the guest to check spam, and to look for a sender that includes the property name.
  4. If it still doesn’t arrive, send them the signing link directly (copy it from the reservation page).

The guest says the link expired

Signing links live until checkout + 7 days. If the link is genuinely expired, click Resend — the system mints a fresh token automatically when the old one is gone.

If the link is showing "already signed," that’s actually the post-sign view — the guest can still use it to see the door code, WiFi, and rules. Tell them to scroll down.

I sent to the wrong email

Edit the reservation’s guest email field and click Resend. The old token still works for the original recipient (single-use, but visible until checkout); the new send mints a fresh token for the correct email.

The fee didn’t get charged

PreArrive doesn’t charge guests directly. The fee gets charged when you submit a Resolution Center or AirCover request and Airbnb/VRBO approves it — the certificate is the evidence you attach.

If the request was denied: most often the listing didn’t disclose the specific fee, the wording was too vague, or the violation wasn’t documented. See AirCover claims.

Calendar sync says "error"

Open the property’s Calendar sync page and look at the last-error field.

  • HTTP 4xx usually means the iCal URL is wrong or expired. Re-copy it from the platform.
  • HTTP 5xx means the platform’s feed is temporarily down — retry in an hour.
  • No new bookings after a sync isn’t an error; the platform may simply not have anything new for that period.

Click Sync now to retry on demand.

Billing change isn’t reflected

Stripe’s webhook updates your effective caps within seconds. If a change isn’t reflected:

  • Refresh the dashboard once — the client cache is the most common culprit.
  • Wait 30 seconds — Stripe occasionally delivers a webhook with a slight lag.
  • If still off after a minute, contact support with the Stripe receipt and we’ll re-sync the row.

Still stuck? Message us — we read every message and reply within a few hours on weekdays.