How to use Parameters in MyOperator App?

How to use Parameters in MyOperator App?

When creating WhatsApp Template Messages in the MyOperator App, you can include parameters—dynamic placeholders that personalize each message with customer-specific details (like names, order numbers, or dates).

⚡ Parameters make templates flexible, scalable, and mandatory for Meta approval if personalization is required.

🧩 What Are Parameters?

  • Parameters are placeholders written as double curly braces: , ,
  • They are replaced with real values at send time, pulled from your audience Excel/CSV.
  • You must also provide sample values during submission so WhatsApp can see how parameters will be used.

✍️ Step-by-Step: Adding Parameters

  1. Create a New Template
    • Go to Manage → Template Messages
    • Click New to create a WhatsApp Template
  2. Insert Parameters in Template Format
    • Use , , etc. in your message body where personalization is needed.
    • ✅ Example (Correct):Hello , your order is out for delivery.
    • ❌ Incorrect:Hello {1}, your order 2 is out for delivery.
    • 📌 Tip: Each parameter must be wrapped in exactly two curly braces.
  3. Provide Sample Values
    • In the Sample Message field, replace each variable with realistic placeholders in square brackets.
    • ✅ Example:Hello [John], your order [#12345] is out for delivery.
    • Required for Meta review—shows how personalization will look in practice.
  4. Submit for Approval
    • WhatsApp requires both the template format and sample message to be completed before review.

📊 Quick Reference Table

Stage

Format Example

Output Example

Template Format

Hello , your order is confirmed.

= customer_name, = order_id

Sample Message

Hello [Jane], your order [#A100] is confirmed.

Submitted to Meta for approval

Live Campaign Send

Hello Rahul, your order #B456 is confirmed.

Actual customer-facing message


⚠️ Approval Rules & Restrictions

  • Parameters are allowed only in:
    • Header (text only)
    • Body
    • Buttons (URL query strings, CTA labels)
  • Not allowed in the Footer (footer must be static text).
  • Every parameter in the template format must appear in the sample message.
  • Parameters must be sequential (, , … no skipping numbers).

🧠 Best Practices

  • Use clear, meaningful sample values ([Priya], [Order #12345]) instead of generic placeholders.
  • Keep parameter usage natural—avoid messages that look robotic.
  • Always preview your template before submission.
  • Use fallback values during campaign variable mapping (e.g., Customer if name is missing).
  • Don’t overload messages with too many parameters; Meta may reject them for poor user experience.

✅ Summary

  • Parameters personalize messages and are required for certain template approvals.
  • Always define them with in the format and provide sample values in [ ].
  • Follow Meta’s rules to avoid rejection (no parameters in footers, sequential numbering only).
  • Preview, test, and use fallback values for error-free campaigns.