Mews-connected properties can tell guaranteed bookings apart from bookings with no payment details on file. When a Mews reservation has a credit card attached to it, Bookboost records the reservation's guarantee type as a credit-card guarantee, and the reservation.guarantee_type token resolves. Mews has no single guarantee-type field, so Bookboost derives the value from whether a card is attached to the reservation.
What it does
When a reservation syncs from Mews, Bookboost checks whether a credit card is attached to that reservation.
If a card is attached, the reservation's guarantee type is set to
credit_card. If not, it stays empty.The value is available as the
reservation.guarantee_typetoken in the Mews token picker when you compose a message or campaign.
Because an empty value means "no card attached to this reservation", the token works as a yes or no signal: use it to split guaranteed bookings from the rest.
How to set this up?
There is nothing to enable. Once the Mews integration is active, the guarantee type populates on its own and the token appears in the Mews token picker alongside the other reservation tokens.
Two things to expect the first time you use it:
Reservations that synced before this change are not backfilled. The value fills in the next time the reservation syncs or is updated in Mews. Mews data syncs about every five minutes.
The stored value is the literal text
credit_card, not a tidied-up label. Use the token in conditions, filters, and audience rules rather than printing it straight into a message, otherwise the guest seescredit_cardin the text.
What you can do with this
Send a different pre-arrival message to guests whose booking is guaranteed and to guests whose booking is not.
Prompt guests with no card attached to add their payment details before arrival.
Build audiences that separate guaranteed from non-guaranteed bookings for follow-up.
What this does not do
Only the credit-card guarantee is detected. Guarantees based on a payment already made, or on billing routed to a company, are not covered, because Mews only exposes those indirectly.
The card has to be on the reservation. A card stored on the guest profile but not linked to the reservation is not picked up. That link is set most reliably when the guest goes through online check-in, or when the booking channel attaches the card.
There is no second value to test for. The token returns either
credit_cardor nothing at all.Old reservations are not backfilled. Reservations that last synced before this change stay empty until they sync or change again.
Common questions
Why is the token empty for some reservations?
No credit card is attached to that reservation in Mews. That is the only signal used, so an empty value means no card on the booking.
The guest has a card saved in Mews, so why is the reservation still empty?
A card on the guest profile is not the same as a card attached to the reservation. Check the reservation itself in Mews.
What values can I test for in a condition?
credit_card, or empty. There is no separate value for a payment-based or company-billing guarantee today.
A booking I made last month is still blank. Is it broken?
Reservations are not backfilled. The value fills in the next time that reservation syncs or is updated in Mews.
Getting help
Open Talk to Us in the left menu, or email support@bookboost.io.