A tour operator can be dealing with a reserved trip, a payment and a signed waiver while customers wait for practical information. Staff may need to check TripWorks, copy booking details and send directions or confirmation messages by hand. When the day is busy, that manual chase can leave a customer without the information they need.

With Zapier, TripWorks events such as Trip Reserved, Payment Created and Waiver Signed can run Mobile Message's Send SMS action. A reservation can prompt a confirmation, a payment can produce a receipt notice and a signed waiver can trigger a final preparation message. New Customer Created can run Create Contact, while Customer Updated can update an existing Mobile Message contact when suitable details are available.

The result is a clear customer touchpoint tied to the event that matters. These are separate, one-directional Zaps rather than a two-way sync between platforms. Map the booking name, date, reference and relevant instruction into each plain text message. Operators can then spend less time checking for routine changes and more time preparing the actual trip.