WhatsApp customer care: consent, records and the handover nobody designs

Why the phone in the pocket stops working

For a small business, answering customers from the WhatsApp Business app on a single phone is often how messaging starts. It is fast, familiar and free, and customers like it. The problems appear as volume grows. Conversations are tied to one device and one person. When that person is ill, on holiday or leaves the company, the history goes with them. Nobody can see response times, nobody can pick up a conversation halfway, and nothing connects the chat to the customer’s order or case.

The more serious problem is accountability. Customer care conversations contain complaints, promises, prices, addresses and sometimes sensitive information. A business that cannot retrieve what was said to a customer cannot resolve a dispute fairly, cannot demonstrate what consent it collected and cannot respond properly to a data access request.

The app versus the Business Platform

Meta offers two routes. The WhatsApp Business app is designed for small businesses managing conversations from a phone or a small number of linked devices. The WhatsApp Business Platform, accessed through Meta directly or through a business solution provider, is designed for integration with CRMs, helpdesks and automation, with multiple agents working from shared systems.

The Platform introduces rules that shape design. Businesses can reply freely within a customer service window that opens when the customer messages them. Outside that window, business-initiated messages must use pre-approved message templates, and customers must have opted in to receive messages from the business. Template categories and pricing change over time, so the current Meta policies should be checked when designing a service.

Business app

Suitable for low volumes and a small team. Limited integration, reporting and shared history.

Business Platform

Suitable for multiple agents, CRM integration, automation and reporting, with template and opt-in rules for business-initiated messages.

Consent is two different questions

Businesses often treat consent as one checkbox, but WhatsApp customer care usually raises two separate questions. The first is whether the customer has agreed to receive messages from the business on WhatsApp at all, which Meta’s policies require for business-initiated messages. The second is whether the business has a lawful basis under data protection law for processing the personal data involved and, where marketing is concerned, whether marketing consent rules are met.

A customer who asks for delivery updates on WhatsApp has not necessarily agreed to receive promotions there. Keeping service messages and marketing permissions separate, recording when and how each was given, and making it easy to opt out protects both the customer relationship and the business.

Records, retention and sensitive information

Connecting WhatsApp to a CRM or helpdesk creates a shared record of conversations, but it also creates a data retention question. Messages should be kept long enough to handle disputes, warranty claims and legal requirements, and deleted when there is no longer a reason to keep them. That period should be decided deliberately and applied automatically.

Customer care teams should also decide what should not be discussed in chat. Payment card details, identity documents, health information and legal matters may require secure forms or other channels. A short message that redirects the customer to a secure upload link is better than collecting sensitive files in an unstructured conversation history.

Where automation helps and where it harms

Automation works well for predictable, low-risk requests: order status, delivery windows, opening hours, appointment confirmations and document requests. When connected to live system data, these answers are fast and accurate, and they remove repetitive work from the team.

Automation harms when it blocks access to a person, answers questions it cannot answer reliably or handles unhappy customers as if they were routine requests. On a personal-feeling channel like WhatsApp, a bot that loops or pretends to understand damages trust quickly. Customers should know when they are talking to an automated system, and should be able to reach a person without guessing a keyword.

Designing the handover

The handover from automation to a person, or from one agent to another, is where WhatsApp customer care is won or lost. The receiving agent should see the whole conversation, the customer’s identity where verified, related orders or cases, and anything the automated system already checked, before replying. The customer should never have to repeat themselves.

Handover rules should be explicit: complaints, refunds outside policy, legal or safety issues, repeated failed answers and any request for a person should route to staff immediately. Response time targets during business hours, and clear messages outside them, set expectations honestly.

The metrics worth watching are first response time, time to resolution, the share of conversations resolved without the customer repeating information, and customer satisfaction after the conversation. Volume handled by automation matters less than whether customers got what they needed.

Where this sits in what we do

This article covers one decision inside a wider engagement. The solution page sets out how that engagement runs, what it includes and what it costs to find out.

• AI Customer Experience — A chatbot, a voice agent and a knowledge base that share one grounded source of truth — with citations, measured accuracy and a fast route to a human.
• AI for custom customer care: what it can answer and what it must not
• Customer care for logistics companies: proactive delay communication beats a bigger call centre
• B2B order portals for wholesale distributors: customer-specific prices, stock and reordering
• When to build software instead of buying it
• All insight articles