How long does WhatsApp API onboarding take?
Printable WhatsApp API onboarding checklist: Meta verification, phone setup, templates, webhooks, chatbot, integrations, and go-live testing — companion to the full integration guide. 5–14 business days for most SMBs. Verification and template approval are the usual bottlenecks.
Last updated: 6 July 2026
This WhatsApp API onboarding checklist is the printable companion to our WhatsApp API integration guide. Use it during sprint planning, vendor handoffs, and go-live reviews. Each item maps to a production requirement — skipping steps is why webhooks work in test but fail with real messages.
Too long? Start here
- Phase 1 (days 1–3): Meta Business Manager, verification docs, Ominiflow account
- Phase 2 (days 2–5): Phone number, display name, WABA connection
- Phase 3 (parallel): Template creation and submission — start early
- Phase 4 (days 5–10): Inbox, chatbot, integrations (Zoho/Shopify/webhooks)
- Phase 5 (days 10–14): Internal test → 50-contact pilot → production launch
Phase 1: Meta Business setup
- ☐ Create or access Meta Business Manager (admin role)
- ☐ Legal business name matches GST / incorporation certificate
- ☐ Business address matches verification documents
- ☐ Website live with privacy policy and contact page
- ☐ Submit business verification (GST cert, utility bill, or MCA docs for India)
- ☐ Assign team members with correct BM permissions (avoid single-person lockout)
- ☐ Enable two-factor authentication on all admin accounts
Deep dive: How to Get WhatsApp API (Step-by-Step Setup Guide)
Phase 2: Phone number and WABA
- ☐ Select dedicated business number (not personal WhatsApp active)
- ☐ Register Ominiflow trial — start here
- ☐ Connect Facebook OAuth to Business Manager
- ☐ Create or select WhatsApp Business Account (WABA)
- ☐ Verify number via SMS or voice OTP
- ☐ Submit display name — must match brand (approval 1–3 days)
- ☐ Confirm phone status = CONNECTED in Business Manager
- ☐ Subscribe WABA to app:
POST /{WABA_ID}/subscribed_apps
Common mistake: deleting personal WhatsApp before migration plan — see 5 common mistakes.
Phase 3: Message templates
- ☐ List every outbound trigger (order confirm, OTP, cart recovery, etc.)
- ☐ Assign correct category: utility, marketing, authentication, service
- ☐ Draft body copy with
{{1}},{{2}}placeholders - ☐ Submit templates in Ominiflow + Meta Business Manager
- ☐ Wait for approval (15 min – 48 hours per template)
- ☐ Document approved template names + language codes for dev team
- ☐ Test variable mapping — count mismatch causes error #132000
Reference: Template message API guide
Phase 4: Platform configuration
- ☐ Configure team inbox — agents, roles, assignment rules
- ☐ Build first chatbot flow (FAQ or lead qual) — no-code guide
- ☐ Configure human handoff — fallback after 2 unrecognized messages
- ☐ Set up opt-in capture (checkout checkbox, QR, click-to-WhatsApp ad)
- ☐ Tag contacts by consent source and date
- ☐ Enable agent notifications (browser + mobile)
Phase 5: Integrations
Pick your pattern from the integration guide:
- ☐ CRM: Zoho OAuth connect, field mapping, deal-stage triggers
- ☐ E-commerce: Shopify connect, order webhooks, cart recovery
- ☐ Payments: Razorpay webhook → payment link templates
- ☐ Helpdesk: Freshdesk ticket sync
- ☐ Custom: HTTPS webhook endpoint, signature verification, async queue
- ☐ iPaaS: Make/Zapier scenario tested with failure alerts
Webhook setup: webhook integration guide
Phase 6: Security and compliance
- ☐ Webhook
X-Hub-Signature-256verification enabled - ☐ Access tokens in secrets manager (not git)
- ☐ PII redaction in production logs
- ☐ Marketing opt-in documented per contact
- ☐ Opt-out keywords configured (STOP, unsubscribe)
- ☐ Quality rating baseline recorded in WhatsApp Manager
Phase 7: Testing and go-live
- ☐ Add 3–5 internal test numbers
- ☐ Test outbound template send — all variables populated
- ☐ Test inbound message → webhook → CRM/inbox update
- ☐ Test agent reply within 24-hour window
- ☐ Test chatbot all branches — no dead ends
- ☐ Test agent handoff — response within 30 seconds
- ☐ Pilot broadcast: 50–100 opted-in contacts only
- ☐ Monitor delivery rate, block signals, quality rating for 48 hours
- ☐ Full launch with warm-up schedule for volume ramp
Typical timeline by team type
| Team profile | Onboarding duration |
|---|---|
| SMB, Zoho + basic bot | 5–7 business days |
| D2C Shopify, 4 templates | 7–10 business days |
| Custom ERP webhooks | 2–4 weeks |
| Enterprise multi-number | 3–6 weeks |
FAQ
How long does WhatsApp API onboarding take? expand_more
5–14 business days for most SMBs. Business verification and template approval are the usual bottlenecks — start both on day one.
What documents do I need for Meta verification in India? expand_more
GST certificate, MCA incorporation docs, or utility bill matching business address. Legal name must match across documents and website.
Can I go live without approved templates? expand_more
You can receive inbound messages and reply within the 24-hour session window. Any business-initiated outbound (order updates, marketing) requires approved templates.
What is the most common onboarding mistake? expand_more
WABA not subscribed to app via Graph API — dashboard "Test" works but production messages don't trigger webhooks.
Should I use a checklist or the full integration guide? expand_more
Use both. This checklist for sprint tracking; the integration guide for architecture decisions and troubleshooting. How to Get WhatsApp API · Platform overview · Pricing · Compare providers · Get onboarding help Updated July 2026. WhatsApp API onboarding checklist for business and engineering teams.