Guides 3 min read Updated November 18, 2026

WhatsApp Customer Service: A Practical Guide

How to run customer service on WhatsApp in 2026 — Business App vs API, the 24-hour window, template messages, and what it costs to do properly.

WhatsApp Customer Service: A Practical Guide

Short answer: WhatsApp customer service runs either on the free Business App, which suits one person on a phone, or on the WhatsApp Business Platform API, which supports a real team and bills per 24-hour conversation. The rule that shapes everything is the 24-hour window: after a customer’s last message, you can only restart the conversation with a pre-approved template.

In large parts of Latin America, South Asia, the Middle East and southern Europe, WhatsApp is not a support channel. It is the support channel.

Business App or API

The free app is a phone application. One business account, limited labels, quick replies, no meaningful multi-agent support and no integration with anything else you run. For a sole trader or a small shop it is genuinely enough, and starting there costs nothing.

The API has no interface at all. You connect it to a platform — a help desk, a shared inbox, a messaging tool — and that platform becomes where agents actually work. You get multiple agents, assignment, automation, and the ability to put WhatsApp conversations next to your email and web chat instead of on someone’s personal handset.

The migration between them is the awkward part. Moving a number from the app to the API is a one-way door for that number, so decide before you print it on packaging.

The 24-hour window, and why it governs everything

When a customer messages you, a 24-hour service window opens and you can reply with anything. When it closes, you cannot simply follow up. You can only send a template message that Meta approved in advance, in a category like utility, authentication or marketing.

Three consequences follow, and they are all operational rather than technical:

Staffing has a deadline attached. A web chat left overnight is rude; a WhatsApp conversation left overnight costs you the ability to answer freely at all. Teams running WhatsApp seriously either cover the hours or let an AI assistant hold the thread until someone is available.

Templates need writing before you need them. Order updates, delivery notifications, appointment reminders and “we are following up on your issue” should all exist as approved templates ahead of time. Writing one while a customer waits is too late.

Marketing templates cost more than service replies, and customers report them as spam faster. Keep the two uses clearly separated.

What it costs

The Business App is free. The API bills per 24-hour conversation, priced by category and by country, with service conversations the customer starts costing less than marketing conversations you initiate. Rates differ enough between markets that a per-conversation estimate from a vendor in one country tells you very little about another.

On top of Meta’s charges you pay the platform you connect through. Budget both. A quoted “WhatsApp from $X” almost always means the platform fee only.

Running it without creating a second support silo

The common failure is treating WhatsApp as its own system. One person ends up owning the phone, conversations do not become tickets, and nobody can see the history when that person is on leave.

Route WhatsApp into the same inbox as everything else. A conversation should become a trackable item with an owner regardless of which channel it arrived on, which is the whole argument for CRM ticketing sitting behind your channels rather than beside them.

Then automate the repetitive share. Order status, opening hours, returns policy and delivery timelines are the bulk of inbound WhatsApp volume for most retailers, and an AI chatbot trained on your own content handles them without a template or an agent.

Where EasyChatDesk fits, honestly

Our product is web-chat-first. Live chat, AI and ticketing come on one plan from $17 per agent per month — see pricing — and that is the right fit if your conversations start on your website and you want them tracked properly.

If WhatsApp is genuinely your primary channel rather than one of several, a WhatsApp-first platform will serve you better on templates, broadcast campaigns and the operational detail of the Business API. We compare that case directly in SleekFlow alternatives.

For the broader channel question, customer communication channels covers how these fit together, and omnichannel customer support covers running them as one queue.

Frequently asked questions

Can I use WhatsApp for customer service?

Yes, through either the free WhatsApp Business App or the WhatsApp Business Platform (the API). The free app suits a single person answering messages on a phone. Once you need several agents, a shared inbox or automation, you need the API and a provider to connect to it.

What is the difference between WhatsApp Business App and the API?

The app is a phone application for one business user, free, with no real multi-agent support. The API has no interface of its own — you connect it to a help desk or messaging platform, it supports many agents, automation and integrations, and you pay per conversation.

How much does WhatsApp customer service cost?

The Business App is free. The API bills per 24-hour conversation window, priced by category and country, and you also pay whichever platform you connect it to. Service conversations started by the customer are cheaper than marketing ones you initiate, and rates vary considerably by market.

What is the 24-hour rule on WhatsApp?

Once a customer messages you, you can reply freely for 24 hours. After that window closes you can only re-open the conversation with a pre-approved template message. This single rule shapes how support teams staff and prioritise WhatsApp queues.

Is WhatsApp better than live chat for support?

It is different, not better. WhatsApp wins on reach and on conversations that continue over days, because the thread lives in an app the customer already has. Web chat wins on immediacy and context, because you know what page they are on. Most teams that do both route them into one inbox.

Level up your customer support

Try EasyChatDesk free: live chat, help desk ticketing and an AI chatbot in one platform.

Start for free

Related articles