⚡Quick answer -
• Variable mapping appears If the template has no variables, the mapping step is skipped and you proceed straight to contact upload.only when your selected WhatsApp template contains placeholders such as {{1}}, {{2}}.
• A fallback value is default text (e.g., “Customer”, “User”) that appears when a variable in your upload file is blank. Set each fallback on the Variable Mapping screen so every recipient sees a complete, professional message—even if some data is missing.
• Open it right after choosing a template in the campaign builder, so you know whether you must match spreadsheet columns to template variables.
• Use it immediately after you upload your Excel/CSV audience file and before you launch a personalised WhatsApp campaign. Correct fallbacks prevent broken messages and template rejections.
Does your template contain variables (e.g., {{1}}, {{2}})?
You encounter mapping if:
• The template preview shows placeholders like {{x}}.
• You’ve uploaded an Excel or CSV audience file.
Answer | What happens |
❌ No | Skip Variable Mapping → proceed to contact upload & scheduling |
✅ Yes | Variable Mapping screen appears → match each placeholder to a column in your Excel/CSV |
• Match variables – link each placeholder ({{1}}) to a column header (e.g., customer_name).
• Set fallback values – optional defaults such as “Customer” or “User”, etc.
• Preview – verify personalisation with the first rows of data.
• Prevents messages from failing when data is missing
• Keeps tone professional and user-friendly
• Maintains campaign continuity without delays
• Protects template approval by avoiding broken personalisation
Template: Hi {{1}}, your order of Rs{{2}} will be delivered on {{3}}.
Scenario | Message output | Result |
Without fallback | Hi, your order of Rs 1499 will be delivered on 25 July 2025. | ❌ Awkward, broken message |
With fallback “Customer” | Hi Customer, your order of Rs 1499 will be delivered on 25 July 2025. | ✅ Clean, professional output |
Scenario | System behaviour | Fix |
Template has no variables | Mapping step skipped | None needed |
Upload missing mapped columns | Error prompts upload of the correct file | Add missing headers |
Variables left unmapped | Messages won’t send | Map all variables or set fallbacks |
Issue | Impact | Recommended action |
No fallback + missing data | The message may fail or look broken | Always define a fallback |
Fallback too long | May truncate or trigger template rejection | Keep ≤ 25 characters |
Unsupported fallback types | Media or rich content not allowed | Use plain text only |
Visual mismatch | The layout may look off in the preview | Test with sample data & preview |
After mapping, the Preview Panel updates with real values or fallbacks. Confirmation message: “Variables mapped successfully — preview updated.”
• Preview multiple rows to catch mismatches.
• Use clear column names (name, amount, due_date).
• Define fallbacks for critical variables (e.g., “Customer”).
• If the template has no variables, focus on audience quality instead.
• Use neutral fallbacks like “Customer” or “User” for universal readability.
• Keep fallbacks policy-compliant (no promotional text inside Utility templates).
• Save your most-used fallbacks for reuse across campaigns.
Fallback values safeguard campaigns against missing data. Define them during variable mapping, keep them concise, and always preview before launch for error-free WhatsApp messaging.
Keywords: fallback value, variable mapping, WhatsApp template, blank variable, MyOperator