For many customers, especially outside the United States, a message on WhatsApp is the most natural way to ask a business a question. It is quicker than email, less formal than a phone call and already open on their phone. A store that offers it can answer “where is my parcel” in seconds and send an order update without needing the customer to install anything.
It is also an area where details matter: who may message whom, what needs approval and what each message costs. This guide explains how to use WhatsApp in a store’s customer service, the difference between the app and the platform, the rules you must respect, and what to automate. Policies and prices change, so confirm everything in Meta’s documentation before you commit. For wider context, see AI chatbots for customer service and chatbot to human handoff rules.
Where WhatsApp fits
| Use | Why WhatsApp works | Caution |
|---|---|---|
| Order updates | High visibility, immediate | Needs opt-in and approved templates |
| Pre-sale questions | Customers ask quickly while deciding | Link from product pages with a chat button |
| Delivery coordination | Address checks, time windows | Do not collect sensitive data unnecessarily |
| Returns and exchanges | Photos are easy to send | Keep a record in your helpdesk |
| Back-in-stock alerts | High attention | Strict opt-in; not promotional spam |
| Abandoned cart reminders | Direct | Requires consent; follow marketing rules |
It works best in markets where WhatsApp is the default messaging app. In places where customers prefer other channels, email or SMS may be better. Check where your own customers come from and what they ask for; our SMS marketing guide covers a similar decision.
The app versus the API
| WhatsApp Business app | WhatsApp Business Platform (API) | |
|---|---|---|
| Best for | Very small stores, low volume | Growing stores and teams |
| Users | One phone, with limited linked devices | Multiple agents through a helpdesk or provider |
| Automation | Basic away messages and quick replies | Chatbots, workflows, integration with the store |
| Broadcasts | Limited | Template messages to opted-in contacts |
| Setup | Install and verify a number | Apply through Meta or a provider, verify the business, register a number |
| Cost | Free to use | Pricing depends on the type of conversation or message and your provider |
Many stores start with the app, then move to the platform when volume or the number of agents grows. Moving means using a number registered with the platform, which cannot be used in the consumer app at the same time, so plan the switch. A provider (called a Business Solution Provider) can handle setup and add a shared inbox.
The rules in outline
- Opt-in. You need permission to message people on WhatsApp, and you should record how and when you got it.
- Customer-initiated conversations. When a customer messages you, a service window opens during which you can reply freely.
- Business-initiated messages. Outside that window you must use pre-approved message templates for specific purposes, such as order updates.
- Content rules. Meta’s policies restrict what businesses may send and which products can be promoted.
- Quality. Meta tracks quality signals such as blocks and reports; poor quality can limit your messaging.
- Pricing. Meta charges by message category, and the model has changed in the past; check the current price list.
Do not buy contact lists or message people who never asked. It violates the policy, damages your number’s quality and risks the number being restricted. Collect opt-in at checkout with a clear statement of what you will send, or when the customer first messages you.
What to automate
| Message or task | Automation | Human role |
|---|---|---|
| Order confirmation and shipping update | Template triggered by order events | None, apart from exceptions |
| Order status question | Bot looks up the order and replies | Handles failures to find the order |
| Delivery problem | Bot collects details and opens a case | Agent resolves |
| Returns request | Bot checks eligibility and issues a label | Agent approves exceptions |
| FAQs about shipping and policies | Bot answers from policy text | Updates the content |
| Complaints and refunds above a limit | Route immediately | Decides |
The structure follows the same pattern as every support automation: answer what you can from reliable data, collect context for what you cannot, and hand over cleanly. Our ecommerce WhatsApp automation and order status updates services implement it.
Writing for the channel
- Short messages, plain words, one question at a time.
- Use the customer’s name and order number, not a long form.
- Buttons and quick replies save typing on a phone.
- Avoid walls of text; send a link for detail.
- Match the tone of a conversation, not a corporate letter.
- Tell people when a bot is replying and how to reach a person.
A setup plan in seven steps
- Decide the goals. Order updates only, or support as well? Start narrow.
- Choose the route. The Business app for a trial, or the platform through a provider for automation and teams.
- Prepare the number. Use a dedicated business number and verify the business with Meta where required.
- Design opt-in. Add a checkbox at checkout and a click-to-chat link on product and order pages, with clear wording.
- Write and submit templates. Order confirmation, shipped, delivered and delay messages, in plain language.
- Connect the store and helpdesk. Trigger templates from order events and route replies to a shared inbox.
- Test and launch gradually. Try it with staff, then a small share of customers, and watch quality and replies.
What to measure
| Metric | Why it matters |
|---|---|
| Opt-in rate at checkout | Shows whether the wording and placement work |
| First response time | The main reason customers prefer chat |
| Resolution without a person | Share handled by the bot or a template |
| Block and report rate | A quality warning; too many risks restrictions |
| Status questions by email | Should fall as updates improve |
| Cost per conversation | Compare messaging fees with time saved |
Review these monthly for the first quarter. If blocks rise, look at message frequency and content before anything else; if opt-in is low, test the wording. Most problems with WhatsApp programmes come from asking for too little consent or sending too much.
Handoff and records
Conversations in a phone app are invisible to the rest of the team. For anything beyond very small volumes, connect WhatsApp to a shared inbox or helpdesk so that all agents see the history, tickets are tracked and the conversation is linked to the order. Keep records according to your retention policy, and avoid asking customers for payment card details or other sensitive information in chat. See customer support chatbot for the build.
Privacy and compliance
WhatsApp messages concern personal data, so privacy laws apply. State in your privacy notice that you use WhatsApp, what you use it for and how long you keep conversations. Respect opt-out requests immediately. If you use a provider, check where data is processed. See GDPR and CCPA for ecommerce chatbots.
Quality, templates and keeping your number healthy
Your WhatsApp number carries a quality rating that depends on how recipients react. Messages that people block or report lower it, and a low rating can limit how many people you may message. Protect it by sending only to people who opted in, by writing templates that clearly match what the customer expects, and by keeping marketing volume modest. Review template performance monthly: retire ones with high block rates, and rewrite those that customers ignore. Keep a log of template submissions and approvals, since rejected templates cost days. If you work with a provider, ask how they report quality and what happens if the rating drops, so that you are not surprised in the middle of a sale.
A worked example
A store with 2,000 orders a month receives about 300 order-status questions by email, each taking 4 minutes. After adding WhatsApp order updates with opt-in at checkout, around 60 percent of customers opt in and the number of status questions falls by about a third, or 100. That saves roughly 6.7 hours a month, about $150 at $22 an hour. If template messages cost a few cents each in the customer’s region and 1,200 orders generate three messages each, the message cost might be $100 to $200 a month; the exact number depends on current pricing. The financial gain is therefore small, and the case for WhatsApp rests on customer preference and faster resolution. The figures are illustrative; check your region’s rates.
Mistakes to avoid
- Messaging without opt-in.
- Using the personal app for business at scale.
- Bots with no way out.
- Promotional templates posing as service messages.
- Ignoring quality ratings.
- Not recording conversations in the helpdesk.
- Not checking prices for your country.
Sources and further reading
Figures and rules in this guide come from the primary pages below. Platform limits and prices change, so open the page before you build on a number.
- WhatsApp Business Platform documentation, API, templates and messaging policies
- WhatsApp Business Policy, what businesses may and may not send
- Meta: WhatsApp Business Platform pricing, current message pricing