No checklist can guarantee that a number will never be restricted. WhatsApp can limit or remove access for policy violations, unauthorized scaled messaging, low-quality experience, or significant negative feedback. The defensible goal is a permission-based campaign system that minimizes surprise, honors opt-outs, and stops when quality signals deteriorate.
After this lesson, you can create campaign eligibility, suppression, approval, test, and stop rules based on official policy rather than tricks.
Build an Eligibility Record
Before a contact can enter a campaign, require:
phone_number
consent_status
consent_source
consent_timestamp
consent_scope
expected_message_category
opt_out_status
last_quality_event
WhatsApp policy requires the business to have the person’s number and opt-in permission for subsequent messages or calls. It recommends setting expectations by message category and providing clear opt-out instructions. Buying, scraping, or importing a list is not consent.
Apply Suppression First
Create one authoritative suppression check shared by WATI, CRM, and other senders:
SUPPRESS if opted_out
SUPPRESS if no evidence for this purpose
SUPPRESS if complaint or legal hold requires isolation
SUPPRESS if number is invalid or repeatedly undeliverable
SUPPRESS if frequency cap reached
SUPPRESS if template is not approved/current for the purpose
Sync suppression before audience export and again immediately before send. Treat “stop,” “remove me,” “band kar dein,” and equivalent requests as opt-outs even if they do not match one exact keyword.
Use a Campaign Release Gate
Require an owner to approve:
- purpose, audience rule, and consent scope;
- approved template name/category and rendered sample;
- variables with missing-value behavior;
- send window and frequency cap;
- offer evidence, price, expiry, and terms;
- opt-out path and staffed reply queue;
- small internal test and sample audience;
- stop thresholds for opt-outs, blocks, complaints, errors, or negative replies.
Never use spelling variation, number rotation, device farms, or throttling tricks to bypass enforcement. Those are not reliability practices.
Worked Example
A Karachi bookstore has 1,200 contacts but valid, recorded new-release opt-in for only 340. It sends an approved marketing template to a small initial segment after checking suppression. The message names the store, explains why the person is receiving it, shows the real offer terms, and includes STOP.
The owner watches delivery status where available, replies, purchases, opt-outs, complaints, and inbox capacity. If the predefined negative-feedback or operational threshold is crossed, the campaign pauses automatically for review. The other 860 contacts are not “reactivated” without fresh permission.
Failure Cases to Diagnose
- CSV upload treated as consent: require evidence tied to purpose.
- Opt-out exists only inside WATI: synchronize authoritative suppression everywhere.
- Template approved, so audience assumed legal: template approval does not create consent.
- Campaign continues while inbox is overwhelmed: capacity is part of release readiness.
- Only clicks are measured: include opt-outs, complaints, blocks, and negative replies.
- Restricted product promoted: verify current business and commerce policies.
- Number warming or rotation advice: reject attempts to evade platform controls.
🇵🇰 Pakistan Angle
Consent gathered at a physical shop, event, website, Facebook lead form, or click-to-chat should state the business, message purpose, and opt-out route. Preserve the form/version and timestamp. A handwritten customer register or delivery list should not silently become a nationwide marketing audience.
Schedule for reasonable PKT hours and segment by actual relevance, not stereotypes about city, language, or income. If the offer has city-specific delivery, exclude unsupported areas rather than collecting responses the team cannot fulfill. Use Roman Urdu only after testing meaning and opt-out clarity.
Hands-On Exercise
- Define the campaign eligibility record and suppression rules.
- Audit a sample contact list for evidence by purpose.
- Complete the release gate for one sample campaign.
- Set frequency and quality stop thresholds.
- Test STOP variants and suppression across every sending path.
Done means: no contact can be selected without purpose-specific permission, and one opt-out reliably blocks every future in-scope campaign.
Completion Rubric
- Consent evidence is tied to message purpose.
- Suppression is authoritative across systems.
- Approved template and permitted audience are checked separately.
- Campaigns start with a controlled test segment.
- Quality and capacity thresholds can pause sending.
- No evasion technique is part of the plan.
Sources
Key takeaway: protect the number by protecting the recipient: verifiable permission, relevant purpose, easy universal opt-out, controlled release, and fast response to negative signals.