NetWebMedia does not answer the phone. Every client conversation — from first inquiry to invoice — runs through WhatsApp automation. This playbook is the exact system we use and deploy for clients across the US and Chile. By the end you will have a fully automated WhatsApp operation: welcome flows, sales sequences, service bots, broadcast campaigns, and a CRM that never misses a follow-up.
8 Modules — Table of Contents
WhatsApp Business API — Setup & Configuration
The infrastructure layer. Get this right once and everything else stacks on top correctly.
1.1 — Business Account vs. Business API: Choosing the Right Tier
WhatsApp offers three tiers: Consumer App (personal), WhatsApp Business App (small business, manual), and WhatsApp Business API (automation-grade). Only the API enables automated messaging, webhooks, chatbot integration, and broadcast at scale. Any business sending more than 50 conversations per day needs the API. Any business that never wants to manually reply needs the API.
The API is accessed through a Business Solution Provider (BSP). Top BSPs: Twilio, 360dialog, Meta directly (Cloud API), Vonage, and MessageBird. Meta's Cloud API is the cheapest option (hosting is free) but requires more technical setup. 360dialog is the fastest to go live — 24–48 hours from application to approval.
The WAVE Criteria
Webhook reliability | API cost per message | Velocity to live | Ecosystem integrations. Score each BSP 1–5 on all four. Highest total wins.
Action Checklist — 1.1
- Create a Meta Business Manager account at business.facebook.com
- Verify your business (upload government docs)
- Select BSP and create a WABA (WhatsApp Business Account)
- Register a dedicated phone number (cannot be used on any WhatsApp app)
- Complete phone number verification via SMS or voice call
1.2 — Webhook Configuration & Message Routing
Webhooks are the nervous system of your WhatsApp automation. Every inbound message, delivery receipt, read receipt, and template status update fires a webhook POST to your server. Your webhook endpoint receives JSON payloads and routes them to the right handler: new lead → CRM, existing contact → context lookup, support keyword → ticket creation.
Your webhook must respond with HTTP 200 within 20 seconds or Meta marks the delivery as failed and retries. Use a queue system (Redis, SQS) to acknowledge the webhook instantly and process asynchronously. Never do database writes or AI calls inside the synchronous webhook handler.
Action Checklist — 1.2
- Deploy webhook endpoint on HTTPS (required by Meta)
- Implement webhook verification token challenge
- Set up message queue to decouple receive from process
- Configure dead-letter queue for failed webhook deliveries
- Test with Meta's webhook tester in Developer Console
1.3 — Session Windows, Conversation Types & Pricing
Meta's pricing model is based on conversation windows, not individual messages. A conversation window opens for 24 hours when either party sends a message. Within that window, you can send unlimited messages at no extra charge. Outside the window, you must use a pre-approved message template to re-initiate. Understanding this drives your entire automation strategy.
There are four conversation categories: Marketing (promotional), Utility (transactional), Authentication (OTPs), and Service (customer-initiated support). Marketing conversations cost the most. Service conversations (when the user messages first) cost the least. Your system should detect service-initiated sessions and pivot to that lower-cost category automatically.
OPEN → EXTEND → CLOSE
OPEN the window with a template. EXTEND it by triggering a user reply within the first hour (question, CTA, or interactive button). CLOSE with a satisfaction message or next-step confirmation. Never let a window expire without capturing a reply — that's a wasted conversation slot.
1.4 — Phone Number Health & Quality Rating
WhatsApp assigns each phone number a quality rating: Green (high), Yellow (medium), Red (low). Low quality triggers message sending limits — as low as 250 conversations/day. Quality is determined by user feedback: blocks, reports, and unanswered messages. A spammy broadcast campaign can destroy a number's health in 48 hours.
Protect your number: warm it up gradually (start at 250/day, increase 2× weekly), only send to opted-in contacts, maintain a 95%+ response rate on service conversations, and monitor the quality dashboard daily for the first 60 days.
Action Checklist — 1.4
- Monitor Quality Rating in WhatsApp Manager dashboard daily
- Set up alert when rating drops below Green
- Implement warm-up schedule: 250 → 500 → 1k → 2k → 10k over 6 weeks
- Never send to un-opted contacts regardless of list source
- Review block/report rate weekly — above 0.3% means your messaging needs adjustment
Message Template Library — Building Your HSM Arsenal
Pre-approved templates are the keys to the kingdom. Build your library before you need it — approval takes 24–72 hours.
2.1 — Template Categories, Components & Approval Rules
HSM (Highly Structured Messages) have four components: Header (text, image, video, or document), Body (main message, max 1024 chars), Footer (short disclaimer or context), and Buttons (up to 3 — Quick Reply or Call-to-Action). Not all components are required. At minimum, every template needs a Body.
Meta rejects templates that are too promotional in Utility/Authentication categories, contain personal data collection without disclosure, use vague variables (e.g., {{1}} with no context), or mimic messages that could constitute phishing. Write templates with explicit variable descriptions in the submission form.
Category → Action → Text → Submit
Define the Category first (Marketing/Utility/Auth/Service). Define the Action the template triggers (book call, confirm order, reset password). Write the Text. Submit with explicit variable descriptions. Approval rate goes from ~70% to ~95% with this sequence.
2.2 — Core Template Library (30 Essential Templates)
Every automated WhatsApp operation needs at minimum 30 pre-approved templates across five categories. Below are the most critical with exact copy.
Welcome & Onboarding Automation
The first 24 hours after contact determines 80% of conversion probability. Automate them perfectly.
3.1 — The 5-Message Welcome Sequence
Every new contact gets an automated 5-message welcome sequence delivered over 30 minutes. The sequence is designed to: establish trust, deliver immediate value, qualify the lead, capture intent, and book a next step. All five messages are pre-approved templates sent automatically — no human involvement.
Start · Educate · Reveal · Validate · Execute
Message 1: Start — welcome + what happens next. Message 2: Educate — one insight relevant to their business. Message 3: Reveal — your main offer/differentiator. Message 4: Validate — proof (result, stat, or case study). Message 5: Execute — clear CTA with two options.
Action Checklist — Welcome Sequence
- Pre-approve all 5 templates in WhatsApp Manager
- Set up trigger: new contact in CRM → start sequence
- Configure delay timers (0, 8, 15, 22, 30 minutes)
- Add reply-detection: if contact replies before MSG 5, branch to qualification flow
- Add opt-out handling: STOP/UNSUBSCRIBE → remove from sequence immediately
3.2 — Opt-In Capture & Double Consent Flow
WhatsApp requires explicit opt-in before you can send template messages. Your opt-in must clearly state: what type of messages they'll receive, your brand name, and how to opt out. Capture opt-in at every touchpoint: website forms, QR codes, ad CTAs, link-in-bio, SMS keywords.
Sales Funnel Automation
From first reply to signed contract — fully automated. The CLOSE system converts without a salesperson.
4.1 — Lead Qualification Flow (BANT via WhatsApp)
Qualifying leads via WhatsApp feels natural when done conversationally. Instead of a form, the bot asks questions over 3–5 messages, scoring the lead in the background. By message 5, the CRM has a complete lead score and the bot routes accordingly: high score → immediate proposal, medium → nurture sequence, low → content newsletter.
4.2 — Objection Handling Automation
The four most common sales objections — price, timing, trust, and authority — can all be handled automatically via WhatsApp keyword detection. When the bot detects an objection keyword, it routes to the appropriate handling sequence. Each sequence is 2–3 messages max, ends with a new CTA, and logs the objection type in the CRM for future optimization.
Customer Service Automation
Handle 90% of support conversations without any human involvement. The 3-STRIKE system resolves most tickets in under 2 minutes.
5.1 — FAQ Auto-Resolution System
Build a tiered FAQ library: Tier 1 (instant auto-reply, covers 70% of questions), Tier 2 (needs context lookup, covers 20%), Tier 3 (escalate to human, covers 10%). Your WhatsApp bot detects the question intent, checks the tier, and either answers immediately or routes to the correct handler. The 3-STRIKE rule: if the bot fails to resolve after 3 attempts, it creates a ticket automatically.
5.2 — Status Updates & Proactive Notifications
The best customer service is proactive — telling clients what's happening before they ask. Set up automated status messages triggered by CRM events: when a report is ready, when a campaign goes live, when a billing date approaches, when a milestone is hit. Proactive messaging reduces inbound support tickets by 40–60%.
Broadcast Campaigns & Re-engagement
Mass messaging done right: segmented, timed, tested, and compliant.
6.1 — Segmentation Strategy Before Every Broadcast
Never broadcast to your entire list. Segment by: industry, location, lead score, pipeline stage, last interaction date, language (EN/ES), and subscription tier. A correctly segmented broadcast to 200 people outperforms an unsegmented blast to 2,000 every time — lower block rate, higher response rate, better WhatsApp quality score.
Stage · Language · Industry · City · Engagement-date
Run every broadcast list through all 5 SLICE filters. Minimum segment size: 50 contacts. Maximum broadcast frequency to any segment: 2× per week. Always A/B test message copy before full send (test on 10% of segment, wait 2 hours, send winner to remaining 90%).
6.2 — Optimal Send Times by Market
WhatsApp open rates vary dramatically by time and day. For US markets, highest open rates are Tuesday–Thursday between 10am–12pm local time. For Chile/LATAM markets, peak engagement is Tuesday–Thursday between 7pm–9pm local time. Never send broadcasts on Sunday or Monday — lowest engagement, highest unsubscribe.
CRM Integration & Contact Intelligence
Every WhatsApp conversation creates data. Wire it to your CRM and nothing falls through the cracks.
7.1 — Tagging Logic & Pipeline Automation
Design a tagging taxonomy before connecting WhatsApp to your CRM. Every inbound message should trigger at least one CRM tag. Tags drive pipeline stages, which drive automation triggers. A contact who replies "YES" to a proposal message should automatically move to "Proposal Accepted" stage, trigger a contract send, and schedule a 48-hour follow-up — all without human input.
Every tag triggers a stage. Every stage triggers an action.
7.2 — Conversation History & Context Passing
When a contact sends a new message 48 hours after their last interaction, your bot must recall context — otherwise it re-asks questions the contact already answered. Store conversation state in your CRM: last intent, last qualification answers, current pipeline stage, and last message sent. Pass this context to your bot on every new session open.
Action Checklist — CRM Integration
- Map every WhatsApp event to a CRM field (reply, read, button click, opt-out)
- Store conversation state with TTL of 72 hours minimum
- Configure pipeline stage webhooks: stage change → WhatsApp template fire
- Set up contact deduplication: match by phone number first, email second
- Build a "VIP contact" rule: clients on active plan → skip bot, route to priority queue
Analytics, Optimization & Scaling to 10k+
Measure, improve, and grow — the operating rhythm for a WhatsApp system that compounds over time.
8.1 — The 6 KPIs Every WhatsApp Operation Must Track
8.2 — Monthly Optimization Cadence
Run this exact review every 30 days. It takes 2 hours and compounds — each month the system gets measurably better. Focus on the lowest-performing template first. Rewrite one variable, re-approve, test for 7 days. Never change more than one variable at a time.
Performance → Root cause → Iteration → Split-test → Measure
Step 1: Pull all 6 KPIs. Step 2: Identify lowest performer. Step 3: Hypothesize one change. Step 4: A/B test new vs. old (50/50 split, min 100 conversations). Step 5: Declare winner after 7 days, retire loser. Repeat each month — at month 6, most clients see 2–3× improvement in reply rate.
Monthly Optimization Checklist
- Export KPI report from WhatsApp Manager + CRM
- Identify the one template with lowest open or reply rate
- Write variant B (change subject line, opening line, or CTA only)
- Submit variant B for template approval
- Run A/B split for 7 days (min 100 sends per variant)
- Declare winner, archive loser, update master template library
- Review quality rating — if Yellow, pause broadcasts for 48 hours
8.3 — Scaling from 500 to 10,000 Contacts
Scaling WhatsApp is not just adding contacts — it's building systems that don't break. At 500 contacts, manual tagging is fine. At 5,000, you need automated tagging rules. At 10,000, you need a dedicated WhatsApp phone number per market segment (US vs. Chile), separate sending schedules, and a quality monitoring dashboard that alerts you before problems become crises.
Ready to Automate Your WhatsApp?
NetWebMedia sets up your full WhatsApp automation system — from API connection to your first 1,000 automated conversations — in 14 days.
✉️ Email Us →