Tags and message triggers

Any way to incorporate the new Tag feature into message triggers?

What I'd like to do is only send my welcome letter with door lock code to guests who have both signed the RA and sent me their ID. The easiest way I can think to keep track of this is by adding an "ID Received" tag to bookings once I receive a copy of their ID. If the tag isn't present, then the message trigger shouldn't fire until the tag is added.

(Of course, I'd love OR to automate this entirely by integrating with an ID verification service--I've posted on that topic before. ;) )

Yes, integrating tags with triggers is a planned feature.

Looks like the logic for the Tags feature in the Triggers is either "Only" or "Everything But."

Can one more logic gate be added: "Contains"? I want to set up a trigger to send a Welcome Packet to people once I've verified their ID, which I'll mark by adding an "ID Verified" tag to their booking. But I also have other tags set up, so "Only" doesn't work, because a booking might have 2 or 3 other tags. So I need the trigger to send to all bookings that "Contains" the "ID Verified" tag, regardless of the presence or absence of other tags. That doesn't seem possible right now. Thanks!

The "only" option does not exclude bookings with other. By "only", it means that only bookings that contain that tag (regardless of any other tags they might have) will be included. So I think you should be good to go.

How do I set up something, from start to finish, if I need to receive a Guest Registration Form, before I send the email with the keyless entry? Thanks

You mean a signed Rental Agreement? There's a criteria in the Trigger you can use, so a given email won't be sent out if they haven't.

No. I mean something that they need to fill out for me and I would have to manually enter as a trigger stating YES, before send the last email with the Keyless entry code.

You'd probably want to do that with our new Tags feature - you'd create a tag that you manually add to a booking once the guest has done whatever it is that you want them to do, and then set having that tag as a criteria on the trigger.

Similarly, can you clairfy the "Everything But" option in Tags? I am using "Only" Tag "Photo ID Received" to trigger sending the guest their check-in letter. Converselyr, can I use "Everything But" Tag "Photo ID Received" to trigger sending the guest a reminder that we have not yet received their photo ID?

Yep! You can use "Everything but" to match any booking that does not have a particular set of tags.

Question about using tags in triggers: There are 2 types of tags, one related to bookings and one related to guests.

If we create a trigger to use "only" a specific tag, does the trigger look at ALL tags or only the tags related to bookings?

In the case of collecting IDs, it would make sense to add the "ID received" tag on the guest so that it is visible if the guest should book another stay in the future; we wouldn't have to ask them for a copy of their ID on subsequent bookings.

But if we create a trigger to automatically send Check-in instructions based upon "paid in full", "Rental agreement signed (yes)" and "ID received" will the system trigger the email if the tag is related ONLY to the guest? Or does it also need to be related to the booking?

Yes, the trigger looks at both Booking and Guest tags (as well as Property tags as well).

So something that applies to the guest in general like "ID received" that should apply to future stays you'd put on the guest. But something that applies to that particular booking like "flight info received" or something like that -- that would go on the booking.

We would like to see the use of TAG expanded. We have owners that do not wish to charge friends a Security Deposit and use a different Legal Agreement. We also charge a lower commission on owner referred bookings. This requires that it go beyond standard triggers and affect PM, rules and system messages. Is this possible in a future release? Also being able to automatically add, remove and change charges based on a TAG would solve problems regarding special handling in many situations. Adding a TAG to a booking that changed a number of parameters and standard charges would be VERY helpful.