WhatsApp for Customer Service: Setup, Scripts, and What Actually Works

WhatsApp for customer service is not as simple as adding a phone number and letting customers message you. Meta's Business API has specific rules about opt-ins, message templates, response windows, and what you can - and cannot - send proactively. Teams that ignore these rules get their accounts flagged or suspended.

This guide covers the practical mechanics: the right product to use, the compliance requirements you can't skip, the use cases that generate real ROI, and the metrics that tell you whether your WhatsApp channel is working.

WhatsApp Business App vs. WhatsApp Business API

Meta offers two products for businesses. Understanding the difference is the first decision any team needs to make.

Any support team beyond a solo operator needs the API. The app's 5-device limit and manual-only workflow won't scale, and without integration you're managing WhatsApp conversations in isolation from your other channels. Velaro connects to WhatsApp via the Business API, routing all conversations into the same agent inbox as web chat, email, and SMS.

The Opt-In Requirement (Don't Skip This)

Unlike email, where you can often message customers who gave you their address during a purchase, WhatsApp requires explicit opt-in before you can initiate a conversation. This is enforced at the platform level - not just Meta's policy, but a technical constraint. You cannot send a template message to a number that hasn't opted in.

Opt-in must be collected outside of WhatsApp (since the customer isn't on WhatsApp with you yet) and must:

• Clearly state that the customer is opting in to receive WhatsApp messages from your business
• Name your business specifically (not just "you will receive messages")
• Include the WhatsApp phone number or business name they'll receive messages from
• Be a separate consent action from your general marketing consent

Valid opt-in channels: a checkbox on your website (order confirmation page, account settings), an SMS opt-in flow ("Reply YES to receive updates via WhatsApp"), or an in-app prompt. Invalid: assuming consent based on a phone number captured during purchase.

"Meta actively monitors for message sending to non-opted-in numbers. An account that generates significant 'block' signals from users can be suspended without warning. The opt-in requirement is not flexible."

The 24-Hour Response Window

WhatsApp's messaging policy divides conversations into two types, and understanding this is essential for how you build support workflows:

Service conversations (customer-initiated)

When a customer messages your business first, a 24-hour window opens. During this window, you can send any message - free-form text, images, documents, custom responses. No template required. This is where standard customer support happens.

If the 24-hour window closes before you respond (or before the customer replies to your response), the window resets. To message the customer after the window, you must send a pre-approved template message - which reopens a new window.

Template (business-initiated) messages

Any message your business sends to a customer outside of an active 24-hour window must use a pre-approved template. Templates are submitted to Meta for review and must meet specific guidelines: no promotional content beyond a limited promotional category, no spam-like structure, clear purpose.

Templates have categories with different pricing:

Best Use Cases for WhatsApp Customer Service

Not every support function benefits equally from WhatsApp. The highest-ROI use cases are:

Order and shipping updates

Proactive order confirmations, shipping notifications, and delivery updates via WhatsApp reduce inbound "where is my order" contacts by 20-30%. Customers who know their order shipped and have a tracking link don't need to contact support. This is a utility template - the cheapest category.

Appointment reminders

Healthcare, service businesses, and B2B teams see 25-40% reduction in no-shows when appointment reminders are sent via WhatsApp instead of SMS or email. The 98% open rate is the reason - the reminder actually gets seen.

Inbound support conversations

When customers message your WhatsApp number with a support question, you have a 24-hour window to resolve it with full free-form conversation. This is where bot automation works well - an automated response within seconds, bot handles structured queries, human takes over for complex issues. The customer experience is conversational and fast.

What Doesn't Work on WhatsApp

Teams that treat WhatsApp as a marketing blast channel run into problems quickly. What to avoid:

• Unsolicited promotional messages: Marketing templates are expensive, need explicit opt-in, and have lower engagement than utility messages. Customers who opted in for "order updates" and receive promotional content will block your number.
• High message frequency: WhatsApp is conversational, not a newsletter channel. Sending weekly promotional messages via WhatsApp generates block rates that can get your account suspended.
• Templates that read like spam: Meta reviews templates before approval. "ACT NOW! 50% OFF TODAY ONLY!!" style copy will be rejected. Templates need to be informative and specific.
• Support without coverage: If you offer WhatsApp support, customers expect it to be staffed. A WhatsApp channel that takes 6 hours to respond is worse than not offering WhatsApp - it creates the expectation of fast response and then fails it.

Metrics That Matter for WhatsApp Support

Standard support metrics apply to WhatsApp, but a few are WhatsApp-specific:

• First response time within the 24-hour window: WhatsApp customers expect fast responses. A 24-hour window sounds generous, but customers typically expect a reply within 2-4 hours. Track median first response time separately for WhatsApp vs. other channels.
• Window utilization rate: What percentage of your inbound WhatsApp conversations are resolved within the initial 24-hour window? Low rates mean you're either responding slowly or conversations are reopening unnecessarily.
• Block rate: Meta provides data on the percentage of recipients who block your number after receiving messages. A block rate above 1-2% for template messages is a warning signal. Above 5% puts your account at risk.
• Template opt-out rate: For each template you send, track how many recipients reply "STOP" or similar. High opt-out rates on specific templates indicate the template is unwanted - revise or retire it.
• CSAT by channel: WhatsApp CSAT should be tracked separately from web chat CSAT. The channel affects the experience - conversational, mobile-first, asynchronous - and benchmarks differ.

Getting Started: The Practical Path

1. Choose a Business Solution Provider (BSP): You access the WhatsApp Business API through a Meta-approved BSP. Velaro is a BSP partner. This is required - there's no direct API access for most businesses.
2. Verify your business: Meta requires business verification before activating the API. This involves submitting business documents and typically takes 3-7 business days.
3. Set up opt-in collection: Add a WhatsApp opt-in checkbox to your order confirmation page, account settings, or checkout flow. Do not go live without this in place.
4. Create and submit your initial templates: Start with 3-5 templates for your highest-priority use cases (order shipped, appointment reminder, support introduction). Submit for Meta review - approval typically takes 24-48 hours.
5. Configure your inbox routing: Route incoming WhatsApp messages to the same queue as your web chat or to a dedicated WhatsApp queue, depending on team structure. Set up your bot's first-response flow.
6. Pilot before full launch: Run a soft launch with a subset of customers before promoting the WhatsApp number broadly. Use the pilot period to refine bot flows and agent response templates.

For teams already using Velaro for web chat, adding WhatsApp is typically a 1-2 day configuration effort once the Meta verification is complete. The Velaro WhatsApp integration handles the API connection, routing, and shared inbox configuration. More context on managing multiple channels in one inbox in the omnichannel guide.

The Bottom Line

WhatsApp gives support teams access to a channel where customers already spend their time - with open rates and response rates no email or live chat widget can match. The API setup requires Meta verification and approved message templates, but for teams already running live chat, the incremental effort is modest. Start with outbound notifications, add inbound support routing, and expand use cases as you validate what your customers actually respond to.