Permission & opt-outs
Record real permission, process withdrawals and avoid repeatedly checking thousands of contacts by hand.
Keep the decision, date, source and evidence together. Use a bulk record only when the same evidence actually covers the selected people.
Understand a WhatsApp permission record
Know what the record represents and what it cannot certify.
Record permission received from a customer
Store an agreement that already exists rather than creating it through a checkbox.
Record a withdrawal correctly
Make a customer's stop request visible to future outreach decisions.
Choose the correct permission decision
Prevent a reversed selection from making a confirmed customer appear withdrawn.
Write a useful permission source
Make the origin understandable to another authorised operator.
Add a permission evidence reference
Keep a findable reference without copying excessive personal information.
Use an accurate permission date
Record when the agreement or withdrawal happened rather than when a list was uploaded.
Update permission for a selected group
Use one bulk operation when the same evidence applies to every selected person.
Import permission alongside contact data
Preserve row-specific decisions and evidence during data preparation.
Handle contacts without permission evidence
Keep uncertain records visible without manufacturing an affirmative history.
Understand permission and campaign eligibility
Trace the connection between contact state and campaign selection.
Investigate an unconfirmed contact after an update
Check the actual stored decision before assuming the save failed.
Correct an incorrectly recorded decision
Repair the history with a truthful new record and an explanation.
Respect opt-outs received outside WhatsApp
Bring a relevant email, phone or support request into the workspace decision.
Separate service requests from promotional permission
Keep a requested transaction distinct from a broader marketing programme.
Prepare a permission collection message
Make the requested communication and customer choice understandable.
Use a permission collection link
Guide customers through the available collection route and inspect the resulting record.
Recheck permission before a new purpose
Review whether existing evidence covers the proposed change in communication.
Explain permission to a client team
Make the recordkeeping process practical without presenting it as a provider verification service.
Audit a sample of permission records
Check that stored decisions can be traced to real evidence.
Handle contradictory permission evidence
Resolve conflicting records with the customer's latest verified instruction in view.
Keep permission references private
Make evidence usable to authorised staff without publishing customer information.
Refresh permission changes across devices
Confirm that web and mobile are showing the latest saved state.
Handle a partially completed bulk update
Review protected or rejected records instead of assuming every selected contact changed.
Create a permission maintenance process
Make real customer choices part of routine contact management.
Relevant public sources
- WhatsApp Business Messaging PolicyProvider policy
- Alactic Communications Terms & ConditionsAlactic public terms