GhalaGhalaHelp Center
Back to ghala.ioghala.ioSign in
  • Getting Started
    • Ghala Documentation
    • Send Your First WhatsApp Message via API
    • Setting Up WhatsApp Webhooks
  • Commerce
    • Start Selling on WhatsApp
    • Set Up the AI Sales Agent
    • Get Paid with Snippe
  • Ai Automation
    • Configuring AI Auto-Reply for WhatsApp
    • Setting Up Human Handover Protocol
  • Campaigns Messaging
    • WhatsApp Message Templates: Complete Guide
    • Bulk WhatsApp Messaging: Complete Campaign Guide
  • Contacts Crm
    • WhatsApp Contact Management Guide
  • Best Practices
    • WhatsApp Customer Support Best Practices
    • Message Template Best Practices
  • Api Reference
    • Ghala API Reference

Products

  • Ghala
  • Sarufi
  • Snippe
  • Sema

Explore

  • Use Cases
  • Pricing
  • Blog

Developers

  • Docs
  • API Reference
  • API Quickstart
  • Webhooks Guide

Contact

  • SkyCity Mall, 9th Floor, Dar es Salaam, Tanzania
  • info@ghala.io
  • +255 699 920 009
© 2026 Neurotech Company LimitedTerms of ServicePrivacy PolicySitemap
  1. Help Center
  2. Best Practices
  3. Message Template Best Practices

Message Template Best Practices

Proven techniques for creating WhatsApp templates that get approved on the first try and perform well.

Two different audiences judge every template you write: Meta's reviewers, who decide if it sends at all, and your customers, who decide whether to reply or block. A great template passes both. The mechanics of building and submitting templates are covered in the templates guide; this article is about writing them well.

Write for Approval

Pick the honest category. The single biggest rejection cause is promotional content submitted as Utility. If the message exists to sell, it's Marketing; if it exists because the customer did something (ordered, booked, paid), it's Utility.

Give variables context. Reviewers see your template with placeholders, so the text around each variable must make its meaning obvious:

  • Weak: {{1}} {{2}} is ready
  • Strong: Hi {{1}}, your order #{{2}} is ready for pickup

Keep the structure clean. Number variables in sequence ({{1}}, {{2}}, {{3}}), never start or end the body with a bare variable, and skip the tricks reviewers are trained to reject: heavy caps, stacked emoji, URL shorteners.

Name templates for the audit trail. order_shipped_v2 tells you what it is a year later; template_final_new2 doesn't.

Write for Response

Approval is the entry fee; the real goal is a reply.

Lead with the reason for the message. The first line shows in the notification preview: "Your order has shipped" earns the tap, "Dear valued customer" doesn't.

One message, one job. A template announcing a sale, introducing a product, and asking for feedback does none of them well. Split it.

Make the next step a tap. Buttons outperform "reply YES if interested." Use a quick reply for conversations and a URL button to your storefront or checkout link for purchases.

Personalize past the name. "Hi Amina, the sneakers you asked about are back in stock" reads like service. "Hi Amina, check out our new arrivals!" reads like advertising. Same variable count, different outcome.

Respect the medium's intimacy. WhatsApp templates land between messages from family and friends. Messages that respect that (short, relevant, occasional) keep opt-outs low and your quality rating high.

Protect Your Quality Rating

Meta scores your number by how recipients react. Templates influence it more than anything else you send:

  • Include an opt-out line in every marketing template, and honour opt-outs the same day
  • Watch blocks after each campaign; a spike means wrong audience or wrong frequency, so fix that before sending more
  • Retire templates whose reply rates decay; audiences tune out repetition

A Pre-Submission Checklist

  1. Category matches the content honestly
  2. Variables numbered in order, each with context around it
  3. No bare variable at the start or end of the body
  4. Opt-out line present (marketing templates)
  5. Sample values read like a real message
  6. Name is lowercase, descriptive, versioned

What's Next

  • The full template lifecycle: WhatsApp Message Templates
  • Put templates to work: Bulk WhatsApp Messaging
PreviousWhatsApp Customer Support Best PracticesNextGhala API Reference

On this page

  • Write for Approval
  • Write for Response
  • Protect Your Quality Rating
  • A Pre-Submission Checklist
  • What's Next