WhatsApp is Nepal’s default sales channel — from D2C checkout confirmations to B2B quote follow-ups. This playbook covers WhatsApp Business App vs API, broadcast templates, catalog commerce, and CRM workflows that scale without losing the personal touch.

→ WhatsApp Marketing service · WhatsApp dictionary term · Facebook Ads Nepal

WhatsApp Marketing Playbook (2026): Business API, Broadcasts & Sales Workflows for Nepal

Why WhatsApp wins in Nepal

Factor Implication
Mobile-first market 70%+ traffic; messaging beats email open rates
COD + trust gap Pre-delivery confirmation via chat reduces RTO
Relationship selling B2B and high-ticket D2C close on chat + voice
Meta ecosystem Click-to-WhatsApp ads feed directly into Business inbox

WhatsApp Business App vs Cloud API

Feature Business App (free) WhatsApp Business API
Team size 1–4 devices Unlimited agents via BSP
Broadcast limit 256 per list Template-based unlimited (approved)
Automation Quick replies, labels Flows, webhooks, CRM sync
Catalog Yes Yes + dynamic via API
Cost Free Per-conversation pricing via BSP

Start on the App if you are a single-location shop under 500 leads/month. Move to API when you need HubSpot/Zoho sync, multiple agents, or Click-to-WhatsApp ad volume.

Opt-in and compliance

  1. Explicit consent — Checkbox on forms: “Contact me on WhatsApp at [number]”
  2. Template categories — Marketing vs Utility vs Authentication (Meta approval required)
  3. 24-hour window — Free-form replies only within 24h of user message; outside requires approved template
  4. Do not — Buy lists, import contacts without consent, or send promotional templates to cold numbers

Broadcast template examples (Nepal)

Use case Template type Sample opener
Dashain sale Marketing “Dashain offer: 1% off until 2. Reply YES for catalog.”
Order shipped Utility “Your order #1 is out for delivery. Track: 2”
OTP / verification Authentication “1 is your verification code.”
Appointment reminder Utility “Reminder: appointment 1 tomorrow at 2.”

Submit templates in Meta Business Manager → WhatsApp Manager → Message templates.

Click-to-WhatsApp ads workflow

Meta Lead Ad / Traffic Ad (WhatsApp CTA)
  → User opens chat with pre-filled message
  → Agent or bot qualifies (budget, location, product)
  → Catalog link or payment request (eSewa/Khalti/COD confirm)
  → CRM tag: whatsapp_lead_source =

Track with UTM parameters in the ad destination URL and manual CRM tagging until CAPI offline events are configured.

Sales team workflow (5 agents)

Stage Owner Tool
New inquiry Round-robin agent WhatsApp inbox + labels
Qualified Senior closer CRM deal stage update
Quote sent Agent PDF + catalog message
Follow-up D+1, D+3 Automated template BSP scheduler
Won/lost Manager Weekly pipeline review

Labels to use: New, Hot, Waiting payment, COD confirmed, Support, Lost.

Integration stack (Nepal-friendly)

Tool Role
Wati / AiSensy / Interakt BSP for API without heavy DevOps
Zoho CRM / HubSpot Lead sync from WhatsApp
Google Sheets Lightweight tracking for SMBs
Meta Business Suite Ad → WhatsApp attribution

Metrics to track

Metric Target
First response time <5 min business hours
Conversation → qualified lead 25–40% (varies by industry)
Template read rate >80% for utility messages
COD confirmation rate Track messages before dispatch
Cost per WhatsApp conversation Compare vs Meta CPL

Common mistakes

  1. Broadcasting without templates — Account restrictions after policy violations
  2. No CRM handoff — Leads die when agents change shifts
  3. Same message for B2B and D2C — Tone and proof points differ
  4. Ignoring voice follow-up — Many Nepal buyers expect a quick call after chat
  5. No offline conversion upload — Meta can’t optimize Click-to-WhatsApp without closed-won data

WhatsApp Business API vs app (decision tree)

<500 conversations/month → WhatsApp Business app + labels
500–5,000/month → BSP (360dialog, Twilio) + CRM integration
>5,000/month + broadcasts → API + approved templates + opt-in database

Broadcast compliance (Nepal)

  • Opt-in must be explicit (checkbox on form, not pre-ticked)
  • Marketing templates need Meta approval before Dashain bursts
  • Utility templates (order update, appointment) for transactional messages
  • Maintain opt-out keyword (“STOP”) in Nepali and English

Click-to-WhatsApp ads workflow

  1. Meta campaign objective: Messages → WhatsApp
  2. Pre-filled greeting + quick replies (product line, city)
  3. Agent SLA: respond within 15 minutes during business hours
  4. Tag conversations in CRM → upload purchasers to exclusion audiences

Integration with site stack

  • GA4 event whatsapp_click on button taps
  • UTM on wa.me links where possible
  • Offline conversion import when chat leads to sale

Service page: WhatsApp Marketing Nepal