Common errors

"Property not found" or "Reservation not found"

• Cause — The webhook or sync referred to a property or booking that doesn’t exist (or isn’t linked) in PingTeo.
• Fix — Ensure the property is added in PingTeo and that the Beds24 property/booking IDs match. Sync or reconnect Beds24 if you recently added the listing. If the reservation is new, wait for sync or check that booking webhooks are enabled.

"Token expired" or Beds24 API errors

• Cause — PingTeo’s stored Beds24 tokens expired or were revoked.
• Fix — In Settings → Beds24, reconnect using a new invite code from Beds24. That refreshes the tokens.

"Plan limit" or "Property limit exceeded"

• Cause — Your plan allows a maximum number of properties; you’re at or over that limit.
• Fix — Remove a property you no longer need, or upgrade your plan in Settings → Billing to add more properties.

Automation not sending

• Cause — Trigger disabled, wrong schedule, template/rules error, or reservation data missing for placeholders.
• Fix — In Properties → property → Automation, ensure the trigger is enabled, days/time are set correctly, and the template (and rules) validate. Use a preview with a real reservation if available. Check that the reservation has the data your placeholders need (e.g. guest name, dates).

Slow or delayed replies

• Cause — Webhook not set (so PingTeo only gets messages on scheduled sync), or AI/service delay.
• Fix — Set the webhook so messages are pushed in real time. If the webhook is set and replies are still slow, check status pages or contact support.

Can’t log in or reset password

• Cause — Wrong credentials, or password reset email not received / expired link.
• Fix — Use Forgot password and check spam. Reset links often expire after a short time; request a new one if needed. If you use another provider (e.g. Google), log in with that method.

For errors not listed here, note the exact message, page or action, and browser/device and contact support.

Next: FAQ — Pricing, trial, and common questions.