Meta WhatsApp Business Verification Worksheet

A single-page reference for completing Meta WABA verification for NetWebMedia. Fields with fixed values are pre-filled and shouldn't change. Editable inputs are placeholders Carlos fills before submitting to Meta. Internal use only

1Business Information

Meta verifies these against your business registration documents. They must match exactly — even punctuation. The "Display Name" must align with the legal name (Meta enforces a similarity rule).

Legal Business Name
Display Name (WABA-facing)
Doing Business As (DBA)
Business Type
Country of Registration
Business Registration Number
Business Category
Year Founded

2Contact Information

Meta uses these for follow-up correspondence and the public-facing WhatsApp Business profile.

Business Address (line 1)
Business Address (line 2)
City
State / Region
Postal Code
Country
Business Email
Business Phone (Twilio purchased)
Business Website

3WhatsApp Business Profile (public-facing)

This is what users see when they open a chat with us. Meta reviews it for guideline compliance.

Profile Display Name
About (148 char max)
Profile Photo
Business Description (longer)
Industry
Business Hours (America/Santiago)

4Documents Meta Will Request

Upload one of these as proof of business legitimacy. Meta reviews within 1–7 business days.

Business registration certificateMost common path. PDF or image. Must show the business name + registration number + issuing authority.

Tax-issued documentRecent tax return / VAT statement / EIN confirmation letter. Must show business name + tax ID.

Utility bill at business addressLast 3 months. Must show business name + business address. Backup option if registration cert is unavailable.

Bank statementLast 3 months. Showing business name + business address. Redact transaction details, leave only header.

5Pre-flight Checklist (before you click Submit)

Tick each item before submitting to Meta. Skipping any of these is the #1 cause of rejection.

Phone number is brand-new for WhatsAppHas never been used for personal WhatsApp. Twilio-purchased numbers always pass this check.

Display Name matches legal name (per Meta similarity rule)Display Name "NetWebMedia" must align with the registered business name. Add LLC/SpA/etc. only if legally required.

Business website is live and matches business namehttps://netwebmedia.com loads cleanly, About page lists Carlos Martinez as Founder, footer references "NetWebMedia".

Business email reachablehello@netwebmedia.com bounces test message back successfully. Meta sometimes pings here mid-review.

Document filename matches business name"NetWebMedia_business_registration.pdf" beats "scan001.pdf" in Meta reviewer trust score.

Business address is consistent across all documentsWorksheet section 2 + uploaded docs + website footer + Twilio billing address all match.

Three message templates submitted for approvalweekly_aeo_insight, niche_specific_audit, campaign_followup — copy in _deploy/social-channel-activation.md §3.5.

6Post-Approval Wiring (10 min)

Once Meta approves, wire the production credentials into NWM. Then run the flush.

From Meta Business Manager → System Users → API keys, copy:
- WA_PHONE_ID (the new verified phone number ID)
- WA_META_TOKEN (system user permanent token)
- WA_META_APP_SECRET (app secret)
Update GitHub Actions secrets in netwebmedia/netwebmedia repo settings.
Trigger a deploy: git commit --allow-empty -m "deploy: WABA verification complete" && git push origin main
Wait ~3 minutes for FTPS to propagate, then test: curl -X GET 'https://netwebmedia.com/crm-vanilla/api/?r=wa_flush&action=count' -H 'X-Auth-Token: <your-admin-token>'
Run a dry flush (no real sends): POST /crm-vanilla/api/?r=wa_flush&action=send with body {"dry_run": true}
If the dry run looks healthy, drop dry_run and run the live flush. Confirmed subscribers graduate from pending_double_opt_in to confirmed automatically.

7Three Message Templates (paste into Meta Business Manager)

Submit these three under "Message Templates" → "Create Template". Category for all three: Utility (not Marketing — utility templates have looser approval rules).

Template 1: `weekly_aeo_insight`

Hi {{1}}, here's this week's AEO insight from NetWebMedia: {{2}} Read the full breakdown: {{3}} Reply STOP to unsubscribe.

Template 2: `niche_specific_audit`

Hi {{1}}, we just published a {{2}}-specific audit. Top 3 findings: {{3}}. Full data + the fixes: {{4}} Reply STOP anytime.

Template 3: `campaign_followup`

Hi {{1}}, quick recap of the {{2}} broadcast: {{3}}. Want a free audit on your site? Reply YES and we'll set one up. Reply STOP to unsubscribe.

Worksheet generated 2026-05-01 — companion to _deploy/social-channel-activation.md §3. The flush handler at /crm-vanilla/api/?r=wa_flush is live as of this deploy and works in dry-run mode immediately. Live sends require the post-approval wiring in §6.