Get opt-in for WhatsApp | Developer Documentation

Prepare a permitted WhatsApp audience for ChatArchitect

Before a campaign, check why each person expects messages from your business and how they can ask you to stop. A phone number in a CRM, an approved template or an open customer service window does not by itself establish permission for a marketing campaign.

Match permission to the planned communication

For a phone-number campaign, identify people who provided their number and agreed to receive communication from your business. Make the business identity and intended content clear. Meta's opt-in guidance allows permission covering business communications generally when it meets the policy and applicable law. Check that the actual wording and method cover the messages you intend to send.

Use the current WhatsApp Business Messaging Policy when designing the collection process. An order update and a promotional offer have different purposes; permission to provide one service is not automatically permission for unrelated offers. The business is responsible for the applicable notices, permissions and communication rules.

Build a permission record your team can use

Maintain the record in your own business process, such as an appropriately configured CRM or a controlled register. Assign responsibility for checking it before a campaign and for excluding recipients who have withdrawn permission. Check the privacy and retention rules that apply to that record.

For an offer sign-up, an illustrative wording is: “I want to receive offers from [business name] on WhatsApp at the number I provide. I can ask [business name] to stop.” Adapt the process to your actual business, purpose, expectations and required notices; this example is not a field installed by ChatArchitect.

Review the audience before sending

1. Define the campaign's business, purpose and message category. Compare them with the permission records rather than assuming that every saved contact belongs in the audience.
2. Exclude people whose permission is missing, unclear, withdrawn or does not cover that communication. A purchased list, a public phone number or an earlier support question is not evidence of campaign permission.
3. Check recipient selection in every CRM, help desk or automation that will launch the campaign. A correction in one list must also reach the other workflows using that audience.
4. Create and review the appropriate template in wtargeted.com, then follow the campaign checklist. Template approval does not replace the audience check.
5. Test with a person who agreed to receive the test. Inspect the message and the available delivery result before expanding the send.

Act on requests to stop

Provide an understandable way to request withdrawal and check requests received both on WhatsApp and through other contact channels. Record what the person asked to stop and apply that scope to future recipient selection. Follow the policy's contact-list removal requirements and avoid contacting the person again through a different campaign to bypass the request.

Stop launching affected future sends. If messages are already queued in a connected tool, check with its operator or ChatArchitect support which pause or removal action is available and what it affects. Do not assume that changing a contact record cancels a request already accepted for delivery.

Review feedback and template quality when introducing a new collection method or campaign. If a Meta account notice appears, use the account restriction guide. Keep permission evidence available to the responsible team without putting full customer lists or credentials into an ordinary support message.