What is a Meta first-message template?

Short version:

• It is not the same as a CRM quick reply
• It is a Meta-approved WhatsApp template
• It is usually needed for first contact, re-engagement, or communication outside the 24-hour window

So the purpose is:

• not just speeding up an active conversation
• but starting or re-opening a conversation in a compliant way

Make this distinction first

Before creating any template, answer this:

1. Is the customer already in an active conversation?

If yes:

• a CRM-side template is often enough
• you may not need a Meta-approved template

If no:

• a Meta-approved first-message template may be required

2. What is the actual goal?

You should consider the Meta side if the goal is:

• contacting a customer for the first time
• restarting a closed conversation
• following up on a reservation or inquiry
• requesting missing information
• reopening a pricing flow

You should usually stay on the CRM side if the goal is:

• replying faster in an active conversation
• sending a quick greeting
• speeding up price, reservation, or payment operations

The shortest decision rule

Make this a team standard:

If the conversation is active, think CRM first.
If this is first contact or re-contact, think Meta first.

What should a Meta first-message template do?

A strong first-message template should:

• identify the brand or team
• clearly state why you are writing
• ask for one clear next action
• make the rest of the conversation easier

It should not try to:

• complete the full process in one message
• sound overly promotional
• explain too much at once
• leave the outreach reason unclear

The 4-part structure of a strong first message

In practice, the cleanest structure is:

1. Brand or team name
2. Reason for outreach
3. Clear customer action
4. If needed, 1-2 variables

Example:

Hello {{1}}, this is the Bonjuro team.
To continue with your request, could you share your preferred date and guest count?

In this example:

• {{1}} can be the customer name
• the reason is clear
• the expected reply is obvious

Good vs bad examples

Bad example 1

Hello, how are you?

Why it is weak:

• no context
• no reason for contact
• does not move operations forward

Bad example 2

We have great offers for you. Reply now.

Why it is weak:

• too promotional
• weak customer context
• feels like pressure rather than service

Better example 1: opening a pricing flow

Hello {{1}}, thank you for your interest.
To share the right pricing options, could you send your dates and guest count?

Why it works better:

• the goal is clear
• the requested info is specific
• it prepares the next step

Better example 2: opening a reservation flow

Hello {{1}}, we received your reservation request.
To continue, could you share the hotel name and your arrival date?

Why it works better:

• the reason for outreach is clear
• the next action is simple
• the operations team can continue easily

Better example 3: re-engagement

Hello {{1}}, we are following up regarding your earlier request.
If you would like to continue, just send your preferred date.

Why it works better:

• the re-contact reason is clear
• it does not feel too aggressive
• it reopens the conversation cleanly

When should you create a separate Meta template?

Creating a separate template makes sense for:

• starting a price inquiry
• opening a reservation process
• completing missing information
• following up before payment
• reconnecting with a paused customer

It may be unnecessary when:

• only the wording changes slightly
• you would create many variants for the same job
• the team can already handle the need with CRM-side quick replies

How should variables be used?

The healthiest approach is:

• few variables
• clear variables
• only necessary variables

For a first message, these are often enough:

• customer name
• hotel or service name
• one critical field such as date

Risky approach:

• too many variables
• variables that are not filled reliably
• making agents do too much manual checking

Rule:

The goal of a first message is not maximum personalization. It is high clarity with low friction.

How Meta templates and Bonjuro templates should work together

The cleanest model is a two-layer setup.

Layer 1: Meta template

Its job:

• open the first contact
• restart communication
• get the first customer reply

Layer 2: Bonjuro internal templates

Their job:

• speed up the conversation
• handle price inquiries
• move reservation flow forward
• simplify payment and follow-up messaging

Bonjuro already supports this through:

• Greeting
• Reservation
• Payment
• Price Query (Hotel)
• Price Query (Tour)
• shortcut-based access
• context-based variable filling

Short summary:

• the Meta template opens the door
• Bonjuro templates carry the operation

What should operations prepare before asking for a template?

Before opening a Meta template, the team should clearly define:

1. Which scenario this message serves
2. Why the customer is being contacted
3. What first response is expected
4. Which variables are truly necessary
5. Which Bonjuro template will be used after the customer replies

If those answers are unclear, the template will often be redundant or underused.

Most common mistakes

These are the most common problems:

• treating CRM and Meta templates as the same tool
• opening too many templates for the same purpose
• writing vague copy
• using too much sales pressure
• making the first message too long
• overusing variables
• creating templates without planning the next operational step

Quick checklist

Before creating a new Meta first-message template, use this checklist:

• Does this message really require Meta approval?
• Is the reason for outreach clear in the first lines?
• Does the message serve one specific purpose?
• Is the customer action explicit?
• Are there unnecessary variables?
• Does another template already solve the same need?
• Is the next Bonjuro template after the reply already defined?

If you cannot answer most of these clearly, the template is not ready yet.

Recommended team standard

It helps to standardize this:

• Every Meta template should serve one clear purpose
• Every Meta template should have a defined Bonjuro follow-up template
• Avoid unnecessary variants
• Keep the first message short, clear, and action-oriented

Conclusion

Meta first-message templates should be treated separately because they solve a different problem.

The stronger model is:

• use Meta templates to open or reopen the conversation
• use Bonjuro templates to accelerate the operation
• keep the first message simple
• ask for one clear customer action

This approach improves both approval quality and team speed.