Integrations·Message Templates

Message Templates

Every automated message TourMan sends — Tour Confirmation, Low/No Pay Verification, No-Show Follow-up — has to be a template Meta has pre-approved. Since these go out to a guest who hasn't necessarily messaged you first, WhatsApp requires the exact wording to be reviewed in advance, not sent as free text.

Templates are created and approved in Meta, not TourMan — you'll need WhatsApp connected first. See How to Connect WhatsApp if you haven't yet.

Open Message Templates

Go to WhatsApp Manager → Message Templates and click Create Template. First double-check the Business Portfolio selected in the top-left corner — if you manage more than one, this page always builds templates for whichever one is currently selected there.

Building it

1

Category: Utility

Tour Confirmation, Low/No Pay Verification and No-Show Follow-up are transactional, not promotional — pick Utility. It's the correct category for this content, and it's billed at a lower rate than Marketing.

2

Name the template

Anything descriptive works — you'll be entering this exact name into TourMan afterward, so pick something you'll recognize later (e.g. tour_confirmation_en).

3

Language

Pick the base language — e.g. plain English, not a regional variant like "English (UAE)". TourMan matches on the base language and won't find a regional-variant template.

TourMan currently supports: English, Spanish, French, Italian, Portuguese. A template covers one language — repeat this whole process for each one you need.

4

Variable Type: Named

When the editor asks how to reference variables in the body, choose Named (not Positional/numbered). This lets you write {{tour_name}} directly instead of {{1}} — and it's what TourMan expects when it fills a template in.

5

Header (optional)

Not required — skip it, or use it for a short title line if you want one.

6

Body — use TourMan's variable names

Write the message, dropping in any of these where you want TourMan to fill in details for that specific booking. Names have to match exactly:

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 point
{{booked_count}}Guests expected (No-Show Follow-up only)
{{checked_in_count}}Guests who checked in (No-Show Follow-up only)
{{missing_count}}Guests who did not show (No-Show Follow-up only)

Only use the ones that make sense for this message — none are required, and any subset is fine.

7

Variable Examples

Meta requires an example value for every variable you used, before it'll review the template — e.g. for {{tour_name}}, enter something like Sunset Kayak Tour. These examples are only shown to Meta's reviewers, never to guests — the real booking's data fills in when TourMan actually sends the message.

8

Footer (optional)

Also not required — a small line of grey text under the body, if you want one (e.g. your business name).

9

Buttons — 2 or 3 buttons, type Custom

Add the buttons as type Custom, in this order — TourMan identifies each answer by the button's position, regardless of its exact wording:

Tour Confirmation

First button confirms attendance (e.g. "Yes, I'll be there"), second declines (e.g. "No, can't make it"). A tap sets the booking's pre-check-in status.

Low/No Pay Verification

First button confirms payment (e.g. "Yes, I paid"), second denies it (e.g. "No, not yet"). Recorded for staff to review — doesn't change the booking automatically.

No-Show Follow-up — 3 buttons

First button: running late (e.g. "I was running late"). Second: changed plans (e.g. "I changed my plans"). Third: attended (e.g. "I attended the tour"). Shown on the No-Shows page; a third-button answer flags the booking as disputed.

10

Submit for review

Meta reviews the content and structure before approving it — usually within a few minutes to about a day, occasionally longer. A template can be rejected if the category doesn't match the content, or the wording reads as promotional rather than transactional.

What it looks like

Roughly how Meta's own Your template preview shows it while you're building it — variables stay as {{like_this}} here; the guest sees the real booking's details instead once TourMan actually sends it:

Your template

Tour Confirmation

Hello {{name}}! Will you be joining the tour? 🎫 Tour: {{tour_name}} 📅 Date: {{date}} ⏰ Time: {{time}} 📍 Meeting Point: {{meeting_point}} See you there!

19:38

Yes
No

Your template

Low/No Pay Verification

Hi {{name}}, Thanks for joining {{tour_name}}! Our records show your payment may be incomplete. Have you already paid?

19:38

Yes
No

Your template

No-Show Follow-up

Hi {{name}}, We expected {{booked_count}} guests for {{tour_name}} on {{date}}, but {{checked_in_count}} checked in. Could you tell us what happened?

19:38

I was running late
I changed my plans
I attended the tour

Keep button labels short — WhatsApp truncates long ones, and a plain Yes / No reads clearly either way.

Once approved, go to TourMan's Settings → Integrations → WhatsApp and enter the template's exact name against the matching message type and language — see the Message Templates section of Settings: Integrations.

Message Templates — TourMan Docs