You set up your OwnerRez triggers: a thank-you at booking, arrival details before check-in, a note on departure day. The first week it felt solved. Then a guest writes at 9 p.m. asking whether they can check in at noon, another asks whether the dog is allowed, and the arrival message you sent yesterday did not mention either. The templates are working. They were never going to cover this.
Why it keeps happening
An automated message answers a question you can predict, at a moment you can predict. Both limits are the point of a template, not a flaw in OwnerRez. As a portfolio grows, the questions that matter most are the ones that depend on the booking: which unit, which dates, which channel, what the house rules say for that unit. Field codes can put booking-specific details into a scheduled message; requests that need a decision still need a separate reply.
What OwnerRez gives you
These points come from OwnerRez's own support center, read on 2 October 2026.
- Templates and triggers. The messaging overview describes triggers that act on booking events, covering pre-booking, pre-arrival, mid-stay, post-departure and cancellation stages, and notifications to staff.
- Several delivery methods. Triggers can send email, SMS or channel messaging through Airbnb, Booking.com and Vrbo. The channel messaging pages include a separate article on channel message limitations.
- A ready-made library. The template and trigger library lists examples by stage. Pre-arrival includes "Send Arrival Information to Guest" and "Send Morning of Arrival Information"; mid-stay includes "Send Departure Information" and "Send Morning of Departure Information"; post-departure includes "Post Departure Review Request"; pre-booking includes replies to inquiries about unavailable dates or missing information.
- Field codes and conditions. The messaging pages reference field codes that insert booking and guest information into a message, and trigger setup includes conditions that must be met before a trigger runs.
I could not read every article in full detail, so check the current settings in your own account before you rely on any of them.
Set them up so they carry more
Whatever you use for the rest, a good set of triggers removes a lot of repeat questions.
- Start from the library, not a blank page. Copy the stage templates and edit them. It is faster, and it shows you which moments OwnerRez expects you to cover.
- One trigger per moment the guest needs something. Booking confirmed, a few days before arrival, the morning of arrival, the morning after, departure day, after departure. Resist adding a message for every question; a long message gets skimmed.
- Put the answers in the message before they are asked. Arrival message: how to get in, parking, Wi-Fi, quiet hours, who to contact. Departure message: checkout time and what to do with keys and trash.
- Use field codes instead of typed values. A message that names the guest, dates and unit reads as written for them, and one edit fixes it everywhere.
- Check each channel. Email, SMS and channel messaging behave differently, and the channel limitations article exists for a reason. Read how your text looks on each before you switch a trigger on.
- Test as a guest. Send yourself the whole sequence and read it in order. Cut anything that repeats.
Keep the sequence short enough that you can remember what each message says; the day a guest quotes your arrival message back to you, you want to know what it contained. Then write down the questions that still arrive. Use that list to improve your templates and identify requests that still need a separate reply.
What is left over
An illustrative scenario, not a customer: a guest writes the day before arrival to ask whether a second car fits, whether the pet policy covers a small dog, and whether check-in can move earlier. The answers exist, scattered across one unit's parking notes, its house rules and the calendar. A template can include the parking and pet rules; an early check-in request may still need someone to check readiness and approve it. So someone reads the reservation, opens the unit's notes and types a reply, often late in the evening.
Multiply that by every unit and every weekend, and the inbox becomes the place where the operation's missing answers show up. The cost is not any single reply. It is that the answer lives in a person, and the person is you.
How InnSync answers the rest
InnSync works alongside OwnerRez. Your triggers keep sending the messages they send. Carmen, InnSync's AI agent, takes the questions that arrive after them. She writes each reply from the booking, the unit and your house rules, through the channels confirmed during onboarding, instead of from a generic script, and hands anything unusual to a person on your team with the context attached. You choose, per channel, whether she replies on her own or drafts for you to review.
Two things stay true. Keep each unit's rules documented, and use review mode while you check Carmen's replies against them. And a decision that belongs to you, such as whether to allow an earlier check-in, goes to you. What changes is that the question arrives with the reservation, the unit and the house rule already attached.
If you use OwnerRez
Keep OwnerRez. InnSync runs the operation around it — the connection is set up with you during onboarding.
The first guest-reply workflow, the booking data it reads and the channels it covers are agreed with you during onboarding.
Next step
Take the last ten messages guests sent after your arrival message. Sort them into what an improved template could answer and what needed a separate decision or reply. If the second pile is the larger one, see how InnSync works with OwnerRez.