Thanks, Bri. I was hopeful that's what it meant -- but sadly since posting my question, I've noticed that it's not playing out that way in practice for me yet... including a booking that came in just today. Is there anything I need to do on my end to ensure this new pause/delay on instant bookings can work properly?
This isn't the full on delayed response feature. That's still a work in progress. What is described above was a bug fix. If that's still not seeming to work as expected for you, please open a ticket with the Helpdesk and I'll take a look with them.
Hey @Bri -- Just FYI so you know, this continues to happen with every new booking (Rezzy responds to the guest's initial message not realizing there's a booking attached). So "Ensure Rezzy AI answers with booking context when guests book and message simultaneously" hasn't played out as expected a single time (at least not on my account).
Yup, I thought it was fixed before but it seems to keep happening again.
Thanks for nudging on this again, Alece. I was able to find the support ticket you have open where this is being discussed and I see that Chris was able to give you a detailed explanation of what's going on behind the scenes.
For visibility, here's what's going on at the moment...
After digging into this, we found it's a timing/sequencing issue on Airbnb's end. They're actually sending the booking message 5-15 seconds before the reservation itself goes through. So when Rezzy processes that message, it looks like there's no booking yet, because from our system's perspective, there genuinely isn't one; Airbnb just hasn't sent it to us yet.
We're currently working with Airbnb to figure out how to handle this out-of-order scenario without adding a blanket 30-second delay to all message processing. The goal is to keep response times fast while still correctly handling this edge case.
