Outbound Wiki

WhatsApp outreach

Contacting prospects through WhatsApp while managing consent, message expectations and business-account limitations.

Use WhatsApp only after the person has given the business a mobile phone number and agreed to receive later messages or calls.1 High message volume is rarely the cause of a blocked number or poor quality rating.2 Sending to people without clean, provable consent can lead to blocks and reports that cause Meta's systems to throttle the sender.3

Run the work in order

  1. Permission
  2. Scope
  3. Proof
  4. Message
  5. Exit

Complete the permission record before you plan the message. Move to the next stage only when the current one has a clear answer.

Stage What you are trying to learn Example question
Permission whether the person chose to hear from the business Did you actively choose to receive messages from this business?
Scope what the person expects to receive What did the permission say you would receive?
Proof whether you can show how permission was given Where is the record of the action?
Message whether the next message helps the person move forward What answer or resource would help now?
Exit whether future contact remains welcome How can this person stop future messages?

Build permission you can prove

Treat a phone number as contact detail until the permission record is complete. A clean record shows the person's active action, the business name, and a clear statement that the person will receive messages from that business.4

Collect permission where the person can make the choice directly. You can use a website, app, checkout page, SMS reply, or QR code.5 Choose the collection method as long as the permission meets the required conditions.

Keep the record attached to the person and the wording they saw. Meta's rules put the burden of proof on the sender.6 If a complaint arrives, you need to show that the person actively agreed.7 Review data protection law before relying on a permission flow because the platform rule does not replace those obligations.8

Double opt-in adds a confirmation step, and only confirmed contacts are added after that step.910 Use it when the extra confirmation suits the motion. It is recommended as a best practice, while the policy does not require the second confirmation.11

Set expectations at capture

The permission wording sets the boundary for later messages. Write it so the person knows who will contact them and what kind of contact follows.

A current policy update says the permission no longer has to state that delivery will happen specifically through WhatsApp.12 A general opt-in for marketing or service messages, collected on any channel, can satisfy the platform requirement when it meets the stated conditions and local law.13 Keep the wording specific enough for a future reviewer to understand what the person agreed to receive.

Give people a clear way to leave. Users must always be able to opt out or unsubscribe from a business's messages.14 Check current WhatsApp Business documentation before launch because its policies and guidelines can evolve.15

Send something worth answering

Once permission is in place, use the conversation to help the buyer take the next step. The message should earn its place by answering a question, pointing to a resource, or making self-service easier.

Customers want to self-serve, and salespeople should guide them to resources and answer their questions when they arise.16 WhatsApp can guide prospects quickly when it is positioned appropriately for the buyer.17 Keep the response close to the question in front of you, and avoid turning a permissioned thread into a sequence of unrelated pitches.

The conversation gives the recipient direct access to the person handling the exchange, so be ready to answer when the recipient replies. Read status can show whether messages have been opened and read.18 Use it as a visibility signal, then wait for an actual response before treating the conversation as active.

What not to do

The common mistakes are confusing possession of a number with permission and making the exit path hard to use.

  • Do not treat a phone number collected from an order as WhatsApp consent.19
  • Do not use a number that was scraped, purchased, or imported from another platform as proof of consent.20
  • Do not rely on a pre-checked checkbox that a person must undo to decline.21
  • Do not bury consent in Terms of Service acceptance when the wording does not mention the messaging permission.22
  • Do not use generic language such as "subscribe for updates" without naming the business.23
  • Do not create a permission flow that gives people no way to opt out or unsubscribe.14

If the record cannot show the person's action and the business they agreed to hear from, repair the capture point before contacting anyone.

Sources

  1. 1
    “You may only contact people on WhatsApp if two things are true: they have given you their mobile phone number, and you have received opt-in permission confirming they wish to receive subsequent messages or calls from you.”
  2. 2
    “That's rarely the real cause.”
  3. 3
    “The real cause is sending to people who never gave you clean, provable consent in the first place, then getting blocked and reported by enough of them that Meta's systems throttle you.”
  4. 4
    “What can't change is the substance: active action, your business name, clear statement that they'll get WhatsApp messages from you.”
  5. 5
    “You can collect it on any third-party channel — your website, your app, a checkout page, an in-store tablet, an SMS reply, a QR code.”
  6. 6
    “Meta's opt-in rules are not vague. They're written down, they're specific, and they put the entire burden of proof on you, the sender.”
  7. 7
    “If a complaint lands, the question is whether you can show the person actively agreed.”
  8. 8
    “This is a platform rule, though, it doesn't override data protection law.”
  9. 9
    “Double opt-in adds a confirmation step.”
  10. 10
    “After the first action, you send a message asking them to confirm (reply YES, tap a button), and only confirmed contacts get added.”
  11. 11
    “Double opt-in is a best practice, not a Meta requirement.”
  12. 12
    “Update (November 2024): Meta updated the WhatsApp Business Messaging Policy so that an opt-in no longer needs to state that messages will specifically be delivered via WhatsApp.”
  13. 13
    “A general opt-in to receive marketing or service messages from your business, collected on any channel, now satisfies Meta's platform requirement, provided it still meets the requirements above and complies with local law.”
  14. 14
    “Users must always have the ability to opt-out or unsubscribe from receiving messages from a business at any time, should they no longer wish to receive communications.”
  15. 15
    “Before we get into the details, it’s worth noting that WhatsApp's policies and guidelines can and almost certainly will evolve over time; so it's always a good idea to refer to the official WhatsApp Business documentation or contact WhatsApp directly for the latest information regarding opt-in requirements.”
  16. 16
    “The way people want to buy has changed. Customers want to self-serve. But salespeople should still guide prospects to resources and answer questions when they have them.”
  17. 17
    “WhatsApp is a very fast way to do that - if it’s positioned in the right way to the buyer. It fits into this digital buying experience that people seem to prefer.”
  18. 18
    “You can see if they’ve opened and read your message.”
  19. 19
    “"We already have your number from your order, so we'll message you."”
  20. 20
    “A phone number scraped, purchased, or imported from another platform.”
  21. 21
    “A pre-checked checkbox the user has to uncheck to decline.”
  22. 22
    “Consent buried in a Terms of Service acceptance with no mention of WhatsApp.”
  23. 23
    “Generic language like "subscribe for updates" without naming you fails this.”