Whatsapp Pro

---
name: whatsapp-pro
description: Use WhatsApp for business — Business app vs. API, broadcast lists, customer support, and compliant messaging.
category: enterprise-communication
---

## Overview

WhatsApp is the dominant messaging app in much of the world — and increasingly a business channel for support, notifications, and sales. This skill covers professional WhatsApp use: Business app vs. Business API, broadcast strategy, customer support workflows, automation via the API, and the compliance rules (opt-ins, templates) that govern business messaging.


WhatsApp is the world's most-used messenger — and increasingly a business platform via the WhatsApp Business API: customer support, notifications, catalogs, and conversational commerce. In many markets it is the primary digital channel, outranking email and web. Mastery means operating within its template/consent rules while exploiting its unmatched open rates.
## When to use

- Setting up WhatsApp for customer support
- Choosing between Business app and API
- Running broadcast campaigns
- Automating WhatsApp notifications
- Designing WhatsApp support workflows
- Navigating WhatsApp business policies

- Customer support in WhatsApp-first markets
- Order notifications and delivery updates
- Conversational commerce and catalogs
- Building WhatsApp chatbots for support
- Running click-to-WhatsApp ad campaigns
- Managing WhatsApp for multi-location businesses
## Core concepts

**App vs. API.** WhatsApp Business app: free, for small teams (labels, quick replies, catalog, away messages) — manual, limited scale. Business API (via providers): automation, chatbots, CRM integration, multi-agent support — required for scale. Choose by volume and automation needs.

**Broadcast lists vs. groups.** Broadcasts: one-to-many where recipients don't see each other (marketing/updates to opted-in contacts). Groups: many-to-many (community, team coordination). For business messaging, broadcasts preserve privacy and professionalism.

**Template messages.** API-initiated business conversations outside the 24-hour window require pre-approved templates (utility, marketing, authentication categories). Write templates that get approved: clear purpose, no marketing fluff in utility templates, correct variables. Rejections waste days — follow the guidelines.

**The 24-hour window.** Free-form messaging allowed within 24 hours of the user's last message; outside it, templates only. Design flows to stay useful within the window and to re-engage compliantly after.

**Support workflows.** WhatsApp as a support channel: quick replies for FAQs, chatbot triage → human handoff, rich media (photos of issues, voice notes for complexity), and CRM logging. Response-time SLAs matter — WhatsApp feels instant; slow replies frustrate more than email delays.

**Compliance.** Opt-in required for business-initiated messages (document it), easy opt-out, WhatsApp's commerce and business policies (prohibited categories), and regional regulations (GDPR, etc.). Policy violations risk number bans — hard to reverse.


**The 24-hour window.** Businesses can message freely within 24 hours of the customer's last message; outside the window, only pre-approved template messages are allowed. Design conversation flows that capture what you need within the window, and use templates strategically for re-engagement (order updates, appointment reminders, back-in-stock).

**Template rules.** Marketing and utility templates require approval (Meta reviews content); templates must match their category; parameters personalize (name, order ID) but the structure is fixed. Build a template library covering your top 20 proactive use cases — approval takes days, so plan ahead.

**Commerce features.** Catalogs (product browsing in-chat), carts, and payment integrations (market-dependent) enable full purchase flows without leaving WhatsApp. In high-adoption markets, WhatsApp storefronts outperform mobile web on conversion — meet customers where they already are.

**Chatbot design for WhatsApp.** Button-based flows (lists, reply buttons) outperform free-text for most use cases.
Keep conversations short — WhatsApp is glanced at, not studied.
Always offer human escalation; bot dead-ends destroy trust.
Design for the 24-hour window — capture what you need while you can message freely.
**Click-to-WhatsApp ads.** Facebook/Instagram ads opening WhatsApp chats — high intent, conversational conversion.
Pre-fill context (which ad, which product) so agents do not ask "how can I help?" blindly.
Track chat-to-sale conversion; it justifies the ad spend.
**Multi-location management.** Central number with location routing vs. per-location numbers.
Central: consistent branding, complex routing. Per-location: local trust, management overhead.
Hybrid (central marketing, local support numbers) often wins.
## Practical workflow

1. **Choose the platform.** Volume, team size, automation needs → app or API. Plan for growth: starting on the app and migrating later is painful — choose with 12-month needs in mind.
2. **Set up properly.** Business profile (complete: description, hours, address, website), catalog for products, quick replies for FAQs, greeting/away messages, labels for organization (app) or CRM integration (API).
3. **Build opt-in.** Website widgets, QR codes in-store/on packaging, checkout checkboxes (unchecked by default), and clear value statements ("order updates + support on WhatsApp"). Document consent.
4. **Design flows.** Support: triage bot → human with context. Notifications: order updates, appointment reminders, delivery tracking. Marketing broadcasts: segmented, infrequent, high-value. Map each flow's 24-hour window handling.
5. **Train the team.** Tone guidelines (WhatsApp is conversational — match it professionally), response SLAs, escalation paths, when to move to voice/video, and logging discipline.
6. **Measure.** Response times, resolution rates, CSAT, opt-out rates, broadcast engagement, and cost per conversation (API). Review templates quarterly for approval status and performance.

**Support response framework:** acknowledge quickly (even "looking into it") → resolve or escalate with timeline → confirm resolution → log in CRM → follow up if needed.


**Support implementation:** WhatsApp number prominently placed (website, packaging, emails) → chatbot triage for common issues (order status, hours, returns) → human handoff with full context → CSAT survey post-resolution → conversation summaries logged to CRM. Response-time SLAs matter more here than email — customers expect chat-speed replies.

**Broadcast campaign playbook:** segmented audience (never blast everyone) → approved utility or marketing template → clear CTA (button, not just text) → send at local-appropriate times → measure read rate, CTR, and opt-outs per campaign. Keep marketing broadcasts to 2–4/month — WhatsApp intimacy punishes spam severely.

**Template library (build 20+):** order confirmations → shipping updates → appointment reminders → payment reminders → feedback requests → win-back offers → support follow-ups.
Get templates approved in advance — approval delays kill campaign timelines.
**Quality rating management.** WhatsApp rates template message quality; low ratings limit messaging.
Monitor ratings weekly; pause low-performing templates immediately.
User blocks are the ultimate signal — track block rates per template.
## Common pitfalls

- **No opt-in.** Messaging people who never agreed. Ban risk + legal risk + annoyed customers.
- **Treating it like email.** Long formal messages. WhatsApp is conversational — short, warm, direct.
- **Slow responses.** WhatsApp creates instant expectations. Staff for the SLA you promise.
- **Template rejections.** Marketing language in utility templates. Write to the category; get approval before campaigns.
- **Ignoring the 24h window.** Designing flows that break when the window closes. Plan template re-entry.
- **Personal numbers for business.** Staff using personal WhatsApp for customers. Use business accounts — for boundaries and continuity.
- **No CRM logging.** Conversations invisible to the rest of the business. Integrate or lose the data.
- **Treating it like email.** Long messages, formal tone, weekly blasts. WhatsApp is conversational — short, personal, timely.
- **No opt-in management.** Messaging without proper consent. WhatsApp bans aggressively for spam reports — consent records are your protection.
- **Ignoring the window.** Letting conversations lapse past 24 hours without a template strategy. Design flows that close within the window.
- **Template spam.** Blasting promotional templates indiscriminately. Quality ratings drop, messaging gets restricted — restraint preserves the channel.
- **Ignoring message timing.** 2am promotional messages. Respect local time and reasonable hours, always.