If you use Apaleo, the comments your team and your guests leave on a reservation no longer have to stay in Apaleo. Bookboost now syncs those comments in as Notes, so your teams always have the latest guest requests and booking context in one place. You can also pull specific comments into your messages with new dedicated tokens, which makes it easy to personalise guest-facing communication while keeping internal notes internal.
Which Apaleo comments are synced
Bookboost ingests four comment fields from Apaleo and stores each one as a Note:
Guest comment (reservation level) — the guest's special requests.
Hotel comment (reservation level) — your internal hotel comment on the reservation.
Booker comment (booking level) — a comment from the person who made the booking.
Booking comment (booking level) — your internal hotel comment on the booking.
Each comment is synced as a separate Note, so you can see them individually against the guest.
How the sync works
Notes stay up to date without duplicating. Each Note is stored with a stable identifier, so when a comment changes in Apaleo the existing Note is updated rather than a new one being created. You will not end up with duplicate Notes.
The comments flow in automatically. Once the sync is active, new and updated Apaleo comments appear as Notes without any manual import.
Using the comments in your templates
You have two ways to bring these comments into a message template.
The existing notes token continues to include all synced Notes, so it will already pick up the Apaleo comments alongside your other notes.
Three new dedicated tokens let you insert one specific comment on its own:
Token | What it inserts |
| The guest's comment |
| The booker's comment |
| The internal hotel comment |
You will find these under Tokens > Reservation in the template editor. Add the dedicated token wherever you want that comment to appear in the template. It resolves at send time, the same way your other personalisation tokens do.
When to use each comment
Personalise pre-arrival messages with the guest's special requests using
reservation.guest_comment.Give staff context on who booked and why using
reservation.booker_comment.Keep internal ops notes out of guest-facing messages by relying on the internal comment for staff workflows rather than putting it in the guest's message.
Good to know
Notes are synced as raw text. There is no added formatting or prefix, so the comment appears exactly as it was written in Apaleo.
Common questions
Do I have to import the comments manually?
No. Once the sync is active, Apaleo comments come in as Notes automatically and stay updated.
Will I get duplicate Notes when a comment is edited in Apaleo?
No. Each Note has a stable identifier, so an edited comment updates the existing Note instead of creating a new one.
What is the difference between the notes token and the new dedicated tokens?
The existing notes token includes every synced Note together. The dedicated tokens (reservation.guest_comment, reservation.booker_comment, reservation.internal_comment) each insert just one specific comment, so you can place them exactly where you want.
Will the internal comment show up in a guest's message?
Only if you add the internal comment token to a guest-facing template. Use the guest and booker tokens for guest-facing messages, and keep the internal comment for your team's workflows.
Can I format the synced comment?
The comment syncs as raw text with no formatting or prefix, so it appears exactly as written in Apaleo.
Getting help
Open Talk to Us in the left menu, or email support@bookboost.io.