How to set up WhatsApp Business API for customer support

WhatsApp is where a large share of the world already talks, which makes it a serious customer-support channel rather than a novelty. But "getting on WhatsApp" as a business is genuinely more involved than installing a chat widget: Meta requires a verified business, a dedicated phone number, and API access through their platform. This guide walks the whole path, honestly, including the parts that take waiting rather than clicking.

First: the app you know is not the API you need

There are three WhatsApp products, and picking the wrong one wastes a week:

Product	Who it's for	Limits
WhatsApp (consumer app)	Personal chats	Not for business use
WhatsApp Business app	Solo operators, one phone	One device-ish, manual replies, no integrations
WhatsApp Business Platform (Cloud API)	Teams and software integrations	Needs Meta setup; this is what support tools use

If more than one person will answer customers, or you want conversations in a shared inbox with routing and history, you need the Cloud API.

What you'll need before starting

• A Meta Business Manager account (business.facebook.com), ideally already verified. Business verification can take from hours to days and unlocks higher messaging limits.
• A phone number not currently registered to any consumer WhatsApp or WhatsApp Business app. Porting a number out of the consumer app is possible but adds steps; a fresh number is the low-friction path.
• A support platform that speaks the Cloud API. This is what turns raw API events into an inbox your team can actually work. (Chattypie's omnichannel inbox includes a WhatsApp channel; the last section shows the exact fields.)

Step 1: Create the Meta app and add WhatsApp

1. Go to developers.facebook.com → My Apps → Create App and choose the Business type, linked to your Business Manager.
2. In the app dashboard, click Add product → WhatsApp. Meta provisions a test number and a temporary token immediately. Good for experimenting, not for production.

Step 2: Register your real phone number

In WhatsApp → API Setup, add your business phone number and verify it by SMS or voice call. Once verified, Meta assigns it a Phone Number ID, a numeric ID you'll paste into your support platform. Note it down.

Step 3: Create a permanent access token

The token shown on the API Setup page expires in 24 hours, a classic trap. For production:

1. In Business Manager, open Business Settings → Users → System Users and create a system user with admin access to the app.
2. Generate a token for that system user with the whatsapp_business_messaging and whatsapp_business_management permissions.
3. Store it like a password. Anyone holding it can send messages as your business.

Step 4: Point the webhook at your support platform

Meta delivers inbound messages by calling a webhook URL you control. In your app's WhatsApp → Configuration:

1. Paste the callback URL your support platform gives you.
2. Enter the verify token, an arbitrary string you choose; the platform echoes it so Meta knows the endpoint is really yours.
3. Subscribe to the messages webhook field.

Step 5: Understand the 24-hour rule before you go live

This is the policy that surprises every team:

• When a customer messages you, a 24-hour customer-service window opens. Inside it you can reply freely.
• Outside that window, you can only send pre-approved template messages, and Meta reviews each template.
• Business-initiated conversations always start from a template.

Practical consequence: WhatsApp is superb for responding to customers and terrible as a cold-outreach channel. Design your flows accordingly, and submit your first templates (order updates, appointment reminders, "we replied to your question") early, since review takes time.

Step 6: Connect it to Chattypie

In the Chattypie dashboard, open WhatsApp Channel and fill in the four fields from the steps above:

• Phone Number ID: from Step 2.
• Business Name: what your team sees on the channel.
• Access Token: the permanent system-user token from Step 3.
• Verify Token and Webhook Secret: set here, then paste the same values into Meta's webhook configuration from Step 4.

Send a WhatsApp message to your business number: it should land in the same inbox as your website chat, with the customer's history attached, routable to any agent. Replies from the inbox go back out through the API within the session window.

Checklist before announcing the channel

1. Test the full round-trip: customer message in → agent reply out → customer receives it.
2. Verify your first message templates are approved.
3. Set expectations in your WhatsApp business profile (hours, response time).
4. Decide routing: who owns WhatsApp conversations, and does the AI agent answer first? (If you are weighing automation, our honest guide to AI support covers where it works.)

WhatsApp setup is front-loaded bureaucracy followed by a genuinely low-maintenance channel. Budget an afternoon for Meta's side, ten minutes for the support-platform side, and a few days of calendar time for verifications and template approvals to clear. One caveat worth stating: Meta moves its admin UI around regularly, so if a menu name here has drifted, the sequence (app, phone number, permanent token, webhook, templates) is the part that stays true.

If WhatsApp is your second or third channel, the coordination question matters more than any single channel: shared inbox vs help desk explains how teams keep multichannel conversations in one place.