Set up, in Automations → Post-booking, the message guests receive as soon as a booking is created — by email, WhatsApp or both.
It is the message that goes out as soon as the booking is created, with nothing for you to do. It serves to confirm the booking, give the next instructions and, where relevant, explain how the guest pays.
It can be delivered by email, WhatsApp or both. The content is the same on both channels: it is one message, delivered in more than one place.
Go to Automations and open the Post-booking tab.
The screen has two parts:
Each situation has at most one message. Understand each one better in what changes in each payment situation.
1. Find the section for the situation you want to configure.
2. Click Add.
3. Give the message a name. It is only for your own reference — the guest never sees it.
4. Choose the channels: Email, WhatsApp or both. At least one is required — with no channel the message reaches nowhere, and the screen tells you so on save.
5. Write the message. Below the field you will find the list of available variables, such as {{guestFirstName}} and {{propertyName}}.
6. Click Save.
Once saved, the section shows a card with the message, and the Add button disappears from that section — because that situation's message already exists. To change the text, use Edit on the card itself: changes are saved to the same message, without creating copies.
Pay later, Pix via Asaas and Card via Asaas fall back to the Default message while they have no message of their own. In those cases the section shows "Uses the default message" — that is not an error, it is the expected behaviour.
These are two different things, and the distinction is worth understanding:
Pausing a message does not make the situation fall back to the default message — it simply stops sending. And if the Default message itself is paused, the situations that rely on it also stop sending; the screen warns you of that in the section.
Each message card offers a preview. It shows the text that would go out, with the variables filled in.
Nothing is sent to the guest during a preview.
Paused messages can still be previewed: you see the stored content and, alongside it, a notice explaining why nothing would be sent in the current state — automation off, message paused, or default message paused.
At the bottom of the screen you may see an Unused old messages area. These are post-booking messages not attached to any of the five situations, and therefore not sent.
They are there so you can delete what you no longer need. If the area does not appear, there are none in that state.
Can I have more than one message in the same situation?
No. Each situation has exactly one message — which is why the Add button disappears once you create the first.
If I switch the automation off, do I lose what I wrote?
No. Switching off only stops the sending. All the content stays stored, and switching it back on changes nothing.
Can the same message be used in more than one place?
It can happen. In that case, opening it for editing shows a notice listing the other places it is used, because the change applies to all of them.
Pipeline templates and post-booking messages: which is which
Understand why there are two message areas, what each one is for, and why post-booking messages do not show up in the Pipeline list.
The email guests receive when they book
Understand the initial booking email, when it goes out, why there is only ever one, and how post-booking content is included in it.
How to connect WhatsApp
Connect your WhatsApp number so automatic messages reach guests, and know what to do when the connection drops.