PEVENDE team ·
WhatsApp Consent: Record Permission and Respect Opt-Outs
Having a phone number in a spreadsheet does not prove permission to message it. Consent must be explainable, and an opt-out request must change both team behavior and automation.
Record evidence
Keep the source, date and scope of permission: for example, a form explaining which messages will be sent. Do not reuse permission for a different purpose without reviewing its scope. Avoid collecting more data than needed.
Separate import and permission
An import may create records for review, but does not authorize a campaign. Contacts without evidence should remain distinguishable. Group membership or receipt of a business card also does not establish promotional messaging permission.
Apply an opt-out
WhatsApp policy requires honoring requests to stop receiving messages. Record the opt-out, exclude the contact from automation and explain which communications stop. Do not erase suppression just to reimport the number.
Test the control
Hypothetical exercise: an authorized contact asks “do not send promotions”. Record the date, stop the relevant automation and verify that the next send excludes the contact. If the scope is unclear, clarify it without continuing the promotion. Check that suppression reaches every system sending messages, not just the CRM. A visible label ignored by the sender does not protect the recipient’s decision. Include this check when changing connectors or importing an updated contact list.
Practical checklist
- Document source, date and scope.
- Preserve opt-outs during import or reassignment.
- Test suppression before enabling sends.
Primary sources
Checked October 2, 2026. Policies and products can change; review the source before implementation.