WhatsApp Marketing Best Practices

Plan WhatsApp communications around the recipient, message purpose and connected sending account. Check the template, reply window and recorded opt-out state before sending; evaluate your own outcomes instead of treating a benchmark as a forecast.

Understanding WhatsApp Business

Why WhatsApp Marketing?

WhatsApp can support template-based updates and conversations with recipients who use it. Whether it suits your audience depends on their preferences, the message and the sending account.

  • Review recorded deliveries, reads, failures and replies separately; they are not equivalent outcomes.
  • A queued or accepted message is not proof of delivery, reading or a purchase.
  • Media and interactive features depend on the template and sending path. A capability offered by Meta is not automatically available through every Oblic workflow or API request.
  • No universal open rate, click rate or delivery deadline applies to your campaign.

WhatsApp Business vs WhatsApp Business API

The WhatsApp Business App and the Business Platform are different products. Check Meta's current product guidance rather than assuming an employee count, device limit or feature in the app defines what an API integration can do.

Oblic's connected-account flow supports eligible template messages and free-form replies through its configured sending services. Campaigns, automations, public API sends and bot conversations have different inputs and guards. Check the relevant Oblic screen or API contract rather than assuming that a general WhatsApp feature is implemented in each one.

Getting Started

Account Verification

Connect the intended organization and phone number through the configured signup flow. The API connection exchanges the signup code, subscribes the account's webhooks and registers the number. A refused or incomplete step is not a connected account; retry with valid inputs and verify the resulting state.

A business profile, a connected Oblic account, a provider badge and a template approval are different states. Completing one does not prove another, improve delivery by a guaranteed amount or remove messaging limits. Follow Meta's current process for any provider verification or badge; Oblic does not award one by saving a connection.

Business Profile Optimization

Essential Elements:

Business Name: Clear, recognizable brand name
Description: A concise account of what you do
Category: Choose relevant industry
Profile Photo: A recognizable logo that fits the current provider requirements
Business Hours: When customers can expect responses
Website: Link to your site
Email: Contact email
Address: Physical location (optional)

Profile Best Practices:

  • Use consistent branding across channels
  • Keep description concise and benefit-focused
  • Update business hours for holidays
  • Respond to messages during stated hours

Message Types and Pricing

Understanding Message Categories

Free-form replies: Oblic checks that the recipient's last inbound message to the account's number is within the 24-hour customer service window. It checks again when sending, so a reply queued near the end can be refused later. A newly saved contact or an outbound message does not itself open that window.

Template messages: Check the intended language, approval, active state and all required values. A saved or submitted template is not automatically approved or sendable. Marketing sends also check recorded opt-outs and the paying wallet; other message kinds still have their own eligibility and provider checks.

Meta's charges depend on the message category and destination market, with exceptions described in its current platform pricing. Meta does not charge for service messages within the customer service window; this is not a promise that Oblic or another provider adds no charge. Check your applicable plan and provider terms. This guide does not quote a fixed per-message price or guarantee that one category always costs more than another.

Template Message Categories

Utility (Transactional):

  • Order confirmations
  • Shipping updates
  • Appointment reminders
  • Payment receipts
  • Account notifications

Authentication:

  • OTP codes
  • Password resets
  • Two-factor authentication
  • Login verification

Marketing:

  • Promotional offers
  • Product launches
  • Event invitations
  • Newsletter updates
  • Cart abandonment

Template Design Best Practices

Creating Effective Templates

Template Structure:

Header (Optional):
- Text or media supported by the chosen template and sending path

Body (Required):
- Main message within the applicable template requirements
- Use variables for personalization
- Clear, conversational tone

Footer (Optional):
- Additional context within the applicable template requirements
- Terms, disclaimers, contact info

Buttons (Optional):
- Call-to-Action (URL or Phone)
- Quick replies supported by the chosen template and sending path

Template Approval Guidelines

Review Before Submission

Check the purpose, variable examples, category and intended recipient. These checks do not guarantee Meta approval.

Inspect Refusals and Current Status

A submission may remain pending or be refused. Recheck the actual status instead of treating a saved example as approved.

Illustrative Marketing Copy, Not an Approved Template

Header: ๐ŸŽ‰ Special Offer Just for You!

Body:
Hi {{1}},

Great news! Get {{2}}% off on your next purchase at {{3}}.

This exclusive offer is valid until {{4}}.

Shop now and save big!

Footer: Reply STOP to unsubscribe

Buttons:
- Shop Now [URL: https://yourstore.com/offer]
- View Terms [URL: https://yourstore.com/terms]

Template Variables Best Practices

Use Variables For:

  • Customer names
  • Order numbers
  • Dates and times
  • Product names
  • Discount amounts
  • Tracking links

Match Variables to the Sending Path:

Numbered placeholders are valid. The public WhatsApp send API fills positional body and text-header values; it refuses named placeholders and templates whose location or dynamic button values that request cannot fill. Automation text values use the recorded header_n and body_n keys. Use the Templates guide and Messages guide, not a label in a copy example, to configure those inputs.

Provider positional placeholders: {{1}}, {{2}}, {{3}}
Oblic automation keys: header_1, body_1, body_2

Opt-in and Compliance

Review Provider Permission

Review the WhatsApp Business Messaging Policy for the connected product and message use case. Your policy owner must assess applicable permissions and notices; this guide does not prescribe one universally valid collection method or certify that a particular checkbox satisfies Meta's policy or local law.

Collection Review Questions:

Which sender and message purposes were described?
Where is the person's choice recorded?
How can that person change the choice?
Who reviewed the applicable provider and legal requirements?

Opt-in Best Practices

The following examples are proposed disclosure text, not approved legal wording or an implemented collection/confirmation flow in Oblic. Review them with your policy owner and verify the actual recording and reply path before use.

Example Website Opt-in:

<form>
  <label>
    <input type="checkbox" name="whatsapp_opt_in" required>
    โ˜ I agree to receive promotional messages from [Company] 
    on WhatsApp. Message frequency varies. 
    <a href="/privacy">Privacy Policy</a>
  </label>
  
  <input type="tel" name="phone" placeholder="WhatsApp Number" required>
  
  <button type="submit">Subscribe</button>
</form>

Double Opt-in Confirmation:

Hi [Name]! ๐Ÿ‘‹

Thanks for subscribing to [Company] on WhatsApp.

Reply YES to confirm and start receiving:
โœ… Exclusive offers
โœ… Order updates
โœ… New arrivals

Reply STOP anytime to unsubscribe.

Managing Opt-outs

Recorded Opt-out Behavior in Oblic:

  • With the inbound webhook consumer running, a standalone STOP, STOPALL, STOP ALL, UNSUBSCRIBE, OPT OUT, OPTOUT or STOP PROMOTIONS records an account-level marketing opt-out. Case, spacing and punctuation are normalized; a sentence that merely contains a keyword is not the same request.
  • CANCEL, END and QUIT are not marketing opt-out keywords in this implementation. Do not advertise them as such.
  • The handler also processes the supported stop-promotions reply and Meta's 131050 marketing-refusal status. A quality-rating change or an inferred block is not, by itself, evidence that Oblic recorded an opt-out.
  • Marketing sends check recorded opt-outs before queuing and again when sending. This is not a claim that every kind of message is suppressed, that an opt-out creates a free-form reply window, or that an acknowledgment is sent automatically.

Opt-out Message Example:

This is illustrative acknowledgment copy, not an automatic reply. Confirm the processing result before telling a recipient that a request was recorded. Writing Reply STOP in a footer does not itself configure or verify the webhook and consumer.

We're sorry to see you go! ๐Ÿ˜ข

You've been unsubscribed from [Company] WhatsApp messages.

You can re-subscribe anytime at [website.com]

Have a great day!

Best Practices:

  • Verify that the configured consumer recorded the request and that marketing sends enforce it.
  • Have your policy owner review acknowledgment wording, retention and access to preference records.
  • Do not infer a universal processing deadline, permanent-retention duty or transactional-message exemption from this guide.

Content Guidelines

Writing Effective Messages

Tone and Voice:

  • Conversational and friendly
  • Professional but approachable
  • Use emojis sparingly (1-2 per message)
  • Match your brand personality

Message Length:

  • Keep messages concise (2-3 sentences ideal)
  • Break long messages into multiple sends
  • Use bullet points for lists
  • Mobile-friendly formatting

Personalization:

Generic: "Hello customer, check out our new products!"

Better: "Hi Sarah! ๐Ÿ‘‹ We just launched 3 new products 
you might love based on your recent purchases."

Best: "Hi Sarah! ๐Ÿ‘‹ Remember those red sneakers you 
viewed last week? They're now 30% off โ€“ just for you! 
Only 2 pairs left in your size."

Timing and Frequency

Choose timing from the recipient's expectations, location, message purpose and your own observed results. There is no universal best-hour table, weekly message count or support-response deadline established by this guide.

Review campaign schedules and workflow actions together. Check the timezone shown by the scheduling screen and verify the resulting date and time before activation; do not assume that it schedules separately in every recipient's timezone. There is no automatic global cross-channel spacing guarantee.

Coordinate volume across teams and channels. Review complaints, opt-outs and failed sends before expanding. Applicable timing or quiet-hour requirements are a separate policy question, not a property proved by saving a schedule.

Rich Media Best Practices

Images:

  • Use the format and size accepted by the chosen upload, template and sending path.
  • Include text overlay for context
  • Ensure mobile readability

Videos:

  • Keep the content concise and check the current accepted format and size.
  • Include captions (many watch without sound)
  • Vertical or square for mobile

Documents:

  • Check the accepted document type and size instead of assuming that every file accepted by an upload can be sent by a template.
  • Name files descriptively
  • Include page numbers
  • Use for: Catalogs, menus, invoices, tickets

Location Sharing:

A location can be useful message content, but a platform feature is not proof that a particular Oblic send path can fill it. The public send API refuses location headers; an automation step cannot fill a location value either. Use a supported template or link rather than assuming the configuration will be completed at send time.

Interactive Features

Quick Reply Buttons

Best Use Cases:

  • Customer preference collection
  • Survey responses
  • Appointment scheduling
  • Product selection
  • Support ticket categorization

Example:

Hi! How can we help you today?

Select an option:
[Order Status] [Product Inquiry] [Speak to Agent]

Button Best Practices:

  • Check the current limits for the particular template or interactive message.
  • Use short, unambiguous labels.
  • Action-oriented labels
  • Logical order (most common first)

Call-to-Action Buttons

URL Buttons:

Check out our summer collection! ๐ŸŒž

[Shop Now] โ†’ https://store.com/summer

Ends midnight tonight! โฐ

Phone Buttons:

Need immediate assistance?

Our team is ready to help!

[Call Us Now] โ†’ +91-XXX-XXX-XXXX

Available 9 AM - 6 PM

Button Guidelines:

  • Use specific action verbs
  • Set clear expectations
  • Track button clicks
  • Test all links before sending

Check whether a button is static or needs a value at send time. The public API refuses templates with dynamic button values that its request cannot provide; an automation step also refuses unfillable button values. A visible button in a template preview is not proof that the chosen send can fill it.

Lists and Forms (Advanced)

Distinguish Meta's platform features from the bot configuration implemented in Oblic. The bot question step sends text or its configured reply buttons and waits for an answer. That is not proof of a ready-to-use catalog, booking system, payment flow or embedded form.

Before designing a list or form interaction, verify that the selected integration exposes it, that the receiving system processes the answer, and that failures have an operator path. Do not infer support from an illustrative menu in this guide.

Automation Strategies

Welcome Messages

First Message Best Practices:

Hi {{name}}! ๐Ÿ‘‹

Welcome to {{company}}!

I'm here to help you:
โ€ข Track orders
โ€ข Find products
โ€ข Get support

What can I help with today?

[Browse Products] [Track Order] [Contact Support]

Set Expectations:

  • Response time
  • Available hours
  • What you can help with
  • How to reach a human

Chatbot Integration

Use the nodes and data sources that your configured bot actually has. A contact lookup is not an order, inventory or appointment integration. Recommendations or external lookups need their own supported data and processing; this guide does not establish that those integrations exist.

When to Escalate to Human:

  • Complex issues
  • Complaints or frustration
  • Sales opportunities
  • When the configured flow cannot resolve the request
  • Customer requests human

Chatbot Best Practices:

  • Make it clear it's automated
  • Provide easy escalation option
  • Keep responses concise
  • Use natural language
  • Test thoroughly before launch

Oblic's handover step can open a conversation for an eligible workspace user, where the bot waits for hand-back. Configure that step and its routing explicitly; there is no automatic three-failed-interaction handover rule established by these examples. Human replies still require the customer service window and the configured outbound worker.

Workflow Automation

The following sequences are planning examples, not saved workflows or default timers. Supply the actual events, data, waits and exit conditions before activation; an order example does not connect an order system. See Events for recording events and the runtime prerequisites. Nominal wait times are not provider-delivery deadlines, and disabling a worker or building a backlog can delay processing.

Abandoned Cart Recovery:

Sequence:
1. (1 hour) "You left items in your cart"
2. (24 hours) "Still interested? Free shipping!"
3. (72 hours) "Last chance: 10% off code"

Timing: Stop sequence if purchase completed
Exit: Remove from sequence after 7 days

Order Updates:

Trigger events:
- Order confirmed โ†’ Confirmation message
- Order shipped โ†’ Tracking link
- Out for delivery โ†’ ETA notification  
- Delivered โ†’ Request feedback

Each includes: Order details, next steps, support option

Quality Rating and Best Practices

Understanding Quality Rating

Meta uses its own feedback and quality signals. Review the current account and template information in the provider's tools rather than assuming that an Oblic report exposes every signal or reproduces Meta's rating calculation.

Quality Tiers:

RatingStatusImpact
HighA favorable quality signalContinue checking separate messaging limits and template eligibility
MediumA signal to reviewInvestigate recent audiences, content and provider feedback
LowA signal needing attentionInspect the actual provider restrictions before further sending

Quality Operations Dashboard

WhatsApp's marketing guidance separates number/template quality, messaging limits and outcome monitoring. A favorable quality rating does not remove a messaging limit or guarantee a template is usable. Review those provider signals alongside Oblic's recorded message outcomes before increasing volume; not every provider dashboard field is an Oblic report field.

SignalReviewInvestigate when
Phone number qualityThe current provider-reported stateDrops after a campaign or new source list
Messaging limitHeadroom for planned sendsCampaign size approaches limit
Template qualityApproval, current eligibility and observed outcomesTemplate receives restrictions or adverse feedback
Read rateConsistent by segment and templateSudden drop for one audience or offer
Provider feedbackAvailable feedback and its scopeAdverse feedback clusters around one campaign or acquisition source
Opt-in quality -> Template relevance -> Send frequency -> User feedback -> Quality rating

Maintaining High Quality

โœ“ DO

Send valuable content, respect frequency limits, respond quickly, use approved templates, maintain opt-in records, monitor metrics.

โœ— DON'T

Spam recipients, ignore opt-outs, use misleading content, send without consent, over-message, ignore quality warnings.

Recovering from Low Quality Rating

Action Plan:

  1. Immediate Actions:

    • Pause all marketing campaigns
    • Review recent messages for policy violations
    • Check opt-in sources
    • Clean contact list
  2. Investigation:

    • Identify high block/report sources
    • Analyze template performance
    • Review message frequency
    • Check for content issues
  3. Improvements:

    • Update templates with clearer value
    • Reduce send frequency
    • Improve opt-in process
    • Segment audience better
    • Enhance personalization
  4. Monitoring:

    • Check quality rating daily
    • Track metrics closely
    • Gradually resume sending
    • Test with small segments first

Scaling Safely

StageAudienceSend behavior
ValidateInternal testers and recent opt-insConfirm template variables, links, and reply handling
PilotSmall, high-intent segmentWatch read rate, replies, blocks, and opt-outs
ExpandSimilar segments with clear consentIncrease gradually and keep frequency capped
OperateFull eligible audienceMonitor quality rating and template health continuously

Use Case Strategies

E-commerce

Product Launches:

๐Ÿš€ NEW ARRIVAL ALERT! 

Hi {{name}}, 

The {{product}} you wishlisted is now available!

โœจ Features: {{features}}
๐Ÿ’ฐ Price: {{price}} (Launch offer: 20% off)
๐Ÿ“ฆ Free shipping on orders over โ‚น500

[Shop Now] [View Details]

Limited stock โ€“ order today! ๐Ÿƒโ€โ™‚๏ธ

Order Confirmations:

โœ… Order Confirmed!

Hi {{name}},

Thanks for your order #{{order_id}}!

๐Ÿ“ฆ Items: {{items}}
๐Ÿ’ณ Total: {{total}}
๐Ÿšš Estimated delivery: {{date}}

[Track Order] [View Details]

Questions? Reply to this message anytime!

Service Businesses

Appointment Reminders:

๐Ÿ“… Appointment Reminder

Hi {{name}},

Your {{service}} appointment is confirmed:

๐Ÿ“ Location: {{address}}
๐Ÿ• Date & Time: {{datetime}}
๐Ÿ‘จโ€โš•๏ธ With: {{provider}}

Need to reschedule?
[Reschedule] [Cancel] [Add to Calendar]

See you soon! ๐Ÿ‘‹

Service Updates:

๐Ÿ”ง Service Update

Hi {{name}},

Your {{service}} is now {{status}}!

โœ… Work completed: {{details}}
๐Ÿ’ฐ Amount due: {{amount}}
๐Ÿ“ธ Before/After photos attached

[Make Payment] [View Invoice] [Leave Review]

Thanks for choosing us! ๐Ÿ™

Customer Support

Support Ticket Updates:

๐ŸŽซ Ticket #{{ticket_id}} Update

Hi {{name}},

Status: {{status}}
Priority: {{priority}}

Latest update:
"{{update_message}}"

โฑ๏ธ Expected resolution: {{eta}}

[View Ticket] [Add Details] [Speak to Agent]

We're on it! ๐Ÿ’ช

Compliance and Regulations

EU Data Protection Reference

Use the EDPB data-protection guide and the relevant authority's guidance for your data use. Your policy or legal owner determines the applicable requirements; this section supplies neither a universal lawful basis nor a breach-notification deadline.

Illustrative Choice Text:

Proposed copy only: review both the wording and the actual withdrawal process. Recording an Oblic marketing opt-out is not proof that every data-rights request has been handled.

By providing your WhatsApp number and checking this box, 
you explicitly consent to receive promotional messages 
from [Company] via WhatsApp.

โ˜ I agree to receive WhatsApp messages

You can withdraw consent anytime by replying STOP.
See our [Privacy Policy] for how we handle your data.

India Data Protection Reference

Use the MeitY data-protection framework as an official starting point for the applicable legislation, rules and notifications. Have your policy owner assess their scope and commencement rather than treating this guide as a current legal checklist.

Meta Policy References

Review Meta's Business Messaging Policy, including its commerce and regulated-vertical guidance, for the product, market and use case. This guide does not maintain a fixed prohibited/restricted-content list. An approved message template does not itself establish permission to operate in a regulated category or satisfy applicable law.

Analytics and Optimization

Key Metrics to Track

Delivery Metrics:

  • Messages sent
  • Recorded deliveries and their denominator
  • Failed deliveries
  • Time to deliver

Engagement Metrics:

  • Recorded reads where available, distinct from delivery
  • Recorded replies, using a clearly defined denominator
  • Click-through rate on links/buttons
  • Conversation rate (user-initiated replies)

Quality Metrics:

  • Provider-reported blocks or reports where available
  • Current account and template quality information
  • Template approval rate

Business Metrics:

  • Conversion rate
  • Revenue per message
  • Customer acquisition cost
  • Customer lifetime value
  • ROI

These business metrics need their own data and attribution method. Oblic's messaging reports do not by themselves establish a purchase, attributed revenue or a return on spend. Compare equivalent audiences and observation periods; this guide supplies no universal delivery, read, reply or complaint target.

A/B Testing

Test Variables:

  • Message timing
  • Content length
  • Emoji usage
  • CTA button text
  • Image vs video
  • Personalization level

Testing Process:

  1. Define hypothesis
  2. Choose comparable audiences and a sample appropriate to the question
  3. Test one variable at a time
  4. Choose an observation period before comparing outcomes
  5. Analyze results
  6. Review uncertainty before changing the campaign

This is an experiment-planning outline, not a guarantee of statistical significance or a built-in automated winner-selection feature. Inspect the available reports and document how the comparison was made.

Research And Reference Table

ReferenceApply this in Oblic
WhatsApp Best Practices for Marketing MessagesMonitor quality rating, messaging limits, template metrics, read rate, and block reasons
WhatsApp Business adaptation studyKeep workflows understandable for small teams moving from personal WhatsApp habits to formal business messaging
CTIA Messaging Principles (2017)Historical industry guidance, not a statute or proof of current provider requirements
Dark Patterns in the Opt-Out ProcessMake withdrawal of consent easy and avoid confusing preference flows

Template Review Checklist

  • Category matches the actual message purpose.
  • Variables are clear when rendered with real data.
  • Header media is readable on mobile.
  • CTA buttons are specific and tested.
  • Opt-out language exists for promotional messages.
  • Message frequency matches the expectation set at opt-in.
  • A human support path exists when the conversation needs escalation.

Next Steps

Was this page helpful?