Integrations
Connect and configure third-party integrations for your organization. Currently supports automated WhatsApp messaging.
Sends automated WhatsApp messages to customers via the official Meta Cloud API. Two message types are available, each configured independently:
Tour Confirmation
Asks customers to confirm attendance before their tour. A Yes/No reply is recorded, and Yes automatically pre-checks the booking in.
Low/No Pay Verification
After the tour, asks customers flagged Low/No Pay whether they already paid. The reply is recorded for the guest's feedback record — it does not change the booking automatically.
Note: WhatsApp needs to be enabled for your organization and connected to a Meta Cloud API account by TourMan support before this tab appears. Contact us to get set up.
Rule Settings
Each message type has its own card with an Enabled toggle, an optional name for your own reference, and targeting to narrow which bookings it applies to.
Field
Description
Tours
Limit the rule to specific tours. Leave empty to apply to all tours.
Languages
Limit to bookings in specific languages. Leave empty for all languages.
Platforms
Limit to bookings from specific platforms. Leave empty for all platforms.
Fallback language
Used when a booking’s own language has no template configured — see Message Templates below.
Tour Confirmation trigger
Send at hour
The hour of day (24h format) messages are sent, in your organization’s tour timezone.
Days before tour
How many days before the tour date the message goes out (0 = same day).
Max people on the slot
Skip slots that already have this many or more people booked.
Low/No Pay Verification trigger
Hours after tour start
How many hours after the tour's start time to send the message. Sent independent of check-in status.
Message Templates
Each rule can have one Meta-approved template per language. A booking is matched to the template for its own language, falling back to the rule's Fallback language (or the first template, if the fallback isn't set up either) when there's no exact match.
Templates themselves — their text and the Yes/No (or Paid/Not Paid) quick-reply buttons — are created and approved in Meta Business Manager. TourMan only needs the approved template's name and knows how to fill in the variables below.
Available Template Variables
When building a template in Meta Business Manager, any subset of these named variables can be used in the message body — only the ones actually present in the approved template get filled in.
Variable
Value
{{tour_name}}Tour name{{date}}Tour date{{time}}Tour time{{name}}Customer's name{{email}}Customer's email{{adult_count}}Number of adults booked{{children_count}}Number of children booked{{meeting_point}}Tour meeting pointHow Responses Are Handled
When a customer taps a quick-reply button, TourMan records the response against the original message. For Tour Confirmation, a Yes/No reply also sets the booking's pre-check-in status, visible on the booking card and in the check-in details. For Low/No Pay Verification, the reply is a self-reported answer from the guest — it's recorded for staff to review, not applied to the booking automatically.