Latest Activity...
Good idea.
i forgot to block Easter this year and had a turnover. I gave my cleaner a bonus but would have rather given her the day off.
It would be very effective to be able to delay how fast rezzy answers. I believe this used to be a feature.
We’ve brought this in-house. Instead of paying Jervis $6 per thermostat, you can use Ecobee Smart Buildings which charges $2 per thermostat and build exactly what you need in Lovable, fully connected to your bookings via API.
Here is out current stop gap solution, built in Lovable. Makes sure we do not miss monthly or yearly expenses. (still manual)
My current workflow is to send renters a quick message through the channel platform after they sign the rental agreement with a heads-up to look out for an email from us. Then an email is sent that includes our curated list of restaurant recommendations, things to do, nearby stores, and more.
At times, guests will reach out with specific interests or questions, but if they sign the agreement right away, the recommendation email is triggered immediately. Ideally, I’d like the opportunity to review and customize that email before it goes out, which is why I originally requested this feature.
For now, I’ve set the email to send one day after the agreement is signed so I have time to personalize and send it manually if needed. That approach works, but it can feel a bit delayed. Guests are often inundated with messages right after booking, so it’s helpful to give them a little breathing room—while still getting this information to them promptly. That’s why having the option to send based on hours rather than days would be much more effective.
Thank you for implementing this feature. It will significantly enhance flexibility for hosts using Trustd.ai Guest Screening solution on OwnerRez. This is a trigger we’ve been looking forward to.
When a booking is received on OwnerRez, it typically takes us 2–4 minutes to generate the guest form and send it back. With this new capability, hosts can configure the trigger to automatically send the guest form to their guests for authorization. We recommend setting a delay of 10 minutes to ensure a smooth workflow. Thank you again for the implementation.
Regards,
Trustd.ai
https://trustd.ai
YES! I keep running into this as well. Random guest stays are being marked as negative sentiment when it doesn't apply, and then we're unable to correct it.
A button or option to train the Rezzy ai when a sentiment is legitimately negative or a miss reading. A options to remove a Negative sentiment is it is false, inaccurate or solved. I appreciate the quality centers ability to focus my attention on issue that matter. If I find a issue that is not accurate or relevant, a product of the ai programming, I would like to be able to train the ai or remove / solve the negative issue so it is clear from my board.
I appreciate you asking, Steve!
When the rental agreement is signed, our triggered message is sent with a copy of the signed agreement and full booking confirmation details. We also have a trigger to send a message offering additional nights if the adjacent nights are available. Because there's no way to stagger that one (10 minutes later, for instance), it sometimes beats the reservation confirmation message to their inbox. It ends up being an awkward communication flow.
I understand that the strategy on this could be shifted to only send that adjacent night offer X number of days prior to arrival (and we do that as a follow-up touch-point), but we have seen maximum results from sending it when we do — primarily because guests receive it before their flights are typically booked. So when the guest starts looking at flights with our offer in mind, they quite often end up taking us up on extending their stay. So I want to keep the message going out shortly after they've booked... Right now there just isn't a way to effectively stagger the trigger so it's slightly delayed from the initial reservation confirmation message.
Another use case is that we send Vrbo and Airbnb guests a channel message as well, letting them know we received their signed rental agreement and sent a copy of it to them via email. Again it has to share the same trigger timing of immediately sending when the rental agreement is signed, but often the channel message is received before the email has been. Once again this unnecessarily just adds some confusion and awkwardness to the communication flow.
We appreciate you taking the time to submit this feature request! If you know other users who would benefit from this, we'd encourage you to share it with them so they can add their support by way of an upvote at the top of the page.
Great suggestion—thanks for submitting! Know anyone else who'd benefit from this? Send them the link so they can add their vote and show there's interest in making this happen.
We've received your feature request—thank you! If you think others would love this too, spread the word and invite them to upvote. Community feedback really helps us prioritize what to build next.
Hi Alece,
That’s really helpful feedback, thank you!
Can you tell us a little more about how you’d use that in practice?
The main use case we had in mind for this feature was booking creation, where other processes often run in the background, such as generating a lock code or setting up a cleaning in a third-party system. In those cases, adding a short delay before sending a message makes a lot of sense. So those items have time to populate before sending the message
So, when it comes to something like signing the rental agreement, I’m curious about your workflow. What’s happening in that moment where having a 10-minute delay before sending a message would make things easier for you?
We did start a bit more focused with this feature, both from a usability and technical standpoint, just to make sure we got the core use cases right first. That said, we’re not opposed to expanding it, especially if there are strong, repeatable use cases like what you’re describing.
Not pushing back at all, just want to make sure we fully understand the need so our devs can build this in the most helpful way.
Thanks!
Thank you so much! This is a game changer for us.
This is great to see, Bri!
I'm really hoping this will also be extended to events such as the rental agreement being signed. Being able to schedule an email for, say, 10 minutes after rental agreement is signed would be SO HELPFUL!
We've adjusted the existing trigger condition (Code Generated Successfully) to wait for all door codes to generate. Now triggers wait until all door codes for a booking are successfully generated before firing.
We will likely expand on this in the future and add another condition for "Any Code Generated" as well, but that would come at a later date.
Today's release included the ability to create triggers that run a specific number of minutes before or after booking events, rather than just days. This allows more precise timing for pre-arrival communications and other time-sensitive messages, with options from 10 minutes up to 24 hours.
It would be very helpful if the reservation number or guest name could flow through with the "new" Airbnb Host Fee into QuickBooks. As it stands, this requires quite a bit of manual work on our end. Currently the only information it pulls in is the posting date which is two days after the reservation arrival. That is confusing to both our team and our owners, and it is insufficient for accounting.
Great suggestion—thanks for submitting! Know anyone else who'd benefit from this? Send them the link so they can add their vote and show there's interest in making this happen.
Hey Douglas!
Typically, the API will override any changes made directly on the channel the next time it syncs. Can you please submit a ticket to help@ownerrez.com and let us know which property this is for so we can take a look?
We've received your feature request—thank you! If you think others would love this too, spread the word and invite them to upvote. Community feedback really helps us prioritize what to build next.
We’ve noticed that when an block is created in OwnerRez for an Owner Stay, it syncs to Breezeway as a “hold” instead of a stay. Because of this, Breezeway does not automatically generate a cleaning task, and our team has to manually schedule it.
Is there a planned update or workaround on the OwnerRez side that would allow Blocks to sync as Owner Stays so cleaning tasks can be triggered automatically?
This would greatly help reduce manual workload and improve efficiency.
[This topic has been merged with another topic (Read-Only Scope for OAuth Applications/API Access). All unique votes have also been merged.]
[Another topic was closed as a duplicate of this topic (Read-Only or Scoped Permissions for OwnerRez API Tokens)]
We're using the OwnerRez API to pull booking data, guest details, and compliance information into our internal operations system, and it has been working very well for us.
However, we've noticed that API tokens currently have full read/write access, with no way to limit permissions. For our use case, we only need read access. We never modify bookings, payments, or property data through the API.
Having a full-access token introduces unnecessary risk. If a token were compromised, or if a script contained a bug, it could potentially modify or delete data without any platform-level safeguard.
Would it be possible to add one of the following?
Any of these options would help us follow the principle of least privilege and reduce our exposure. I imagine other property managers using the API for reporting, dashboards, and internal tools would benefit from this as well.
We are currently enforcing read-only access at the application layer. However, things could change in the future, or those protections could potentially be altered on our end, so we would appreciate the added safeguard of enforcing read-only access on the API side as well.
It's crazy to me that this is not possible!
I would also greatly benefit from Owner Rez recognizing automatically when payment have been remitted to owners directly already because of Airbnbs split payout/co-hosting model. A lot of my owners really appreciate being paid after every booking and I also prefer not to touch their money and just have my portion automatically paid out to me. Having to manually make this on each booking in OR is INCREDIBLY time consuming 😭. Please help! 🙏
Thanks, Alece!
Your secondary ask there sounds like a bug to me, so I've asked our dev team to take a look.
My company would be a perfect candidate for this integration. Currently, there are minimal hotels in our area and Marriott would benefit from having our home offerings that align with their brand.
