WhatsApp for Business Support: Complete 2026 Guide

IN THIS ARTICLE

1. 01WhatsApp Business App vs WhatsApp Business API: which one do you need?
2. 02How to get access to the WhatsApp Business API
3. 03Message templates and the 24-hour rule
4. 04Compliance: what you must get right
5. 05Managing WhatsApp support at scale
6. 06Automation on WhatsApp: what to automate and what not to
7. 07WhatsApp and CSAT: measuring satisfaction on a messaging channel

WhatsApp has 2 billion monthly active users. Messages sent through it have a 98% open rate, compared to around 21% for email. For businesses that handle customer support, these numbers are not abstract: they mean your customers are far more likely to read and respond to a WhatsApp message than an email, and far more likely to contact you there if you let them.

But running customer support on WhatsApp at scale is not as simple as downloading an app. This guide covers the full picture: what your options are, how to set up properly, how to stay compliant, and how to manage WhatsApp support at volume without drowning your team.

WhatsApp Business App vs WhatsApp Business API: which one do you need?

There are two entirely different products marketed under the "WhatsApp Business" name, and choosing the wrong one creates serious operational problems as you grow.

WhatsApp Business App

The WhatsApp Business App is a mobile app available for free download. It is designed for sole traders and very small businesses. You get a business profile, quick reply shortcuts, away messages, and a catalogue feature for products. It works from one device per number. Multiple agents cannot share it properly. There is no inbox management, no analytics, no SLA tracking, and no way to connect it to your CRM or helpdesk.

If you are a one-person operation handling five messages a day, this is sufficient. If you have a support team, it is not.

WhatsApp Business API

The WhatsApp Business API (now part of the Meta Cloud API) is a programmatic interface designed for businesses with volume. It is not a standalone app. You access it through a Business Solution Provider (BSP) or by direct Meta integration, and you connect it to a platform like Delyt to manage messages. Multiple agents can handle conversations. You get read receipts, message templates, automation, and full analytics.

How to get access to the WhatsApp Business API

To use the WhatsApp Business API, you need a Meta Business account and a verified phone number. The verification process takes one to five business days and requires a real business entity. You cannot use a personal mobile number that is already registered on WhatsApp.

1. 1Create or verify your Meta Business Manager account at business.facebook.com
2. 2Register a phone number that is not already associated with WhatsApp (a landline or a dedicated SIM works)
3. 3Connect to the Meta Cloud API directly or through a BSP (Delyt handles this step for you during onboarding)
4. 4Submit your business for WhatsApp verification: you will need a business website and an active Facebook Business page
5. 5Once approved, configure your business profile: display name, description, website, and support hours

Meta has significantly streamlined the approval process since 2024. Most businesses with a legitimate online presence are approved within two to three business days.

Message templates and the 24-hour rule

WhatsApp has a customer protection policy that requires businesses to understand before going live: the 24-hour messaging window.

Within 24 hours of a customer sending you a message, you can respond freely with any message type. After that window closes, you can only send pre-approved message templates (called HSMs: Highly Structured Messages). This means you cannot send a follow-up or re-engagement message to a customer who contacted you three days ago unless it is a template that Meta has approved in advance.

• Utility templates: order confirmations, shipping updates, appointment reminders (approved quickly)
• Authentication templates: one-time passwords (approved quickly)
• Marketing templates: promotions, re-engagement campaigns (require more evidence during approval)
• Customer service templates: follow-ups, resolution confirmations, survey requests

Template approval takes one to 24 hours for straightforward utility messages. Build your template library before going live so your team is not blocked on day one.

Compliance: what you must get right

WhatsApp support comes with compliance requirements that differ from email. These are not optional and Meta enforces them through account ratings that affect your ability to initiate conversations.

• Opt-in required: customers must explicitly opt in to receive WhatsApp messages from you. "By placing this order, you agree to receive WhatsApp updates" is acceptable. Scraping phone numbers from a CRM without opt-in is not.
• Opt-out must work: every outbound message must honour STOP/unsubscribe requests. Ignoring them degrades your phone number quality rating.
• No spam: high block and report rates from customers will result in your number being restricted or banned. Send relevant messages only.
• GDPR and CCPA: WhatsApp conversation data needs to be covered in your privacy policy. If you store transcripts in a third-party inbox platform, that platform needs to be listed.
• Template pre-approval: any message sent outside the 24-hour window requires an approved template. Sending unapproved messages is a policy violation.

Managing WhatsApp support at scale

The biggest operational challenge with WhatsApp support is volume management. Customers expect fast replies: often within minutes, not hours. If you connect WhatsApp to a shared inbox without triage and routing logic, the channel will overwhelm your team.

The answer is the same infrastructure that makes any channel manageable: AI triage to classify incoming messages, routing rules to assign them to the right agent, automated responses for common questions, and a unified view that lets your team see WhatsApp alongside email, Instagram, and chat without switching tools.

Automation on WhatsApp: what to automate and what not to

WhatsApp automation has a higher bar for quality than email. Customers using WhatsApp expect conversational, human-quality responses. A robotic auto-reply that does not address their question will earn you a block faster than the same response on email.

Good candidates for automation: order status lookups (where the answer is a specific data point from your order system), return policy questions, shipping estimate queries, business hours, appointment confirmations, and FAQ-style questions your knowledge base can answer definitively.

Bad candidates for automation: complaints, anything requiring empathy, complex billing disputes, situations where the customer sounds upset, and any scenario where a wrong answer from the AI would make the situation worse. These should escalate to a human immediately.

WhatsApp and CSAT: measuring satisfaction on a messaging channel

WhatsApp is a natural channel for post-resolution CSAT collection. A short message after a ticket is closed: "We have resolved your case. Did we help? Reply 1 for Yes, 2 for No": gets significantly higher response rates than an email survey link. The informality of the channel works in your favour.

Keep CSAT messages short and binary. WhatsApp is not a survey platform. One or two questions maximum. If you want more detail, collect it via a brief follow-up question only if the customer replies.