{"id":38922,"date":"2026-05-05T09:00:00","date_gmt":"2026-05-05T09:00:00","guid":{"rendered":"https:\/\/www.aurorainbox.com\/?p=38922"},"modified":"2026-05-05T09:00:00","modified_gmt":"2026-05-05T09:00:00","slug":"crear-plantillas-whatsapp-aprobadas-meta","status":"publish","type":"post","link":"https:\/\/www.aurorainbox.com\/en\/2026\/05\/05\/create-approved-whatsapp-templates-meta\/","title":{"rendered":"How to create WhatsApp Business templates that Meta will approve on the first try (2026)"},"content":{"rendered":"

Getting Meta to approve your WhatsApp Business templates on the first try depends on six things: the correct category (marketing\/utility\/authentication), a respectful tone without false urgency, clear variables with readable labels, only one CTA per message, content specific to the use case (not generic), and compliance with WhatsApp's business policy. Approval, when everything is in order, takes minutes to hours\u2014and your operational life changes dramatically when you stop battling rejections.<\/p>\n

Why Meta rejects WhatsApp templates<\/h2>\n

Meta's review system operates with two layers: automated classifiers and human review in borderline cases. The five causes that trigger rejection are:<\/p>\n

    \n
  1. Incorrect category.<\/strong> A promotional template submitted as a "utility" is automatically rejected.<\/li>\n
  2. Aggressive language.<\/strong> Excessive capitalization, false urgency, threats \u2014 all rejected.<\/li>\n
  3. Prohibited content.<\/strong> Alcohol, tobacco, gambling in some countries; unauthorized financial services; unlicensed pharmaceuticals.<\/li>\n
  4. Misused variables.<\/strong> {{1}}<\/code> without context explained in the documentation.<\/li>\n
  5. ambiguous or multiple CTAs.<\/strong> More than one call to action per message.<\/li>\n<\/ol>\n

    The four Meta categories and when to use them<\/h2>\n\n\n\n\n\n\n\n\n
    Category<\/th>\nWhat is it for?<\/th>\nCost (Mexico USD\/conversation)<\/th>\n<\/tr>\n<\/thead>\n
    Marketing<\/strong><\/td>\nPromotions, offers, announcements, launches<\/td>\n$0,0436<\/td>\n<\/tr>\n
    Utility<\/strong><\/td>\nConfirmations, reminders, account updates, collections<\/td>\n$0,0080<\/td>\n<\/tr>\n
    Authentication<\/strong><\/td>\nOTP codes, 2FA verification<\/td>\n$0,0309<\/td>\n<\/tr>\n
    Service<\/strong><\/td>\nResponse within 24h window<\/td>\nFree<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Operating rule: If you're torn between marketing and utility, it's almost always utility.<\/strong>Marketing is solely for explicit promotion.<\/p>\n

    6 rules for Meta to pass on the first try<\/h2>\n

    1. Maintain a respectful tone<\/h3>\n

    Bad: "LAST CHANCE! Your payment is due TODAY!"
    \nOkay: "Hello {{1}}, your ${{2}} payment is due on {{3}}. Link: {{4}}."<\/p>\n

    No capital letters, no multiple exclamation marks, no false urgency.<\/p>\n

    2. Customize with clear variables<\/h3>\n

    Each {{N}}<\/code> It must have a clear label in the documentation you upload to Meta. Good examples: {{1}}=name<\/code>, {{2}}=amount<\/code>, {{3}}=date<\/code>.<\/p>\n

    Bad: "Hello {{1}}, you owe ${{2}}, pay here {{3}}."
    \nOkay: "Hello {{customer_name}}, friendly reminder: your $ {{amount}} invoice is due on {{due_date}}. To pay: {{payment_link}}."<\/p>\n

    3. One CTA per message<\/h3>\n

    Bad: "Call us at X, write to us at Y, schedule an appointment at Z."
    \nOkay: "To schedule: {{link_calendario}}."<\/p>\n

    Multiple CTAs confuse the receiver and lower conversion.<\/p>\n

    4. Be specific to the use case<\/h3>\n

    Generic error: "Hello, thank you for contacting us."
    \nTo be very specific: "Hi {{1}}, we received your interest in an Aurora Inbox demo. I have {{2}}, {{3}} or {{4}} available this week \u2014 which one works for you?"<\/p>\n

    Generic templates are rejected due to "low quality content".<\/p>\n

    5. Comply with the commercial policy<\/h3>\n

    Categories prohibited or restricted in some countries: alcohol, tobacco, gambling, unlicensed pharmaceuticals, financial services without local authorization. Check the Meta's trade policy<\/a> before going up.<\/p>\n

    6. Document each variable<\/h3>\n

    When uploading the template, complete the "Sample values" section with real values. Meta uses these examples to validate that the variable meets the category.<\/p>\n

    Recommended template structure<\/h2>\n
    [Personalized greeting with {{name}}] + [Concrete and specific information] + [A single CTA with link] + (Optional) [Short footer: sender's identity]\n<\/code><\/pre>\n
    Full example:<\/p>\n
    Hello {{client_name}}, this is {{agent_name}} from {{company}}. Your appointment is confirmed for {{date}} at {{time}} at {{address}}. To reschedule: {{calendar_link}}. {{company}} Team.\n<\/code><\/pre>\n
    Examples by category<\/h2>\n
    Marketing \u2014 launch promotion<\/h3>\n
    Hello {{name}}, we're launching {{product}} with a welcome discount of {{discount}}% valid until {{date}}. See details: {{link}}.\n<\/code><\/pre>\n
    Utility \u2014 order confirmation<\/h3>\n
    Hello {{name}}, your order #{{folio}} has been confirmed. Total: ${{amount}}. Estimated delivery: {{date}}. Tracking: {{link}}.\n<\/code><\/pre>\n
    Utility \u2014 appointment reminder<\/h3>\n
    Hello {{name}}, we are reminding you of your appointment at {{location}} on {{date}} at {{time}}. If you need to reschedule: {{link}}.\n<\/code><\/pre>\n
    Authentication \u2014 OTP<\/h3>\n
    Your verification code is {{code}}. Valid for 10 minutes. Do not share it with anyone.\n<\/code><\/pre>\n
    Collection \u2014 payment reminder<\/h3>\n
    Hello {{name}}, your $ {{amount}} payment (folio {{folio}}) is due on {{date}}. Pay: {{link}}. If you have already paid, ignore this message.\n<\/code><\/pre>\n
    Common mistakes that trigger rejection<\/h2>\n