The short version

Every message TripWorks sends to a guest -- automated or manual, email or text -- starts from the same message template. Automated moments on an activity's Email Automations tab decide when a template fires on its own; you can also send any template by hand, any time; and AI Chatbot and Callbot answer guests directly without a template at all.

Why this matters

Every message an operator has to remember to send by hand is a chance for it to happen late, inconsistently, or not at all -- a confirmation that's slow to go out, a reminder nobody sent, a cart that quietly goes cold, a phone call nobody answers.

Once you see templates, automated moments, and AI channels as one connected system instead of five separate tools, you know exactly where to go to change any message a guest gets, and which parts run themselves versus need your attention.

The mental model

One shared message template powers everything you send. A handful of automated moments decide when it goes out on its own. A manual send and an AI channel are always available for everything else.

Message Templates: the one building block

You write a message once in the template library, insert variables that fill in each guest's real details, and choose whether it also has an SMS version. From there it's reusable everywhere: an automated confirmation, a reminder, or a message you send yourself.

Automated messaging

Every activity has one Email Automations tab running a single timeline: a cart goes abandoned, a booking confirms, the activity approaches, the activity finishes. Each moment can trigger its own template, on its own schedule, without you touching it again after setup.

Abandoned cart recovery

Abandoned cart recovery lives on that same timeline, as the "Cart abandoned" moment -- substantial enough to earn its own dedicated lessons on setup, tuning, and reporting.

Sending a message manually

Any template -- automated or not -- can be sent by hand from a trip, any time: a weather update, a personal thank-you, or a nudge you don't want to wait for the schedule to catch.

AI Chatbot and Callbot

AI Chatbot answers guest questions on your website using your knowledge base and live availability, and AI Callbot does the same thing on the phone -- both can complete a booking, not just answer a question.

How it all connects

Templates are the content. Automations and manual sends are two ways that content reaches a guest. Abandoned cart recovery is automation applied to one specific moment worth its own attention. AI is the channel that doesn't need a template at all because it's answering in real time.

FAQ

What's the difference between a message template and an automated message?

A template is the reusable content -- what the message says. An automation is what decides when that template gets sent on its own, like a booking confirmation firing the moment a trip reserves. The same template can also be sent manually any time.

Where do I go to change what a reminder or confirmation says?

Open the template it uses in Message Templates and edit the content there. Where and when it sends is controlled separately, on the activity's Email Automations tab or the account-wide Email & SMS Automations page.

Do Chatbot and Callbot use message templates too?

No -- they answer guests directly using your knowledge base and live availability data, in real time, rather than sending a pre-written template. They're a different channel on the same communication system.

Transcript

Every message a guest gets from you is either something you built once and let run on its own, or something you sat down and sent by hand. When that line is blurry -- when nobody's sure if a confirmation already went out, or a cart just goes cold because no one noticed -- guests feel it as silence, and silence loses bookings.

Here's the simplest way to think about TripWorks communication: one shared message template powers everything you send, and a handful of automated moments decide when it goes out on its own -- with a manual send and an AI channel always available for everything else.

Concretely, it works like this. You build a message once, in the template library. That template can be attached to an automated moment -- a cart going cold, a booking confirming, a reminder before the activity, a follow-up after it -- so it sends itself. Or you pick that same template and send it by hand, to one guest or a whole trip. And increasingly, a guest doesn't need a template at all -- they can just ask Chatbot or Callbot a question and get a real answer, live.

Message Templates are the one building block behind everything else in this system. You write the content, insert variables that fill in each guest's real details, and choose whether it also has an SMS version -- once. From there it's reusable everywhere: an automated confirmation, a reminder, or a message you send yourself.

Automated messaging is where most templates actually get used. Every activity has one Email Automations tab running a single timeline: a cart goes abandoned, a booking confirms, the activity approaches, the activity finishes -- each moment can trigger its own template, on its own schedule, without you touching it again after setup.

Abandoned cart recovery lives on that same timeline, as the "Cart abandoned" moment -- but it's substantial enough to earn its own three lessons.

None of this locks you into waiting on automation. Any template -- automated or not -- can be sent by hand from a trip, any time.

The newest piece of this system skips templates entirely. AI Chatbot answers guest questions on your website using your knowledge base and live availability, and AI Callbot does the same thing on the phone -- both can complete a booking, not just answer a question.

Here's how it all connects: templates are the content, automations and manual sends are two ways that content reaches a guest, abandoned cart recovery is automation applied to one specific moment worth its own attention, and AI is the channel that doesn't need a template at all because it's answering in real time.

Put together, that's the shift: instead of wondering whether a message got sent or guessing which setting controls it, you know exactly where every guest communication lives -- what it says, when it fires, and who -- or what -- sent it.

Start with Message Templates if you haven't looked at yours yet, then check your activity's Email Automations tab to see what's already running. The next four lessons in this course go deeper on each piece.