Skip to main content
This page is the deep reference for the parts of a template — variables in the body and text header, media headers, and buttons. If you’re creating your first template, read Create a Template first.

Variables reference

Template variables use numbered placeholders that are replaced at send time.

Format

{{1}}  {{2}}  {{3}}  …
  • Double braces on each side.
  • Digits only — no names, no spaces.
  • Start at {{1}} and number sequentially.
Template variables use {{1}} style — indexed numbers.Bot Flows use a different syntax — {variable_name} with single braces and a name.Don’t confuse them. Template variables are always numeric and double-braced.

Where variables are allowed

LocationVariables allowed
Text headerYes — up to 1
BodyYes — sequential, practical max ~10
FooterNo
Media header (image/video/document)No (the sample file is separate)
Quick-reply button labelNo

Variable rules

  • Every variable must have a sample value supplied when you create the template.
  • Variables must be numbered sequentially — no gaps.
  • The body cannot start or end with a bare variable — wrap them in fixed text.
  • The same variable number can be reused multiple times in the body.

Good vs. bad variable use

GoodBad
Hi {{1}}, thanks!{{1}} as the entire body
Order #{{1}} is ready.{{1}} alone at the very end of the body
Short values: names, dates, IDsLong values: paragraphs of marketing copy
See Dynamic Templates for how variables get values at send time.

Media headers

You can put an image, video, or document at the top of a template message. Pick the header type when creating the template; supply the actual file when sending each campaign or message.

Header types

Xobito supports four header format options:
FormatFile formats
TEXTPlain text (supports 1 variable)
IMAGEJPG, PNG
VIDEOMP4
DOCUMENTPDF

Media size limits

WhatsApp enforces its own upload size limits. Practical guidelines:
Header typeTypical ceilingRecommended
ImageA few MBCompress well under 1 MB for fast delivery
VideoTens of MBKeep under 30 seconds
DocumentLarger PDFs allowed but slowerUnder 10 MB for fast delivery
Oversized files can fail silently — the message text arrives but the media doesn’t. Always test a template with a real phone before doing a large campaign.

Uploading the sample file

When you create a template with an IMAGE, VIDEO, or DOCUMENT header, you upload one sample file. Meta uses this sample during their review. It doesn’t have to be the file you will ultimately send to recipients — it just has to represent the template’s purpose.
  • For an order-confirmation template: upload a sample receipt image.
  • For a welcome-video template: a short branded intro clip.
  • For a terms template: a sample terms PDF.

Sending the real file at send time

When you later send the template in a campaign or chat, Xobito asks for the actual media file for this send. You can use a different file each time, as long as it matches the declared header type.

Image best practices

WhatsApp displays header images in a landscape-ish crop on most devices. Square or tall images may crop awkwardly.
Smaller images load instantly on slow networks. Tools like Squoosh or TinyPNG can compress without visible quality loss.
Text inside an image is small, unsearchable, and often hard to read. Use the image for visuals, the body for words.
What looks good on a desktop monitor may be unreadable on a 5-inch screen.

Video best practices

WhatsApp users scroll fast. 15–30 seconds is a good ceiling.
H.264 video + AAC audio is the most compatible combination across phones.
Most video on WhatsApp gets watched with the sound off. Burn captions into the video.
The first two seconds decide whether someone watches on.

Document best practices

Other formats may not display predictably on all devices.
Recipients see the filename. Invoice-April-2026.pdf is clearer than doc_final_v3.pdf.
If the PDF has editable fields or comments, flatten them before sending to avoid unexpected edits.

Buttons

Xobito’s template builder currently supports Quick Reply buttons explicitly. Quick Reply buttons are tappable buttons that send a preset reply back to your WhatsApp number.
Meta’s wider template platform also supports URL and Phone Number buttons. Xobito’s current builder implementation is focused on QUICK_REPLY handling; if your workspace has URL or phone button options available, use them per the in-product labels. Otherwise, include links or phone numbers as plain text in the body.

Quick Reply buttons

  • Purpose: send a preset text reply back to your workspace when tapped.
  • Label: short, action-oriented — Confirm, Cancel, Yes, please.
  • Good use cases:
    • Order confirmation: Confirm / Change delivery.
    • Appointment reminder: I'll be there / Reschedule.
    • Quick survey: Good / Bad.
When a recipient taps a Quick Reply button, your bot flow or inbox can branch on that reply to continue the conversation automatically.

Formatting in the body

WhatsApp supports basic rich formatting inside the body:
MarkupResult
*bold*bold
_italic_italic
~strike~strikethrough
Triple backticksmonospace
Line breakspress Enter
Emojispaste or type directly: 👋 🎉 ✅
Use bold for order numbers and totals — they stand out and make confirmations easy to scan. Don’t bold everything; it defeats the purpose.

Character limits

PartLimit
Template name512 characters (keep it short for readability)
Text headerShort (WhatsApp caps it)
BodyMeta’s body limit applies — aim for 1024 characters or fewer
FooterShort single line
The builder flags over-limit fields before submission.

Next steps

Create a template

Step-by-step walkthrough with screenshots.

Dynamic templates

How to fill variable values at send time.

Meta approval

Avoid rejection with our rejection-reason guide.

Custom fields

Store the data you’ll merge into templates.